End Discovery With a Decision and a Clear Purpose

Discovery should finish with a decision about work, people, and purpose. A broad product tour rarely supplies such a decision. A buyer might accept one to stay polite, then arrive with a different colleague and no shared question. Both sides leave busy, yet no closer to a choice.

Use the middle and final minutes of discovery to sort what you heard. Separate a stated problem from a missing fact, a missing person, or an internal choice. Approval delays describe a problem. Whether finance needs a separate review route describes a missing fact. A finance process owner who was absent describes a missing person. A manager deciding where staff time belongs describes an internal choice. Each condition calls for a different next action.

Start this work before the closing minutes. Pause after a buyer explains a process and test your understanding in plain language. Say, “You described requests moving through email before a manager review. Which handoff creates the most pressure for your team?” Then wait. A buyer who names manager wait time gives you direction. A buyer who says every stage feels slow needs more exploration before any meeting proposal.

Look for detail behind broad language. “Our process differs” does not yet supply an agenda. Ask who begins a request, who approves, where records live, and what happens after a request stalls. Ask for one recent situation. Precise answers reveal whether a focused review would serve a real decision or only fill a calendar.

For example, a buyer says approvals pass through two managers and finance, while exceptions follow another route. Resist a general tour. Ask, “For one new request, which handoff worries you most?” If the reply is, “Finance needs a clear record before release,” your recap has an anchor. The next session has one question: does the proposed workflow support a visible finance review? Invite the finance process owner, use one fictional request, and reserve enough time to trace one route.

Name your understanding without turning a recap into a speech. Try, “I heard a wish to shorten manager wait time, and finance review is still open. Did I capture both points?” The buyer has room to correct your words. Such corrections matter. A clean correction now prevents a later meeting built around an issue nobody owns.

Offer a next step tied to one uncertainty. “Would a working session with the finance process owner help us inspect one approval route?” gives a buyer a reason to involve another person. “Would a demo help?” leaves agenda design with them. Buyers often choose an easy reply even when a product tour leaves the real concern untouched.

A product session fits when someone needs to see a workflow. Request a small starting example before scheduling. For approval work, ask for a fictional request, the people involved, and the moment when review changes. No confidential record is necessary. Your preparation then follows a buyer owned sequence instead of a familiar screen order. State what you will inspect and what decision should follow from the session.

Stakeholder discovery fits when someone outside the call owns a decision or holds essential context. Say, “Before we review options, would an introduction to the person responsible for finance review help us understand their criteria?” Keep this request narrow. You seek one person’s view of one decision. A crowded call often hides ownership rather than exposing ownership.

A technical review fits when a technical concern blocks movement. Ask which system connects to the workflow, who reviews fit, and what evidence they expect. Do not promise a result before a qualified technical specialist reviews details. Frame the meeting around an answerable question, such as whether a proposed connection supports a required handoff. Invite participants whose work bears directly on this question.

Internal planning time fits when the buyer understands the workflow yet lacks a reason to prioritize change. Ask what decision leaders need before they commit time or budget. They might need a picture of present effort, a planned deadline, or agreement about whose work deserves attention first. Avoid invented savings or outcomes. Help the buyer organize their own observations for an internal conversation.

Sometimes no meeting belongs on the calendar. A buyer might say, “I need to speak with my manager first.” Respect this answer. Ask what they plan to discuss and what would make a later follow up useful. Agree on a short recap, then a check in after their internal discussion. Pressure for a demo at this point creates activity without evidence of readiness.

Use your notes to keep evidence separate from interpretation. Write the buyer’s exact concern beside the detail supporting the concern. For example, “finance needs a clear record” belongs beside “exceptions follow another route.” Then write one open question: “Does finance review need a separate route for exceptions?” This structure exposes a weak agenda before an invitation goes out. If no open question appears, return to discovery rather than scheduling.

Fictional practice situation: Morgan, a seller, speaks with Lee, who leads operations for a 40 person service group. Lee reports late approvals yet has no answer about finance review. Morgan asks which handoff receives complaints. Lee says managers approve routine work by noon, but exception requests wait until finance has a clear record. Morgan says, “Our next useful question concerns the exception route. Would you invite the finance review owner to a 30 minute working session?” Lee agrees and offers Tuesday morning.

Morgan checks who will bring context. Lee names Dana, who reviews finance requests, and explains Dana needs an example before accepting. Morgan asks whether a fictional request with one exception resembles normal work. Lee says yes. Morgan does not ask Lee to send a real request or promise what Dana will conclude. Their plan is limited: trace one fictional exception from submission through finance review and identify any unanswered process question.

Morgan sends a recap on the same day. The first sentence uses Lee’s language about the clear finance record. The second names Dana and Tuesday morning. The third states the purpose: trace one fictional exception request and inspect whether finance needs a separate route. Morgan leaves out product catalog language and a generic agenda. Dana receives enough context to decide whether attendance serves the meeting.

At the start of Tuesday’s session, Morgan opens with a blank process page and asks Lee to describe the fictional request. Lee says a supervisor submits an exception at 9:00. Dana says finance receives an email at 11:00 but lacks the manager note. Morgan writes those two times, circles the missing note, and asks Dana, “What record would let you complete review?” Dana answers, “A manager note linked to the request.” Morgan adds this phrase to the invitation notes, then asks Lee to bring a fictional manager note for their next working session.