Present discovery as a structured way to understand a situation and decide what needs investigation next. State the questions, preparation, session format and record provided. Explain that a session may reveal missing evidence or a reason not to proceed, rather than guaranteeing a solution or a project proposal.
Define the uncertainty being explored
Begin with the kind of uncertainty the session addresses. Someone might know that internal onboarding is inconsistent but not know whether the problem concerns documentation, system access or responsibility. A discovery conversation can map the current account and identify missing information. It cannot responsibly promise to diagnose every cause from one meeting. Name the decision the session supports, such as whether a more detailed review is worth considering, rather than advertising instant certainty.
Identify who should attend and what they should bring. Ask for a concise description of the situation, relevant existing material and known constraints. Explain that participants should share only information they have permission to disclose. A useful preparation request makes the session more focused without turning an initial meeting into an unpaid full investigation. If reviewing substantial material is part of the offer, distinguish that work from simply receiving background context.
Describe the conversation and its record
Explain the broad structure: establish the situation, explore competing explanations, identify constraints and agree the next questions. Keep room for unexpected information. A rigid promise to produce a complete plan can encourage premature recommendations before the problem is understood. State how long the session is intended to last, whether preparation is included and whether recording is available only by agreement. Do not assume every participant is comfortable with a recording or transcription tool.
Describe the handover in proportion to the investigation. It might include a short summary of the situation as understood, assumptions to check and possible next actions. Mark unverified statements and distinguish participant reports from independently examined evidence. If the session is exploratory, say that its notes are not a full technical, legal or operational assessment. A clear record of uncertainty is more useful than a polished list of recommendations that obscures how little was examined.
Make the next decision optional
Explain that several outcomes are possible. The client may gather more evidence internally, seek a different specialist, proceed to a scoped project or decide that no external work is needed. If you may propose a further engagement, make that relationship visible without presenting it as the inevitable purpose of the session. Discovery should still produce the agreed record when the sensible conclusion is to stop or reconsider the original assumption.
Review the public description against the way you actually run sessions. A “free introduction” and a paid investigation may have different preparation and deliverables, so label them accurately. Keep availability and pricing information current, and tell people what happens after they submit a request. Do not promise immediate booking, a particular response time or confidentiality arrangements unless the actual process supports those commitments. The profile should invite an informed conversation about the session.
Fictional example: questioning the proposed solution
A fictional process consultant, Hana, receives an invented enquiry asking for an onboarding handbook. Her discovery-session description promises a structured discussion and a summary of open questions, rather than a finished handbook plan. During the illustrative conversation, the team describes several conflicting access procedures and cannot identify who approves them. Hana records policy ownership as an unresolved dependency.
The fictional handover suggests that the team first identify an internal decision owner and collect current procedures. A writing project may become appropriate later, but the session does not establish that documentation alone solves the problem. The example shows a legitimate stopping point for discovery and gives the client something usable without inventing a measured improvement or guaranteed subsequent engagement.
A checklist for your next step
- Name the uncertainty being explored.
- Specify participants and preparation.
- Describe the session and handover.
- Mark unverified assumptions.
- Allow a decision not to proceed.
Common questions
Must discovery end with a proposal?
No. A useful conclusion can be that more evidence, another specialist or internal work is needed first.
Is a brief introductory call the same as discovery?
Only if the stated purpose and work match. Distinguish a fit conversation from a paid investigation with agreed preparation and outputs.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.