Sample simulation
A fictional run from briefing to evidence-backed debrief.
This sample shows the Simple Scenarios loop without requiring sign-in: players read a case packet, negotiate, submit artifacts, and the room resolves what the evidence earns.
Scenario
Enterprise AI Rollout
Human role
Product Lead
Practice target
Launch plan plus defensible controls
Run timeline
What changed and why
Briefing and role claim
- Evidence submitted
- The team opened with an AI governance case file, a pilot scope memo, a security risk register, and a customer-promise note.
- Resolved outcome
- Everyone understood the central tradeoff: move fast enough to keep the customer, but not beyond the controls security could defend.
Turn 1: scope pressure
- Evidence submitted
- Product proposed a narrow assistant pilot, Security demanded source restrictions, and Sales pressed for executive-visible proof.
- Resolved outcome
- The submitted package included a scoped launch plan and a first risk register, but support ownership stayed vague.
Turn 2: evidence closes the gap
- Evidence submitted
- Operations added escalation owners, Security added data-retention gates, and Sales rewrote the customer note with reversible language.
- Resolved outcome
- The resolver advanced pilot readiness because the artifacts connected promises, controls, and operating capacity.
Final turn: decision package
- Evidence submitted
- Final package bundled the launch memo, risk register, support playbook, and board update with clear owners and stop conditions.
- Resolved outcome
- The team won on goals first, rubric second: high readiness, acceptable security posture, and credible customer communication.
What a stronger team does
Turns talk into a package the room can score.
The best teams use chat to gather pressure and private context, but they win by submitting artifacts with owners, evidence, constraints, and clear decision language.