The Decision You Keep Delaying Is Already Costing You
You do not need more information. You do not need more time. You need to stop finding reasons to avoid the decision you already know you need to make.
You know what the decision is. You do not need someone to name it for you. It is the person who has been underperforming for eight months and who you have had two direct conversations with and three indirect ones. It is the service line that costs more to deliver than it earns, that has been subsidised by the profitable parts of the business for the past eighteen months. It is the partnership that stopped being mutual twelve months ago and has been running on the remaining goodwill of one party since then.
You know. You have known for longer than you are comfortable admitting. And every week that passes without the decision being made is a week that the cost of the delay accumulates — in money, in team morale, in your own energy, and in the opportunity cost of the capacity that is locked into managing something that should no longer exist in its current form.
The question is not what to decide. The question is why you have not decided yet. And the answer to that question — when examined honestly — is almost never about information. It is almost always about something else.
Why Founders Delay Hard Decisions — The Real Reasons
The stated reasons for delay are usually reasonable-sounding: I need more data, I want to see if things improve naturally, I am waiting for the right moment. These are rationalizations. The real reasons are emotional, and they are worth naming clearly — because naming them is the first step to moving past them.
Reason 1 — The discomfort of causing pain to someone you know
Most hard decisions in a founder-led business involve people. Letting someone go. Ending a partnership. Telling a long-standing client that you cannot continue to serve them. These decisions cause pain — not just for the person on the receiving end, but for the founder who has a relationship with them. The person who needs to be let go has a family. They have been loyal. They tried, even if they did not succeed. Ending a partnership means acknowledging that something you both invested in has not worked.
The discomfort of causing this pain is real and legitimate. It reflects the founder’s humanity and their awareness of the impact of their decisions on other people’s lives. But this discomfort, when it becomes the primary driver of delay, does not protect the person in question. It prolongs their uncertainty, deprives them of the clarity they need to make their own decisions, and consumes the resources — the founder’s time, the team’s energy, the business’s capital — that belong to the people and work that are actually moving forward.
Delaying a painful decision is not kindness. It is the management of the founder’s own discomfort at the cost of everyone else’s clarity.
Reason 2 — The fear of being wrong
Hard decisions carry the risk of error. What if the person would have improved given another month? What if the service line would have become profitable with a different approach? What if the partnership needed one more honest conversation rather than a restructure?
This fear of being wrong is particularly acute for founders who have built their identity around good judgment. The founder who is known for making sound decisions has more to lose, psychologically, from a decision that proves incorrect than a founder who holds their decisions more lightly. The fear of being wrong becomes the paralysis that prevents any decision at all — which is itself always wrong.
Reason 3 — The hope that the situation will resolve itself
This is the quietest and most expensive form of delay. The founder is not actively choosing to avoid the decision. They are choosing to wait and see — betting that the situation, if given enough time, will either improve or deteriorate to the point where the decision becomes undeniable.
Situations that require a founder’s decision almost never resolve themselves. They drift. The person who is underperforming does not spontaneously begin performing.
The unprofitable service line does not discover a new revenue model on its own. The partnership that has stopped being mutual does not rebalance through the passage of time. What happens instead is that the cost of the unresolved situation continues to accumulate, the team’s confidence in the founder’s willingness to act continues to erode, and the eventual decision — when it is finally made — is made in worse circumstances than if it had been made months earlier.
| Not deciding is a decision. And it is almost always the most expensive one available — because it combines the costs of the wrong situation continuing with the costs of the delay, and produces none of the benefits of the right decision having been made earlier. |
What Delayed Decisions Actually Cost
The cost of a delayed decision is not just the direct cost of the situation continuing. It is a composite of at least four distinct cost categories that most founders calculate incompletely.
The carrying cost
Every day that a wrong situation persists, it consumes resources. The underperforming team member receives a salary, occupies a role, and fills capacity that could be used for someone who would deliver what the business needs. The unprofitable service line consumes delivery resources, management attention, and cash. The dysfunctional partnership occupies board meeting time, generates legal and administrative overhead, and drains the emotional energy of both parties.
The carrying cost is calculable. Take the monthly resource cost of the situation — salary, delivery cost, management time at an honest valuation — multiply it by the number of months the decision has been delayed. In most cases, the number is significantly larger than the founder had estimated.
The opportunity cost
Every resource consumed by a wrong situation is a resource not available to a right one. The salary paid to the underperforming team member is a salary that could be attracting a high performer. The management attention consumed by the dysfunctional partnership is attention not available for the strategic thinking that drives the business forward. The cash subsidising the unprofitable service line is cash not invested in the profitable one.
Opportunity cost is invisible in the moment — because the lost opportunity is hypothetical rather than real. But it becomes visible over time, when founders look back at the years during which the wrong situation persisted and ask what could have been built with the resources that were consumed by it.
The team confidence cost
Your team is watching every delayed decision. They see the underperforming team member still in role after the second conversation that was supposed to change things. They observe the dysfunctional partnership continuing despite its visible dysfunction. They notice that the service line that costs more than it earns has survived another quarter.
Each of these observations updates the team’s model of the founder’s decisiveness and clarity. When the model degrades — when the team begins to believe that the founder will not make difficult decisions — it creates a secondary cost: the team begins to make their own decisions about the business’s direction, the value of their role within it, and whether this is an environment worth their best effort.
The personal energy cost
Unresolved decisions do not leave the founder’s mind when the working day ends. They travel home. They surface at dinner. They occupy the space between sleeping and waking that is supposed to be rest. The cognitive and emotional load of carrying an unresolved decision — particularly one with personal dimensions — is a real and significant drain on the founder’s capacity for the thinking and the relationships that matter most.
“The founders who move fastest are not the ones who decide fastest. They are the ones who have done the work to be clear enough that decisions become obvious — and have built the courage to act on what is obvious.”
A Framework for Making the Decision You Have Been Avoiding
The following framework is not a decision-making tool for situations where you genuinely lack information. It is a tool for situations where you have the information but have not yet acted. If you recognise yourself in what has been described above, this framework is for you.
Step 1 — Name the decision explicitly
Write it down in one sentence. Not the situation — the decision. Not Farrukh has been underperforming but rather: I need to decide whether to continue Farrukh’s employment or end it. The difference between naming the situation and naming the decision is significant. The situation invites further analysis. The decision invites action. Write the decision, not the situation.
Step 2 — Calculate the carrying cost honestly
Take the resource cost of the current situation — in money, time, and team energy — and multiply it by three months. This is the minimum additional cost of continuing to delay. Write this number down next to the decision. Make the cost of inaction as concrete as the discomfort of action.
Step 3 — Answer the information question honestly
Ask yourself: is there specific information I do not currently have that would materially change this decision? Be honest. In most cases of decision delay, the answer is no — the founder has the information required to decide and is waiting for certainty that will not arrive, or for circumstances to change in ways that would make the decision unnecessary. If the answer is genuinely yes — name the specific information, the specific source, and the specific timeline for obtaining it. If you cannot name all three, the delay is not about information.
Step 4 — Identify the worst realistic outcome of deciding now
Not the worst imaginable outcome — the worst realistic one. The person who is let go will find another role. The partnership restructure will be uncomfortable but survivable. The service line closure will disappoint some clients but will be explained professionally. Compare this worst realistic outcome to the accumulated cost of continued delay. In most cases, the comparison resolves the question.
Step 5 — Set a decision date and hold it
Identify the date by which the decision will be made — not implemented, made. Mark it. Tell someone you trust. The accountability of a named date does not replace the clarity required to decide well. But it does prevent the indefinite extension of the delay that characterises most avoided decisions.
How to Make Hard Decisions With Humanity
Making a decision promptly does not require making it harshly. The founder who decides to end a team member’s employment can do so with respect, with generous notice, with an honest conversation about the reasons, and with practical support for the transition. The founder who restructures a partnership can do so with fairness, with legal clarity, and with genuine acknowledgment of what was built together.
Decisiveness and humanity are not in conflict. What is in conflict is the desire to make a decision and the desire to delay making it because it might cause discomfort. The decision that is made promptly and humanely almost always produces a better outcome — for everyone involved — than the decision that is delayed and then eventually forced by circumstances into a context where neither promptness nor humanity are possible.
Frequently Asked Questions
How do I know when I genuinely need more information versus when I am just avoiding the decision?
Ask yourself: if I received the additional information I am waiting for and it confirmed what I already believe to be true, would I then decide? If the answer is yes — you are waiting for permission, not information. The information you have is sufficient. The permission you need is your own.
What if the decision affects people’s livelihoods and I genuinely care about the impact?
Caring about impact is appropriate and worth honouring. The question is whether the delay actually protects the people it is intended to protect — or whether it prolongs their uncertainty while the founder manages their own discomfort. In most cases, a clear, honest, promptly made decision — communicated with genuine care — does more to protect people than a delayed one made under worse circumstances.
Should I involve my team in hard decisions?
Involve your team in the process of thinking through decisions where their perspective is genuinely valuable. Involve them in the implementation of decisions once made. Do not involve them in the decision itself when the decision is about people or partnerships — these decisions belong to the founder or the leadership team, not to the collective. Making hard people decisions by committee almost always produces worse outcomes and greater damage to the people involved.
I made a delayed decision and it went badly. How do I process that?
Every delayed decision that is eventually made produces a better outcome than the same decision never made. The cost of the delay is real — acknowledge it honestly. But the decision that was made, even late, addressed a situation that the delay was not addressing. Learn from the delay. Identify what prevented earlier action. Then carry that learning into the next decision that begins to accumulate the familiar weight of being avoided.
How do I build a culture of faster, clearer decision-making in my business?
Model it. The team’s decision-making culture mirrors the founder’s. When the founder makes difficult decisions promptly and communicates them clearly, the team develops confidence that decisions will be made, that information will be shared, and that clarity will follow ambiguity. When the founder delays, the team learns to wait. The culture of decision-making is always downstream of the founder’s own practice.
| Ready to build a business with real clarity? Book a free 30-minute Founder Clarity Call with Anubhav Bharadwaaj. www.aydeebee.com | grow@aydeebee.com |
| About the Author Anubhav Bharadwaaj Business Coach & Strategic Consultant | Dubai, UAE Anubhav Bharadwaaj is a Dubai-based entrepreneur, business coach, and institutional mentor. Founder of Aydeebee — a strategic consulting platform for founders across the UAE, GCC, and Asia. Mentor at IIT Delhi’s FITT and MDI Gurgaon. Author of The Founder’s Code series. |
