Ambiguity & Prioritization
Nobody hands senior engineers clean requirements. These questions check if you need them.
5 lessons · ~45 min · free
By the end you can
- Show autonomy: converting unclear asks into drafts, assumptions, and bets
- Describe triage with an explicit principle instead of raw effort
- Tell scope-cut stories where quality lines held and stakeholders knew
- Communicate deprioritization before it becomes a surprise
- Handle the deadline-pressure and changing-requirements variants
Lessons
Start the course- The autonomy check8 minWhat ambiguity questions predict, and the waiting-for-requirements answer that fails them.
- Turning fog into structure10 minDraft specs, stated assumptions, time-boxed spikes: the moves that make ambiguity workable.
- Triage with a principle9 minRanking by impact and blast radius, saying the ranking out loud, and telling the losers first.
- Cutting scope on purpose9 minValue-ranked cuts, quality lines that don't move, and making the tradeoff belong to stakeholders too.
- Building your ambiguity answers9 minMapping your projects to the variants, and rehearsing the judgment calls behind each.
The account is free and so is every lesson. It unlocks the courses and saves your progress.