The Hidden Cost of a Decision You Keep Avoiding

There's a decision you've been carrying for longer than you should.

You know what it is. It shows up in the quiet moments: the drive to a meeting, the last ten minutes before sleep, the moment someone asks how things are going and you give a version of the truth that doesn't include it.

You haven't made the decision. But you haven't abandoned it either. It lives in a kind of permanent suspension, costing you something every single day.

This is the most underestimated problem in running a business.

Not the decisions you've made badly. Not the ones that didn't work out. Those have already happened, and at least the costs are fixed. The real drain is the undecided: the co-founder conversation you're putting off, the product line you're not sure whether to cut, the client relationship that needs to be restructured or ended, the team member you already know isn't working.

Every day you don't decide, you're paying.

The carrying cost of an unmade decision

The cost isn't just psychological, though it is that too. It's operational. When a decision is pending, it changes the options available to you. The product line you're considering cutting still draws attention in your team meetings. The client you're unsure about still occupies space in your pipeline reviews. The co-founder conversation you're avoiding still shapes every strategic discussion you have.

You're not pausing the decision. You're deferring it while the meter runs.

Most founders are surprisingly comfortable with this. They'll build extraordinary capability for execution: shipping product, closing deals, managing people. And almost no capability for decision. The thing that could change everything sits in a drawer, and the rest of the machine keeps running around it.

The reason, almost always, is not lack of information. It's the opposite. You have enough information to make the decision. You just don't like any of the options.

Why decisions feel more dangerous than they are

There's a specific failure mode I see in smart, experienced operators: they mistake decision-making for certainty. They keep gathering information because the right answer hasn't become obvious. They mistake prolonged deliberation for rigour.

It isn't.

Beyond a certain point, more information doesn't improve the quality of a decision. It improves your comfort with making it. These are different things. The first is useful. The second is a delay mechanism dressed up as due diligence.

The other force at work is reversibility. We systematically overestimate how permanent our decisions are. The partnership you're considering ending can be restructured. The product direction you're nervous about committing to can be course-corrected in 90 days. The team change you're delaying has a version of itself that doesn't require finality until you learn more.

The decision you're afraid to make is rarely as permanent as it feels from the inside.

The structure that removes the stall

Decision Protocol exists because I got tired of watching good operators: and being a good operator: run expensive holding patterns on things that needed to be resolved.

The framework isn't complicated. Five stages. Each one designed to take the decision out of your head and put it through a process that holds.

Define it clearly. Write one sentence that states exactly what decision you're making. Not "what to do about the product": "whether to discontinue the legacy product line before the end of Q1." Precision removes ambiguity. Ambiguity is where decisions go to hide.

Gather the actual signals. Not more research. The specific information that would change your conclusion if it were different. If nothing would change your conclusion, you already have your answer and you're stalling. If something would, go find it.

Weigh the options against your criteria. Not your feelings about each option. Your criteria: the things that actually matter to this decision at this stage of your business. Write them down before you score the options. Scoring first and setting criteria after is rationalisation, not reasoning.

Decide. Commit to one option with a documented rationale. Not because it's certainly right, but because making a decision with 80% of the information is almost always better than making it with 95% of the information three months later.

Review it. Set a date. Not to second-guess the decision, but to evaluate whether the information that was uncertain has resolved in the way you expected. This closes the loop and builds the decision-making capability that compounds over time.

The decision you've been avoiding

If you've read this far and the specific pending decision is still sitting in your mind, it hasn't moved itself. That's what pending decisions do.

Here's the exercise: write down the one decision you've been carrying longest. Not all of them. The one. Set a deadline for making it: not an open-ended "soon," a specific date. And write the one piece of information that, if you had it, would make the decision obvious. Then go find that information, or accept that you're not going to find it and decide with what you have.

The cost of not deciding is already running. The question is how much more you want to spend before you stop.

---

*Decision Protocol is a structured framework for making better decisions under pressure. Free access at [leonhardwick.com/101121](/101121). Deeper work available through the [programmes](/programmes).*