Lesson 6 · Deck, Demo, and Executive Conversation

Deck, Demo, and Executive Conversation

Length: 23 minutes across 7 sections
You will be able to apply: The Narrative Spine · The Demo Contract
You will produce: Commit Statement
You will work: 4 gated questions

Reading

Which single decision should advance by the end of this meeting, and what is the minimum material required to make that decision possible?
Core question

A meeting is not a presentation. It is a decision environment. The deck frames the decision. The demo proves the mechanism. The executive conversation confirms the next step. When sellers measure a meeting by how much material they covered, they optimise for throughput. When they measure it by which decision advanced, they optimise for outcome. Only one of those measurements closes deals.

You treat every buyer-facing session as a decision event with a defined entry condition, a single narrative arc, and a committed next step. The deck builds the case. The demo proves the claim. The executive conversation converts both into a governed decision. If any element runs without a confirmed problem to address, it consumes time without advancing the deal.

Next: The pathology: Slide Completeness

Section 2 of 7

The pathology: Slide Completeness

PrincipleSlide Completeness is the reflex of measuring a meeting by how much material was covered rather than which decision advanced. It appears when a seller builds a forty-slide deck for a thirty-minute window, races through capability slides to reach the end, or feels the meeting failed because seven slides were skipped. The tell is anxiety about uncovered content rather than curiosity about the buyer's decision. It is not thoroughness. It is avoidance of the harder question: did the buyer move?

The counter is narrative minimalism. You build the fewest slides that carry the argument, sequence them so any slide can be removed without breaking the logic, and enter the meeting knowing which slides you will cut if the conversation shifts. Selma Whitfield at OmniCorp Advisory enforces a rule: no deck exceeds the number of minutes divided by three. A thirty-minute meeting gets ten slides maximum. Not ten slides minimum. Ten slides maximum.

Interactive modelSlide Completeness versus decision focuscontrast · 2 elements

Slide Completeness

Anxiety about uncovered content; success means reaching the last slide.

The measure of a meeting is which decision advanced, not how much material was covered.

Slide Completeness: Anxiety about uncovered content; success means reaching the last slide.
Decision focus: Curiosity about the buyer's movement; success means a named next step with an owner and date.

Next: The Narrative Spine

Section 3 of 7Framework

The Narrative Spine

Definition

The Narrative Spine is the method for building a presentation around five elements in fixed sequence: one problem, one consequence, one mechanism, one proof, one decision. Each element earns the next. The problem establishes relevance. The consequence creates urgency. The mechanism explains how the problem is resolved. The proof demonstrates that the mechanism has worked before. The decision names the next step the buyer should take.

The spine is deliberately minimal. It carries only what the buyer needs to make the next decision. Every slide maps to one element. If a slide does not serve problem, consequence, mechanism, proof, or decision, it is decoration. Decoration consumes time without advancing the deal. Remove it.

When to Use It

Use the Narrative Spine for every buyer-facing presentation: first meetings, proposal reviews, executive briefings, steering updates, and renewal conversations. Use it when you have five minutes with a chief executive and when you have sixty minutes with a working committee. The length changes. The structure does not.

Do not use it for internal planning sessions where the goal is exploration rather than decision. The spine is built for external moments where the buyer's time is finite and the outcome is a commitment. Internal workshops afford divergence. Buyer meetings do not.

How to Apply It

Write the problem in one sentence using the buyer's language from discovery. If you cannot, you have not finished discovery.
Write the consequence: what happens to the buyer if the problem persists for another two quarters? Name the cost in units the buyer measures.
Write the mechanism: how does your solution resolve this specific problem? One sentence. No feature list.
Write the proof: which named engagement or delivery evidence demonstrates that the mechanism has worked before?
Write the decision: what is the single next step, who owns it, and by when?

Map your slides to these five elements. If you have more than two slides per element, you are adding decoration. Cut until the argument is clean.

Interactive modelNarrative Spine sequenceflow · 5 elements

Problem

Establishes relevance by naming the buyer's confirmed pain.

Each element earns the next; removing any one breaks the logic that makes the decision land.

Problem: Establishes relevance by naming the buyer's confirmed pain.
Consequence: Creates urgency by naming the cost of inaction.
Mechanism: Explains how the problem is resolved.
Proof: Demonstrates the mechanism has worked before.
Decision: Names the next step, owner, and date.

Worked example 1 of 3

Camille Okafor prepared a twenty-minute executive briefing for Miriam Ashworth, group chief executive at OmniCorp Group. She built six slides. Slide one: OmniCorp Group deployed AI in three operating companies without unified governance. Slide two: regulatory exposure across jurisdictions and inconsistent risk controls the board could not oversee. Slide three: a cross-group governance programme embedding operational controls into each operating company's decision-making. Slide four: proof from two comparable multi-entity programmes achieving board-level oversight within twelve weeks. Slide five: approve a six-week scoping engagement with named deliverables. Slide six: timeline and ownership.

Miriam cut the meeting to fifteen minutes. Camille dropped slide four and delivered the proof verbally in one sentence. The spine held because every slide earned the next. No logic gap appeared when proof moved from visual to verbal. The decision advanced.

Why This Works

The spine works because it aligns with how executives process information. An executive scans for relevance, cost, mechanism, and ask. The spine delivers those elements in the order she needs them, without requiring her to extract them from a feature tour. The decision lands because it was earned by the argument, not appended after a product walkthrough.

It also survives interruption. If a senior leader interrupts at slide three to ask what you need from me, you answer immediately because the decision slide exists and the spine has already framed the justification. A feature-tour deck cannot survive that interruption because the ask has no context until all capabilities have been presented.

Worked example 2 of 3Optional depth

Dev Raghunathan prepared a proposal review for Adaeze Okonjo, chief risk officer at OmniCorp Financial. Problem: consumer lending operated AI-assisted case preparation without model-risk governance controls. Consequence: regulatory examination in the next quarter could surface an uncontrolled decision path. Mechanism: an eight-week programme embedding governance controls into the lending workflow. Proof: three comparable programmes passed regulatory review within the delivery window. Decision: approve the statement of work and assign Martin Hollis as operational owner. Adaeze approved in the meeting because the spine gave her the risk frame, the evidence, and the ask in sequence.

Worked example 3 of 3Optional depth

Owen Brackley presented to Yusuf Demir, vice president of network operations at OmniCorp Logistics, and Claire Beaumont, head of dispatch systems. Problem: dispatch optimisation decisions ran without governance controls, creating operational risk in late-route handling. Consequence: three incidents in the previous quarter escalated to regional management because no governance review existed at the decision point. Mechanism: embedding governance checkpoints so exceptions surfaced before they became incidents. Proof: one comparable logistics programme reduced escalations by 60 percent in the first operational quarter. Decision: approve a scoping session with Anders Nilsen, platform engineering lead, to map integration requirements. Yusuf approved the scoping session in the meeting.

Edge Cases and NuancesOptional depth

When the audience is a working committee rather than a single executive, the spine still applies but the proof element expands. Committee members need evidence relevant to their function. The proof becomes two slides: one for the operational audience, one for the control audience. The spine tolerates this expansion because it serves the decision.

When a meeting is cut short, the spine provides a clear skip order: proof can be delivered verbally, consequence can be acknowledged rather than presented, and mechanism can be summarised in one sentence. The one element you never skip is the decision. A meeting that ends without naming the next step, owner, and date has consumed time without producing value.

Knowledge check

A senior executive interrupts at slide three and asks what you need from her. You have not yet shown your proof slide. What does the Narrative Spine allow you to do?

Answer first, then check.

Next: The Demo Contract

Section 4 of 7Framework

The Demo Contract

Definition

The Demo Contract is the agreement established before any live demonstration that specifies what will be shown, to whom, against which confirmed problem, with the success criterion and the follow-up decision agreed before the session begins. It converts a demonstration from a product tour into a governed proof event. Without the contract, a demo is entertainment. With it, a demo is evidence.

The contract has five terms: the confirmed problem being addressed, the audience and their decision authority, the specific capability being demonstrated, the success criterion the audience will use to evaluate, and the next decision that follows if the criterion is met. All five are confirmed with the buyer before the session. If any term is missing, the demo is not ready.

When to Use It

Use the Demo Contract before every live demonstration, technical proof of concept, sandbox walkthrough, or recorded capability presentation. Use it for ten-minute embedded demos within a broader meeting and for sixty-minute dedicated technical sessions. The duration varies. The contract does not.

Do not use it for informal exploratory conversations where the buyer asks to see something on the spot. In those moments, name the limitation: I can show you a general view, but a proper demonstration against your confirmed problem requires a structured session. That protects both parties from evaluating capability against an unconfirmed context.

How to Apply It

Confirm the problem in the buyer's language. Do not demonstrate until the problem is stated and the buyer agrees it is the problem they need solved.
Confirm the audience and their decision authority. Know who will evaluate and who will decide based on the evaluation.
State the capability you will demonstrate. Name what you will show and what you will not show. Boundaries prevent scope drift.
Agree the success criterion. Ask the buyer: what would you need to see to confirm this addresses your problem?
Agree the follow-up decision. Ask: if the demonstration meets the criterion, what is the next step and who owns it?

The contract is a conversation, not a document. It takes three minutes at the start of the session. Those three minutes save thirty minutes of unstructured demonstration and two weeks of ambiguity.

Interactive modelDemo Contract termsstack · 5 elements

Follow-up decision

The next step that follows if the criterion is met.

All five terms are confirmed with the buyer before the demonstration begins; if any is missing, the demo is not ready.

Follow-up decision: The next step that follows if the criterion is met.
Success criterion: How the audience will evaluate the demonstration.
Capability shown: The specific feature demonstrated and its boundaries.
Audience authority: Who evaluates and who decides based on the evaluation.
Confirmed problem: The problem in the buyer's language that the demo addresses.

Worked example 1 of 3

Owen Brackley prepared a demonstration for Nadia Farouk, director of digital services at OmniCorp Public, and Theo Lindqvist, records and privacy officer. The confirmed problem: citizen service requests triaged manually, creating delays and inconsistent routing. The audience: Nadia had decision authority for service operations; Theo had veto authority for records compliance. The capability: AI-assisted triage with governance controls showing how routing decisions were logged and reviewable. The success criterion Nadia stated: show me that the triage logic is transparent and that Theo can audit any decision. The follow-up decision: if met, Grace Mutiso, service owner, would schedule a scoping session for a controlled pilot.

Owen Brackley: Before I show anything, let me confirm the contract. The problem is manual triage delay. I will show governance-controlled AI routing with full audit visibility. Nadia, your criterion is transparency and auditability. If this meets the mark, the next step is Grace scheduling a scoping session. Does that match your expectation?
Nadia Farouk: That matches. Theo, does the audit criterion cover your records requirement?
Theo Lindqvist: I need to see that the retention policy applies to every logged decision. If that is visible, I am satisfied.
Owen Brackley: I will show retention policy enforcement as part of the audit trail. If it is not clear, tell me during the session and I will address it before we close.

Why This Works

The contract works because it eliminates ambiguity about evaluation. Without it, the buyer watches a demonstration and says interesting, let me think about it. With it, the buyer says the criterion was met or it was not. Binary evaluation produces binary decisions. Binary decisions advance deals.

It also protects the seller from scope drift. A buyer who agreed to evaluate one capability against one problem cannot fairly ask why you did not show five others. The contract establishes the boundary before the session and makes deviation a conscious choice rather than an unconscious expectation.

Worked example 2 of 3Optional depth

Camille Okafor ran a demonstration for Priyanka Venn, group chief financial officer at OmniCorp Group. The confirmed problem: group-level AI spend lacked a governed oversight mechanism. The audience: Priyanka held budget authority. The capability: a governance dashboard showing AI programme spend by operating company with risk-weighted decision flags. The success criterion: Priyanka needed to see that spend visibility linked to risk categorisation, not just financial reporting. The follow-up decision: if met, Priyanka would approve the scoping engagement and assign a finance liaison. The demonstration met the criterion in fourteen minutes. Priyanka approved before the thirty-minute window closed.

Worked example 3 of 3Optional depth

Dev Raghunathan demonstrated to Bea Karlsson, model risk lead at OmniCorp Financial, and Martin Hollis, head of consumer lending. The confirmed problem: model-risk exceptions in consumer lending lacked a governance trail connecting the exception to the decision that produced it. The audience: Bea held model-risk veto authority; Martin owned the operational workflow. The capability: governance controls showing how each exception traced to a specific lending decision with full audit history. The success criterion Bea stated: show me that the trail is complete enough for regulatory examination. The follow-up decision: if met, Martin would assign his operations lead to a two-week integration assessment. The demonstration met Bea's criterion and Martin assigned the operations lead before the meeting ended.

Edge Cases and NuancesOptional depth

When a senior executive joins a demonstration unexpectedly, do not restart. State the contract in one sentence: we are demonstrating governance-controlled triage against the confirmed problem of manual routing delay, and the success criterion is transparency and auditability. That gives the executive full context in ten seconds. Then continue where you left off.

When the buyer changes the problem mid-demonstration, pause. Restate the original contract and ask whether the buyer wants to proceed or reschedule against the new problem. Continuing against an unconfirmed problem produces ambiguous evaluation. Ambiguous evaluation produces no decision. No decision costs you two weeks and one meeting slot.

Knowledge check

A demonstration ends with the buyer saying interesting, let me think about it. No next step is named. Which Demo Contract term was most likely missing?

Answer first, then check.

Decision point

You are seven minutes into a fifteen-minute demonstration for Colm Byrne at OmniCorp Health when Dr. Ilona Reyes joins unexpectedly and asks you to start from the beginning. You have eight minutes remaining. What do you do?

Write your answer before you continue

Confidence before seeing the analysis

What evidence or assumption could change your decision?

Commit, calibrate, and name contrary evidence first.

Decision point

Ingrid Solheim at OmniCorp Retail asks you to demonstrate a capability that was not part of the confirmed Demo Contract. The request is reasonable but the capability has not been prepared for this audience. What do you say?

Write your answer before you continue

Confidence before seeing the analysis

What evidence or assumption could change your decision?

Commit, calibrate, and name contrary evidence first.

Next: Common Failure Modes in Deck and Demo Delivery

Section 5 of 7

Common Failure Modes in Deck and Demo Delivery

Failure modeFeature tour. What it looks like in the moment: the seller moves through capability slides sequentially, demonstrating each feature without connecting it to the confirmed problem or asking whether the buyer finds it relevant. The cost when this happens: the buyer sees fifteen capabilities, remembers two, and cannot explain the value to their internal stakeholders. The deal stalls for three weeks while the buyer asks for a shorter summary. The correction: map every slide and every demo moment to one element of the Narrative Spine. If it does not serve problem, consequence, mechanism, proof, or decision, remove it.

Failure modeMissing contract. What it looks like in the moment: the seller launches into a demonstration without confirming the problem, audience authority, success criterion, or follow-up decision. The demonstration runs smoothly but ends with interesting, let me think about it. The cost when this happens: two weeks pass with no next step, and the seller must schedule another meeting to achieve what the first meeting should have produced. One deal cycle extends by fourteen days. The correction: spend three minutes at the start of every demonstration confirming the five terms of the Demo Contract.

Failure modeRestart for the executive. What it looks like in the moment: a senior leader joins mid-meeting and the seller restarts the presentation from slide one, consuming the remaining time on context the working team has already absorbed. The cost when this happens: the decision slides are never reached, the meeting ends without a next step, and the deal cycle extends by one week while the seller reschedules to reach the ask. The correction: state the contract in one sentence, continue from the current point, and schedule a separate recap if the executive needs deeper background.

Failure modeUnprepared capability demonstration. What it looks like in the moment: the buyer asks to see something not in the contract and the seller attempts to demonstrate it without preparation, producing a confused walkthrough that raises more questions than it answers. The cost when this happens: the buyer forms a negative impression of a capability that was never properly positioned, and the seller spends two additional meetings correcting the impression, costing one full week of deal momentum. The correction: acknowledge the interest, decline to demonstrate without preparation, and schedule a structured session against the new question with a proper Demo Contract.

Failure modeDecision-free meeting. What it looks like in the moment: the presentation is delivered, the demonstration runs, questions are answered, and the meeting ends with thank you, we will be in touch. No next step is named, no owner is assigned, no date is set. The cost when this happens: the deal enters a two-to-four-week drift where neither party has a commitment, and the seller must manufacture a reason to re-engage. One meeting slot and 60 dollars of preparation time are consumed without advancing the decision. The correction: end every meeting by stating the next step, the owner, and the date. If the buyer will not commit to a next step, name that explicitly and ask what would need to be true for a decision to advance.

Next: Worked scenario: OmniCorp Logistics executive presentation

Section 6 of 7

Worked scenario: OmniCorp Logistics executive presentation

Owen Brackley prepared a thirty-minute executive presentation and embedded demonstration for Yusuf Demir, vice president of network operations at OmniCorp Logistics, Claire Beaumont, head of dispatch systems, and Anders Nilsen, platform engineering lead. The objective: secure approval for a scoping engagement to map governance controls into the dispatch decision layer.

Owen built the Narrative Spine. Problem: dispatch optimisation decisions ran without governance checkpoints, producing escalations that consumed regional management time. Consequence: three escalations in the previous quarter each required eight hours of senior management attention and one resulted in a customer SLA breach. Mechanism: governance controls embedded at the dispatch decision point, surfacing exceptions before they became incidents. Proof: one comparable logistics programme reduced escalations by 60 percent in the first operational quarter. Decision: approve a two-week scoping session with Anders to map integration requirements.

Owen mapped seven slides to the spine. Two for problem and consequence. Two for mechanism. One for proof. One for the demonstration setup. One for the decision. He set the Demo Contract with Claire before the session: the confirmed problem was uncontrolled dispatch exceptions, the success criterion was visibility into exception governance before escalation, and the follow-up decision was Anders scheduling the scoping session.

In the meeting, Yusuf interrupted at slide four to ask what Owen needed from him. Owen moved directly to the decision slide: a two-week scoping session with Anders, funded from existing operational budget, with a defined deliverable of an integration requirements map. The spine held because every prior slide had earned the ask. Yusuf approved. Claire confirmed the success criterion was met by the three-minute embedded demo. Anders scheduled the scoping session before the meeting ended. Total time used: twenty-two minutes. Eight minutes returned to the buyer.

Mark the level that describes you today. Nothing is submitted.

Behaviour	Ready	Developing	Not yet
Building to the Narrative Spine	In the OmniCorp Logistics scenario, maps every slide to one spine element, cuts when Yusuf interrupts, and reaches the decision without losing logic because the spine carried the argument.	Builds a spine-aligned deck but includes two additional capability slides that do not map to any element, requiring extra time and making the interruption harder to navigate.	Builds a feature-tour deck with no narrative sequence, cannot skip slides without losing context, and fails to reach the decision slide when the meeting is cut short.
Establishing the Demo Contract	In the same OmniCorp Logistics scenario, confirms the five contract terms with Claire before the session and delivers a focused three-minute demonstration against the confirmed criterion.	Confirms the problem and audience but does not state the success criterion or follow-up decision, leaving evaluation ambiguous after the demonstration.	Launches into the demonstration without any contract, shows multiple capabilities, and ends with no clear evaluation or next step.
Reaching the decision within the time window	In the same OmniCorp Logistics scenario, reaches the decision in twenty-two minutes when Yusuf interrupts, names the next step, owner, and date, and returns eight minutes to the buyer.	Reaches the decision but runs to the end of the thirty-minute window without buffer, leaving no time for buyer questions or confirmation of ownership.	Consumes the full thirty minutes on slides and demonstration, never reaches the decision, and ends with we will follow up by email, extending the deal cycle by two weeks.

Next: Commit

Section 7 of 7

Commit

Commit Statement

Complete the lines below before your next buyer-facing presentation. Use the meeting where you most recently failed to advance a decision. Sign it and review it with your manager.

I commit to

I will stop

I will start

I will know I succeeded when

Signed Date

Window	Field application
Days 1 to 7	Select your next buyer presentation. Build the Narrative Spine: problem, consequence, mechanism, proof, decision. Map every slide to one element and remove any that do not serve the spine.
Days 8 to 14	Prepare the Demo Contract for your next demonstration. Confirm all five terms with the buyer before the session. Record whether the follow-up decision was reached.
Days 15 to 21	Review your last three meetings. For each, identify whether a decision advanced or whether the meeting ended without a named next step, owner, and date. Diagnose the failure mode.
Days 22 to 30	Deliver a full spine-aligned presentation with embedded demonstration and Demo Contract. Record the outcome and review with your manager against this lesson's rubric.

DisclaimerGeneral guidance only. All organisations and people named in this lesson are fictional, including OmniCorp Advisory, OmniCorp Group, OmniCorp Financial, OmniCorp Health, OmniCorp Retail, OmniCorp Logistics, and OmniCorp Public. Competitive claims and demonstration material must be approved by commercial counsel before external use. Outcomes described are instructional and must not be presented as guarantees or typical results.

Required practice must be complete.