We prep well — why do the messy, damaged cases still beat us?
Here is what is happening. You rehearse the smooth version of the work — the clean client, the working file, the calm handoff. It goes well. Then a real case shows up already cracked: someone furious before you start, data that's wrong, a teammate gone mid-project. And the team that handled the clean version falls apart on this one. This is not bad luck. It is a choice you made without noticing. The damaged case is unpleasant to imagine, so your group avoided imagining it. You practiced what was comfortable to practice. More of the same preparation will not fix this. Only one thing will: sitting down together and putting the ugly case on the table before it arrives, not after.
You don't fail on the hard cases. You fail on the ones already broken before you arrived. You trained for the clean version and skipped the ugly one — on purpose, because it was easier. Choose, as a group, to rehearse the damaged case out loud. That is the actual job.
What changes unlock by starting
- Your team stops calling messy cases bad luck and starts treating them as the real job.
- You build a shared library of rehearsed damaged cases you can pull from under pressure.
- Debriefs get sharper — less blame, more naming of exactly what broke.
- The gap between your best day and your worst day gets smaller.