Recipe for Disaster
A structured, tongue‑in‑cheek recipe that blends unclear requirements, unrealistic timelines, and unverified assumptions into a perfectly avoidable catastrophe.
Equipment
- 1 meeting room (virtual or physical)
- a shared document no one reads
- a communication channel everyone ignores
- a critical cable (unplugged)
- Optional: a whiteboard full of outdated notes
Ingredients
- 1 cup unclear requirements. Establish misalignment.
- 1 tbsp unrealistic timelines. Combine unrealistic expectations.
- a generous handful of assumptions. Introduce assumptions.
- 3–5 stakeholders who “skimmed the email.” Add stakeholders.
- 1 missing dependency (preferably critical). Insert critical failure.
- a pinch of overconfidence. Season with overconfidence.
- 1 Optional: person who says “it’ll only take five minutes.” Accelerate the timeline.
Instructions
- Preheat the environment by ensuring no one has the same understanding of the goal.
- In a large bowl, combine unclear requirements with unrealistic timelines. Stir until lumpy.
- Fold in assumptions slowly, making sure they remain unverified.
- Add stakeholders one at a time, allowing each to introduce a new constraint.
- Drop in the missing dependency without warning. Do not mix.
- Season with overconfidence. Taste and adjust denial as needed.
- Bring everything to a rapid boil by announcing a deadline.
- Serve immediately, preferably during a meeting that should have been an email.
Notes
- For a spicier version, substitute “last‑minute scope change” for assumptions.
- Disaster pairs well with finger‑pointing, post‑mortems, and lessons that will not be applied next time.
- 0 calories (because the only thing consumed is time and morale).
- Cost is incalculable (in money, and sometimes in consequences).
- Cook time: depends on how long it takes for someone to notice.
- Rest time: until the next crisis.
For a more intense disaster, add a last‑minute scope change or remove the only person who understood the system.