Skip to lesson
Exit
Capstone: Mock Loop1 / 2

1 min lesson

Demo B: for the CTO and VP Eng

Talk this through in your own words. "In Demo A for the skeptical principals, why is deliberately rejecting a weak Agent suggestion a stronger move than running a flawless, fully-accepted demo?" Finish with the next move.

Step 1 of 2

Demo B: for the CTO and VP EngROI and the strategic bet

  1. 1Frame the decision first. "You asked whether to go all-in. Here's what the bet looks like and how we'd know it's working by end of Q2."
  2. 2Show the outcome. One tight live moment, a real change shipped fast, then straight to the metric: cycle time, onboarding ramp, PR throughput.
  3. 3Tie it to delivery speed. Translate cycle-time gains into how much sooner changes reach customers at Northwind's scale. Anchor on their numbers from discovery.
  4. 4Address the strategic risk head-on. Name the privacy and governance posture before they ask, so the bet looks de-risked rather than reckless.
Dimension
Opens on
Principals (Demo A)
A real engineering task under their gates
Exec (Demo B)
The go/no-go decision and the bet
Dimension
Proof is
Principals (Demo A)
Live Agent/Rules workflow, tests green
Exec (Demo B)
A metric moving at their scale
Dimension
Their fear
Principals (Demo A)
AI degrades code quality
Exec (Demo B)
An expensive, risky mandate that flops like Copilot
Dimension
You win by
Principals (Demo A)
Rejecting bad output and respecting review
Exec (Demo B)
De-risking privacy and tying value to delivery speed

One product, two scripts. The audience decides what counts as proof.

Learn more

Optional practice

Test yourself on Demo B: for the CTO and VP Eng

QThe CTO and VP Eng join for Demo B. What should carry the proof?