Don’t Make Plans That Require Miracles
Miracle-dependent planning feels good in the moment. It’s optimistic. It makes us feel capable and confident. We tell ourselves we’re being ambitious, not unrealistic. But we are confusing hope with strategy.
Good plans account for normal human limitations. Bad plans assume everything will go perfectly. Build in extra time, because things take longer than expected. Keep a cushion in the budget, because emergencies happen. Have a backup option, because first choices fall through. Hope for the best, but plan for the likely. Miracles are wonderful when they happen, but terrible foundations for important decisions.
The truth is simpler and less flattering: we plan for miracles because we don’t want to do the hard work of planning for reality. Reality means acknowledging that we might fail, that things might take longer, that we might need help. It forces us to confront our limitations.
But limitations are not weaknesses, they’re design constraints. And good design works within constraints, not against them.
Miracle planning looks like the startup that needs every hire to be perfect, every product launch to go viral, and every investor meeting to result in funding. Or the wedding that requires perfect weather, no family drama, and every vendor to deliver flawlessly. It’s the parent who schedules back-to-back activities with no buffer time for traffic or tantrums, and the couple who buys a house at the absolute top of their budget, counting on no job changes, medical bills, or major repairs.
They all have the same flaw: they require everything to go right and nothing to go wrong.
Miracle plans are everywhere once you know how to spot them.
The cost goes beyond stress. When Plan A fails and there’s no Plan B, you make desperate decisions under pressure. You spend more money, burn relationships, compromise quality. You say yes to things you should decline and make promises you can’t keep.
Worst of all, you train yourself to avoid planning altogether. Why bother thinking through contingencies if nothing ever goes according to plan anyway? This creates a cycle where poor planning leads to chaos, which reinforces the belief that planning doesn’t work.
Good planning starts with one question: What could go wrong? Not out of pessimism, you’re just building a list of things to account for before you start.
Build in buffers. If something normally takes two hours, schedule three. If your budget is tight, add a 20% cushion. More importantly, identify your critical dependencies, also known as, “the things that must go right for your plan to work,” then ask how you can reduce them. Can you start earlier? Can you break this into smaller pieces? What happens if a key person is unavailable?
Plan for the likely, not the ideal. Most projects run over budget and behind schedule. People will be late, get sick, get distracted. Technology will have hiccups. Account for this upfront and you’re already ahead.
Here’s the counterintuitive part: planning for problems makes success more likely. Buffer time lets you do better work instead of rushing. An emergency fund means smart decisions instead of desperate ones. A backup plan means setbacks don’t have to become crises.
People who plan realistically appear more confident, not less. They know what could go wrong, and they’ve planned for it. They deliver on their promises, stay calm under pressure, and get to underpromise and overdeliver.
No miracles required.
