Ask questions that change delivery decisions
Discovery questions should clarify the desired outcome, current workflow, constraints, dependencies and ownership. Ask why the project is needed before prescribing a technology. Separate must-have requirements from preferences and unresolved assumptions. Each question should help decide scope, sequencing or acceptance rather than collecting detail simply because a questionnaire can.
Worked example
Illustrative scenario; not a claim of measured client results.
For a customer portal, ask who will use it, what tasks they must complete, which systems hold the data and who approves access. These answers affect architecture and delivery. Asking only which framework the client prefers can miss the actual operating problem. Use follow-up questions to resolve contradictions between the desired outcome and available resources.
Checks, limitations and next decisions
After the discussion, summarize what is confirmed, assumed and still unknown. Ask the relevant stakeholders to validate the summary before treating it as scope. Avoid promising a fixed estimate when major integrations or data conditions remain untested. Good questions reduce uncertainty and produce a shared basis for the next decision rather than an apparently complete but unreliable specification.
A practical starting point
Work through these checks in order. Use the results to decide what needs to change in your own workflow.
- Clarify the current problem and who experiences it.
- Identify systems, approvals and deadlines that constrain the work.
- Agree how success will be evaluated.
A mistake to avoid
Do not use discovery only to confirm a solution already chosen.
How to check progress
Track unresolved assumptions and the decisions each answer enables.
Your action checklist
Use this checklist while reviewing your own setup. Checkmarks are temporary and stay in this open page.
For the wider decision process, read Reducing friction in a project enquiry form.
Further reading
Official background resources for this topic. The workflow above is general guidance, not a guarantee of a particular result.
AI-assisted editorial content. Examples are illustrative, not client case studies. Read our editorial policy or report a correction.
