1 min lesson

The scenario brief

Put this idea into your own words: "Read the brief once, then treat it as fixed."

One fictional account, four deliverables, one honest scorecard. This is the practical case the loop puts in front of you, simulated so you can fail it cheaply now instead of live.

Read the brief once, then treat it as fixed. Every later section is a timed artifact you produce against these facts - a 30/60/90, a stalled-rollout rescue, an EBR and an expansion play. The account is deliberately uncomfortable: a real Cursor deployment in a 2,000-engineer org never arrives clean.

Learn more

Full explanation

The Mock Loop, End to End

THE MOCK LOOP, END TO END

1/5

Scenario brief · fixed facts: Lock the Meridian account - 2,000 engineers, 600 signed seats, a VP Eng sponsor, a champion, a pending security review and an incumbent Copilot deployment. Restate the charter as the three numbers (activation, adoption, retention/expansion) before you plan anything.

diagram: loop-timeline

Five stages on one account - produce each as a timed artifact, then grade yourself.

Account: Meridian Systems

Size: 2,000 engineers across 9 business units; recently signed a 600-seat enterprise agreement
Champion: Platform/DevEx team lead who ran the eval and wants this to work
Sponsor: VP Eng - single executive sponsor, holds the budget, skeptical of AI ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. Press Enter for the full definition. claims
Blocker: Security org has an open review: SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition./SAMLSecurity Assertion Markup Language. The XML-era enterprise standard that powers single sign-on: your identity provider vouches for you to each app. Older than OIDC but still what many enterprise tools speak. Press Enter for the full definition., data retention and SOC 2 questions unanswered
Incumbent: GitHub Copilot deployed org-wide for ~18 months; uneven usage, no formal program
Telemetry: You have admin analytics: seats provisioned vs. activated, Tab and Agent usage, acceptance signals

Hold these facts constant across all six sections. Do not invent new ones to make a deliverable easier.

The scenario brief

Step 1 of 3

The Mock Loop, End to End