Judgment · Lesson 09
Decision-making, alternatives, and trade-offs
Reconstruct what was known at the time and why a choice was reasonable under its constraints.
What you will learn
- Reconstruct what was known at the time and why a choice was reasonable under its constraints.
Avoid hindsight certainty
A good answer does not pretend the final outcome was obvious. State the options available, missing information, decision criteria, and risk controls at the moment of choice.
- What did you know then?
- Which alternative was credible?
- What reversible step reduced uncertainty?
Updating is evidence
Changing direction after new data can demonstrate judgment. Explain the trigger and how you protected the team from thrash.
- What observation changed the decision?
- Who needed to be re-aligned?
- What did you preserve from the original plan?
Sync versus async under burst risk
A team had to ingest partner updates before a fixed launch.
I chose Kafka because it scales better.
Synchronous processing was simpler, but partner bursts could hold request threads past our latency budget. I chose a queued path with idempotency keys, kept the initial consumer single-region, and defined a backlog threshold that would pause onboarding. A load test later changed the batch size, not the ownership model.
- A real alternative is acknowledged.
- Criteria and risk control are explicit.
- Later evidence changes a bounded part of the plan.
Build a decision table for one consequential choice.
- 1List two credible alternatives.
- 2Name the criteria and information available then.
- 3Identify the trigger that would have changed your decision.
Open the answer check
The chosen option should look reasonable under the original constraints even if the eventual result was imperfect.
Finish this lesson
Record completion when you have worked through the material. Completion is learning progress, not evidence of mastery.
Loading completion…