Judgment · Lesson 12
Ambiguity, priorities, and deadlines
Expose how you frame unknowns, choose what not to do, manage risk, and update stakeholders.
What you will learn
- Expose how you frame unknowns, choose what not to do, manage risk, and update stakeholders.
Turn ambiguity into decisions
Name the unknowns, owners, and smallest useful test. Do not claim you removed uncertainty; show how you bounded it enough to act.
- Which unknown could reverse the plan?
- What could be learned cheaply?
- What decision could wait?
A deadline creates exclusions
A credible deadline story states what was cut, deferred, or degraded, who accepted the risk, and how the decision was communicated.
- What did you explicitly not do?
- Which quality floor stayed non-negotiable?
- How did stakeholders learn about the trade-off?
Launch versus reliability commitment
A small team faced a fixed customer pilot and unresolved retry behavior.
I worked harder and delivered everything on time.
I separated pilot-critical flows from two reporting features, kept the idempotency fix as the quality floor, and proposed deferring reports by one week. Product accepted the scope change after I showed the duplicate-charge risk and a manual reporting fallback.
- The rejected work is named.
- A risk-based quality floor is explicit.
- Decision authority and communication remain visible.
Reconstruct one deadline decision as a priority stack.
- 1List must-do, defer, and reject items.
- 2Name the risk and owner for each deferred item.
- 3Write the update you gave to a stakeholder.
Open the answer check
The answer should show judgment under constraint, not only effort or heroics.
Finish this lesson
Record completion when you have worked through the material. Completion is learning progress, not evidence of mastery.
Loading completion…