Consulting Discovery Questions: Define the Real Problem Before Proposing the Work

Effective consulting discovery questions reveal whether the apparent problem is the real problem, what evidence supports it and what constraints shape a useful engagement. Discovery is not a disguised proposal presentation. It is a disciplined attempt to understand before committing the client or consultant to work.

This guide focuses on diagnosing a client situation. It differs from AI meeting notes for consultants, which is about capturing and reviewing client conversations after the meeting structure is chosen.

Start with the trigger, not the solution

Ask, “What happened that made this worth addressing now?” The answer reveals urgency, recent events and who is paying attention. Follow with, “Can you walk me through the most recent example?” Concrete examples expose the distance between a broad label and operational reality.

Useful opening questions include:

• What prompted this conversation now?
• What problem are people currently trying to solve?
• Who experiences it directly?
• What happened the last time it occurred?
• What has already been tried?

Do not reward dramatic language with an immediate recommendation. First establish what is observed and what is inferred.

Define the problem in observable terms

“Communication is broken” could mean delayed approvals, contradictory instructions, missing information or low trust. Ask questions that produce observable conditions:

• What should happen that does not happen today?
• Where in the workflow does the gap first appear?
• How often does it occur, and how is that known?
• What is the practical consequence?
• When does the process work well?
• What would disconfirm your current explanation?

The last two questions are especially valuable. Exceptions reveal enabling conditions, while disconfirming evidence prevents discovery from becoming confirmation theatre.

Identify outcomes and non-goals

Ask the client to describe a better state before discussing deliverables:

• What should be different for which people?
• What decision or behaviour should become easier?
• What evidence would make the work worth continuing?
• What must not worsen while this changes?
• What is explicitly outside this engagement?
• If nothing changes, what is the likely consequence?

A deliverable such as a workshop, dashboard or strategy is not the outcome. Use the SMART goals examples to make outcomes testable, but resist false precision when no reliable baseline exists.

Map stakeholders and decision rights

Do not ask only who “the stakeholders” are. Clarify the role each person plays:

• Who owns the current process?
• Who experiences the problem?
• Who controls required resources or data?
• Who can approve a change?
• Who could block implementation, and on what legitimate grounds?
• Whose perspective is missing from this conversation?
• Who will own the result after the consultant leaves?

Avoid personality labels and speculation about motives. Record decision rights and observable concerns. Handle personal data and sensitive workplace information under the client’s appropriate governance process.

Test evidence and baseline quality

Ask how the client knows the problem exists and how each measure is defined:

• What evidence supports the current view?
• Where does the data come from?
• What period and population does it cover?
• Has the definition changed?
• What relevant evidence is unavailable?
• What qualitative accounts contradict the aggregate?
• Who can verify the baseline?

Do not fabricate an industry benchmark to fill a gap. A transparent “baseline unavailable; first phase will establish it” is more useful than an impressive but irrelevant comparison.

Explore constraints without treating them as excuses

Constraints define the feasible solution space. Ask:

• Which deadlines are fixed, and what makes them fixed?
• What budget, capacity or procurement limits apply?
• Which systems, contracts or policies cannot change now?
• What security, privacy, accessibility or regulatory review is required?
• What internal initiatives compete for the same people?
• What would make a technically good solution unusable?

This checklist does not establish legal, regulatory, security, accessibility, safety or professional sufficiency. Specialist owners should assess applicable requirements.

Understand previous attempts

Previous work prevents the consultant from proposing a renamed version of something that already failed. Ask:

• What has been tried, by whom and for how long?
• Which parts helped?
• Where did adoption or delivery stop?
• What assumptions guided that approach?
• What changed afterward?
• Is any useful asset or learning reusable?

Discuss failure without turning discovery into an employee evaluation. Systems, incentives, dependencies and timing often matter as much as individual action.

Ask about change readiness and ownership

A proposal is weak if nobody can own the change. Explore:

• Who will make time for the work?
• Which decisions can the project team make independently?
• How will affected people contribute?
• What communication channels already work?
• How will disagreements be resolved?
• What early result would build confidence?
• Who maintains the change after handover?

If ownership remains vague, make that a proposal condition rather than hiding it in project risk language.

Use a structured 45-minute discovery flow

DISCOVERY CALL — 45 MINUTES

1. Trigger and desired decision — 5 min
2. Recent concrete example — 8 min
3. Outcomes and non-goals — 7 min
4. Evidence and baseline — 7 min
5. Stakeholders and constraints — 7 min
6. Previous attempts and risks — 5 min
7. Summary, gaps and next step — 6 min

Facts heard:
Interpretations to test:
Open questions:
Commitments:
Next decision and owner:

Use the structure as a route, not an interrogation script. Follow important evidence, explain why sensitive questions are relevant and allow the client to decline.

Capture agreed conversations responsibly

If an in-person client conversation would benefit from a reviewable source, ask before recording and explain purpose, access, retention and alternatives. Consent and professional duties depend on the people, location and engagement; obtain appropriate guidance rather than treating a template as authorization.

Need to revisit an explicitly agreed in-person discovery conversation? Kuno supports visible capture and draft notes for human review, without replacing the consultant’s judgment. Explore Kuno

The source should support listening, not justify collecting everything. Exclude unnecessary sensitive detail, protect access and verify every generated statement before use.

Synthesize before proposing work

After discovery, create a short problem brief:

Observed condition:
Affected people / process:
Desired outcome:
Evidence and limitations:
Likely contributors (hypotheses):
Constraints and non-goals:
Open questions:
Decision required:
Recommended next diagnostic step:

Use note taking and outlining to separate capture from structure, then apply the objective summary method before adding recommendations. Send the client the consequential parts for correction.

Decide whether to propose, investigate or decline

Discovery can lead to three legitimate outcomes. Propose work when the problem, ownership and feasible next step are sufficiently clear. Recommend a bounded diagnostic phase when key evidence is missing. Decline or refer when the work falls outside competence, creates unmanaged conflicts or requires specialist authority you do not have.

End with a specific next decision, not “we will circle back.” A useful discovery process reduces uncertainty honestly; it does not manufacture certainty to make a proposal easier to sell.

Keep discovery grounded in what was actually said. Kuno can support consented room capture, while the consultant and client verify the brief and remain accountable for every recommendation. See Kuno