# The 11pm Fix: Why Plans Fail on Monday — Pilot to Production

> Every plan looks good on Friday. Then Monday happens. What 11pm fixes teach you about planning, and how to build plans that survive reality.

Canonical: https://thegrowthproject.com/podcast/the-11pm-fix/

*Pilot to Production*, the Growth Project podcast — hosted by Sam and Maya.

- Listen: https://thegrowthproject.com/podcast/the-11pm-fix/
- Read the article: https://thegrowthproject.com/blog/the-11pm-fix/
- Audio: https://thegrowthproject.com/audio/podcast/the-11pm-fix.m4a?v=287ed0f1

## Transcript

**Sam:** Smart people, a whiteboard, boxes and arrows, clean timelines. Everyone nods. The plan is logical. It's thorough. It accounts for the major risks.

**Maya:** And then Monday happens, and reality wins. Every time.

**Sam:** Welcome to Pilot to Production, from the Growth Project. I'm Sam.

**Maya:** And I'm Maya. Today: why your Friday plan dies on Monday, and what an eleven pm fix teaches you that a whiteboard never can.

**Sam:** Okay, so what's actually wrong with the Friday plan? The energy is good, the deck looks professional.

**Maya:** Nothing's wrong with it on paper. That's the trap. The plan is built for the happy path. Reality isn't the happy path.

**Sam:** Give me Monday. What does Monday actually look like?

**Maya:** Start with the edge case nobody considered. Your plan assumed customers submit one order at a time. Your biggest customer uploads five hundred orders via CSV. The system chokes, the queue backs up, someone gets paged.

**Sam:** That's one. Keep going.

**Maya:** The integration that times out. The API worked in staging. Production has ten times the volume. Timeout settings are wrong, the retry logic is aggressive, and now you're DDoSing your own system.

**Sam:** We did that to ourselves once. It's humbling.

**Maya:** Then the human layer. The plan assumed Jess handles the data migration. Jess is in Fiji for her sister's wedding, and nobody else knows how the legacy system works.

**Sam:** And nobody planned for Jess having a life.

**Maya:** Right. And the workflow nobody documented. You're replacing the old order system, but there's a shadow process in accounting that depends on one specific export format. Nobody mentioned it, because nobody knew about it.

**Sam:** That's the one that gets you. The thing that isn't on any diagram.

**Maya:** And the permissions that don't exist. Deployment needs production database access. Ops needs forty-eight hours to provision credentials. The sprint ends in twenty-four.

**Sam:** So the post says these aren't even edge cases.

**Maya:** It says they're Tuesday. They're normal. And here's the kicker. Seventy percent of technology projects fail. Not because the plan was wrong on paper. Because it didn't survive contact with reality.

**Sam:** Seventy percent. So where does the eleven pm fix come in?

**Maya:** The first time you fix a critical system at eleven pm, you're stressed. The second time you're annoyed. By the tenth time, you're educated.

**Sam:** Educated in what, exactly?

**Maya:** What breaks under load. What actually depends on what, not the clean boxes, the hidden dependencies. How people really work. The docs say steps one, two, three. Reality is one, three, two, skip four, repeat one.

**Sam:** And the workarounds.

**Maya:** Which workarounds are load-bearing. Someone built a hacky, undocumented fix three years ago, and it's the only thing preventing a cascade failure. You find that out when you try to clean it up.

**Sam:** That's expensive education. The post is blunt about that.

**Maya:** It is. You pay in stress, missed dinners, and career years. But it's real. It changes how you plan. Whiteboard plans come from whiteboards. Plans that work come from scars.

**Sam:** So what does a Monday-proof plan actually look like? Make it concrete.

**Maya:** Five things. One, it assumes failure, not success. Good plans ask what could go wrong. Great plans ask what has gone wrong before.

**Sam:** Two?

**Maya:** It includes the human layer. Who knows this system, what happens if they're not available, where's the documentation, who's on call. Three, it accounts for the shadow process, the sticky notes and the ask-Sarah steps and the spreadsheet accounting secretly depends on.

**Sam:** Four and five.

**Maya:** Four, smaller blast radius. Don't migrate the whole system at once. Migrate one piece, verify, migrate the next. When something breaks, and it will, the damage is contained. Five, rollback. Every deployment answers one question. If this fails, how do we get back to working. If the answer is we can't, the plan isn't ready.

**Sam:** There's a line in here about consultants that stung a little.

**Maya:** The consultants who write the Friday plan leave before Monday. They never see the failures, never learn from them, and they carry the same blind spots to the next engagement. Operators stay for Monday. They stay for the eleven pm fix. They carry the scars.

**Sam:** Okay, first thing tomorrow. Someone's listening, they've got a plan on a whiteboard right now. What do they do?

**Maya:** List your last three fires. Real production incidents. For each one, ask what it taught you about planning. Then add one question to every plan. What's the workaround. If the system fails, what do people do instead. If you can't answer it, you're not ready.

**Sam:** And the human layer.

**Maya:** For every component, write down who knows this, and what happens if they're unavailable. Then run a pre-mortem. Before launch, imagine it already failed, and work backwards. And finally, make the blast radius smaller. Break the deployment into phases, each one independently rollback-able.

**Sam:** The goal isn't zero failures.

**Maya:** It's never zero failures. The goal is to plan for failures so they're recoverable.

**Sam:** Plans don't fail because they're poorly reasoned. They fail because they're built for the Friday whiteboard, not the Monday reality.

**Maya:** And the eleven pm fix is where you learn the difference.

**Sam:** This has been Pilot to Production, from the Growth Project. If your plans look great on Friday and fall apart on Monday, that's the gap we close, at thegrowthproject.com.

**Maya:** Thanks for listening. See you next time.