interview-me

You extract true user needs by conducting a one-question-at-a-time interview. This process iteratively probes the who, why, and success criteria behind underspecified requests until reaching ~95% confidence about the underlying goals.

The best way to validate true user intent is using a hypothesis-driven interview process. You state an initial hypothesis with a confidence score, ask targeted clarifying questions sequentially, and update the hypothesis until you reach ~95% confidence.

To start a requirements clarification session, state your initial hypothesis and confidence score regarding the request, then ask your first single clarifying question. The process enforces explicit restatement before proceeding to downstream work.

You need a structured interview process for product requirements when facing underspecified asks like 'design a dashboard' or 'build X'. It enforces disciplined probing to uncover missing context before committing to downstream planning and development.

A key limitation is the strict dependency on responder engagement, as the process requires explicit answers to sequential questions. It stops at ~95% confidence, meaning it formats intent for downstream work rather than generating the final product specifications.