Scenario Library
6 scenarios. Six categories. One skill.
Technical correctness does not automatically create alignment.
Category
Complexity level
Available now
The Vague Ask
A Product partner asks Engineering for “just a little help” on an urgent launch issue. The ask is warm, vague, and expanding.
The Premature Commitment
A Product leader wants a firm launch date in front of stakeholders — before engineering confidence exists.
The Public Challenge
A Design partner challenges your engineering solution in front of a larger meeting. Eyes turn to you.
The Yellow Project
A project is quietly trending late. Leadership still thinks it's green. The window to surface it is closing.
The Missed Deliverable
A teammate missed a commitment your work depended on — again. You need to give feedback that fixes the pattern, not just the moment.
The AI Draft
An AI-generated message is fast, precise, and technically airtight — and likely to damage a partner relationship.
In development
The Reorg Rumor
A reorg rumor is spreading and your team is anxious. You know little, and what you say will travel.
The Quiet No
A senior leader 'suggests' a direction you think is wrong. Compliance is easy; judgment is costly.
The Credit
A peer presented your team's work as their own to leadership. The room believed it.
The Model Said So
An AI analysis recommends a decision the whole team is uneasy about, but no one can fault the logic.
Two Rooms, Two Stories
Leadership and your team have two different versions of the same status. You sit between them.
Setting the Standard
A shortcut would hit the date and quietly lower the bar for everyone who comes after you.