Volume I · Capstone · Lesson 1
Everything At Once
Four days until the roadmap locks, and four people with four reasons it should change.
Judgment0 judgment
←→ to move through the storySwipe or use the arrows to move through the story
01 / 16
Four days until the roadmap locks, and four people with four reasons it should change.
←→ to move through the storySwipe or use the arrows to move through the story
Everything At Once — Volume I, Understanding Humans Before Products · Capstone · Dilemma · Practitioner. Three angry accounts, a survey, a metric that moved and a deadline all point different ways on the same decision, and Maya has to choose which question to ask first
01 · Opening
Four days until the roadmap locks, and four people with four reasons it should change.
02 · The setup
Thursday. The roadmap is locked on Monday and four people have four reasons why it should not be.
Sam: Three enterprise accounts have escalated on bulk permissions. I need it in the plan.
03 · The setup
On the table, Thursday — Escalated accounts: 3; Survey asking for it: 18% of 900; Permissions errors since release: up 40%; Days until lock: 4
04 · The evidence
Priya: The survey has it fourth out of eleven. Not nothing, not the top.
05 · The evidence
Dev: Permissions errors are up forty percent since the March release. That might be the same thing or a different one.
06 · The evidence
Four instruments, four directions. Maya recognises every one of them and that is the problem.
Maya thinks: Denominator says three of nine hundred. Value says check what they hold up. Both are right and they disagree.
07 · You make the call
The story does not tell you first.
A. The instrument with the largest sample
B. Whichever question could make the others irrelevant
C. The escalations, because revenue is at risk
08 · What happened
Maya: Which of these could make the others not matter? That is the one I ask first.
09 · What happened
Dev's error rate is the only item that might mean the feature is not the question at all.
Maya: If March broke something, then nobody wants bulk permissions. They want the old behaviour back.
10 · What happened
One afternoon. The error spike is checked before anything else is argued about.
Permissions errors since March — Errors up: 40%; Accounts affected: 2 of the 3 escalated; Cause: March role migration; Fix estimate: 3 days
11 · What happened
Maya: Two of your three are not asking for a feature. They are asking us to undo a bug.
Sam: And the third?
12 · What happened
Maya: The third is a real request and it can wait a quarter.
13 · What happened
By the end of a volume you have several instruments and they will routinely disagree, because each was built for a different question. Reaching for the one you trust most is how a toolkit becomes a habit.
The ordering rule is simple and almost never applied: ask first whichever question could make the rest not matter. A broken thing being mistaken for a missing thing does that to every other input on the table, so it goes first regardless of who is arguing loudest.
Notice what this is not. It is not picking the best tool, and it is not weighing the evidence. It is sequencing — and the four days that felt like a constraint were plenty, because the first question only took an afternoon.
14 · What happened
The migration fix ships in three days. The roadmap locks on Monday without bulk permissions in it, and nobody escalates again.
Sam: I was ready to spend a quarter on the wrong thing.
15 · What happened
Maya thinks: Every instrument was working. I nearly let the loudest one go first.
16 · Complete
When your tools disagree, the skill is sequencing rather than choosing — ask first whatever could make the rest not matter. Next: the last thing this volume can teach you, which is how to audit yourself.