Module 9: Applying It in Discovery Calls

This module translates the framework into a working playbook for actual presales and delivery discovery, assuming multiple stakeholders as the default case, not the exception.

Before the Call

• Identify every stakeholder expected on the call (or relevant to the topic even if not attending) and their likely standing on each agenda topic.
• Review known context and pre-tag anything already known: what’s confirmed L2, what’s still narrative, what’s provisional pending a standing stakeholder.
• Flag likely conflict points between departments in advance (e.g., finance’s close-process needs vs. sales ops’s deal-velocity needs) so they’re recognized as conflict, not mistaken for confusion, when they surface.

During the Call

• Run Step 0 (note the speaker) before the altitude ladder, for every substantive statement.
• Let L0/L1 material flow naturally — this is rapport-building and shouldn’t be rushed.
• Watch for the Module 4 tells for all three failure modes.
• Deploy bridge statements at natural topic boundaries, naming whose position is being synthesized once more than one stakeholder has spoken on a topic.
• When two stakeholders’ statements appear to conflict, apply the Module 7 test: step up to L1 and check whether this is genuine conflict or a coverage gap that looks like one.
• When a client offers an L3-shaped detail before any L2 statement exists, resist following it — note it, and return once the bridge is confirmed.
• Log genuine conflicts explicitly and note who has authority to resolve them.

After the Call

• Update the stakeholder map: which topics have a confirmed, standing-appropriate L2 statement, which have flagged conflicts awaiting escalation, which still need a standing stakeholder to weigh in at all.
• Mark any L2 statement from someone without clear standing as provisional until confirmed by the right owner.
• Only once L2 statements exist for a topic should L3 detail-gathering be scheduled for it.

Domain-Specific Watch Points

• Pricing/plan changes: finance and sales frequently hold genuinely different L2-level positions here (finance wants margin protection, sales wants deal flexibility) — expect real conflict, and route it to whoever owns pricing policy rather than splitting the difference yourself.
• Integration triggers: the “which system is the source of truth” ambiguity is often itself a standing question — IT may have more actual authority here than the department requesting the integration.
• Multi-entity/multi-currency billing: frequently surfaces from one regional stakeholder as an aside, with no one else aware it’s a requirement — a strong candidate for “apparent gap, not conflict,” since it’s usually missing coverage rather than disagreement.

Worked Example — Annotated Call Excerpt (Composite)

Before the call: Practitioner knows Sarah (Finance), Marcus (Sales Ops), Priya (IT), and Dana (CS Ops) are attending; flags in advance that Finance/Sales may conflict on discount authority. During the call: Sarah opens with the L0 (billing errors costing renewals). Marcus adds L1 (no visibility after close). Practitioner bridges: confirmed L2 on auto-sync. Marcus raises the override question — practitioner recognizes standing on both sides, doesn’t resolve it in the room, logs it as a conflict for escalation. Priya’s source-of-truth question surfaces the two-way reconciliation gap (Module 6). Dana’s aside about EU billing in euros gets parked as a likely coverage gap, not chased into detail immediately. After the call: Stakeholder map updated (Module 7’s table above); auto-sync L2 marked “advised” pending Sarah’s revision; discount-override topic marked “conflicted”; multi-currency topic marked “not yet translated.” Next: Module 10 — From Tagged Notes to the Requirements Document.