How to improve decision making as an entrepreneur: the frameworks nobody teaches you
A founder I know spent nine weeks deliberating over whether to fire a single client. Nine weeks. The client represented 4% of her revenue and about 60% of her stress. When she finally made the call, the whole thing took one email and a difficult Tuesday afternoon. That gap between the cost of deciding and the cost of the decision itself is where most entrepreneurs bleed.
Improving decision making as an entrepreneur is not about becoming smarter or more intuitive. It's about building systems that stop you from re-litigating the same judgment calls and burning your best hours on choices that don't deserve them.
Key Takeaways
- Most entrepreneurs lose more time deciding than executing. The bottleneck is the process, not the intelligence.
- Named frameworks — the 5 C's, the 10-10-10 rule, inversion, pre-mortems — work because they force you out of your default thinking pattern.
- Cognitive biases (sunk cost, survivorship, founder overconfidence) silently corrupt calls you believe are rational.
- Decision fatigue is real, and it hits hardest in the late afternoon. Protect your mornings for the calls that matter.
- A reversible decision made fast beats a perfect decision made slowly. Almost every time.
Why smart founders keep making bad decisions
I once watched a technically brilliant founder — someone who could debug a payment pipeline at 2 a.m. — spend three months refusing to kill a product line that had generated eleven sign-ups in a quarter. His reasoning was coherent. He'd built it. He'd hired for it. Walking away meant admitting the last eight months were wasted.
The catch? Those eight months were already gone. No decision could bring them back. He wasn't choosing between "kill the product" and "keep the product." He was choosing between "stop the bleeding now" and "bleed for another six months to protect my self-image."
The real bottleneck isn't analysis
Entrepreneurs rarely fail because they lack information. They fail because the information they have is filtered through emotional commitments they don't notice. The sunk cost fallacy is the obvious one, but it's not alone.
- Survivorship bias — you study the founders who made it, then copy their habits, forgetting the thousands who did the same thing and vanished.
- Overconfidence — you remember the calls you got right and quietly forget the rest.
- Anchoring — the first number you hear (a valuation, a salary, a projection) sticks, even when you later learn it was garbage.
- Confirmation — you notice the customer who loves the product and skip past the six who churned without a word.
None of these feel like errors. They feel like judgment. That's the problem.
What are the 5 C's of an entrepreneur?
The 5 C's are a self-check tool built around five qualities that compound on each other: Commitment, Courage, Capability, Confidence, and Consistency. The logic is that each one builds on the previous — you can't have real confidence without capability, and you can't build capability without committing long enough to learn.
Why does this matter for decision making? Because most stalled decisions are disguised failures of one of the five, not of analysis.
How the 5 C's map onto real decisions
- Commitment — the founder who can't decide whether to launch is often not undecided; he's unwilling to commit until he's certain. Certainty never arrives. Commit anyway.
- Courage — killing a product, firing a friend, raising prices. The analysis is easy. The act takes nerve.
- Capability — some decisions stall because you genuinely don't know how to evaluate the options. That's a signal to learn or delegate, not to delay.
- Confidence — comes after the previous three, not before. You earn it by doing.
- Consistency — the one most founders drop. One good decision per quarter doesn't build a company. The same good decision, repeated weekly, does.
When a decision has been sitting in your head for more than a week, run it through this list. Which C is actually missing? Nine times out of ten, it's courage or commitment — and no amount of further analysis will fix either.
What is the 10-10-10 rule for decision-making?
The 10-10-10 rule, popularized by Suzy Welch, asks you to evaluate a decision by how you'll feel about it in 10 minutes, 10 months, and 10 years. The three timeframes strip out the emotional noise of the moment and force you to weigh the decision against genuinely different horizons.
I've used this one more than any other framework, and it saved me from at least one terrible hire.
A concrete example
A candidate I was interviewing had the right résumé and a genuinely warm presence. Ten minutes after offering the role, I'd have felt great. Ten months in, based on two reference calls I'd been avoiding, I'd likely be managing around a gap in his skills. Ten years out, I'd barely remember the hire either way — so the ten-month view was the one that mattered.
I passed. He went on to build something impressive elsewhere. Both outcomes were fine.
The trick is recognizing which horizon actually governs the decision. For a pricing change, the ten-month view usually dominates. For a co-founder equity split, it's the ten-year one. For what to say in a difficult email this afternoon, ten minutes is enough.
| Framework | Best for | Time to apply | Weakness |
|---|---|---|---|
| 10-10-10 rule | Emotionally loaded calls | 2 minutes | Ignores second-order effects |
| Inversion | Strategy and risk | 15-30 minutes | Can spiral into paranoia |
| Pre-mortem | Big irreversible bets | 1 hour, with team | Requires honest people in the room |
| 5 C's self-check | Stalled decisions | 5 minutes | Diagnostic, not prescriptive |
| Eisenhower matrix | Daily triage | 3 minutes | Too coarse for strategic calls |
Pre-mortems and inversion: the two frameworks I'd keep if I could only keep two
Most founders plan for success and then get blindsided. A pre-mortem flips it: you gather the team and imagine it's twelve months from now, the project has failed spectacularly, and you're writing the post-mortem. What went wrong?
The reason this works is uncomfortable but simple — people are far better at explaining failure in hindsight than predicting it in advance. Give them permission to be the pessimistic narrator and they'll surface risks nobody wanted to raise in the optimistic planning meeting.
Inversion is the solo version. Instead of asking "how do I make this work?", ask "what would guarantee this fails?" Then avoid those things. It sounds trivial. It isn't. When I applied inversion to a partnership deal two years ago, the answer to "what would kill this?" was "a slow legal review during a cash-flow crunch." That single insight reshaped the whole timeline.
When not to use these
Pre-mortems and inversion are for decisions that are expensive or impossible to reverse. Applying them to a $200 tool subscription is a waste of a good framework. Reserve them for the calls that actually shape the company's trajectory.
Managing biases and decision fatigue
Here's what I got wrong for the first couple of years: I treated decision quality as a character trait. It isn't. It's closer to a battery that drains.
By 4 p.m., after a day of small calls, I was making worse choices than I would have made at 8 a.m. — and I didn't notice, because bad decisions made while tired feel exactly like good ones. I'd agree to meetings I should have declined. I'd approve spending that deserved a night of thought. I'd snap at the wrong moment.
The fixes that actually worked
- Batch trivial decisions. What to eat, what to wear, which email to answer first. Templates and defaults, not deliberation.
- Protect morning hours for high-stakes calls. I schedule hiring, pricing, and strategy decisions before 11 a.m.
- Write the decision down before making it. Half the time, the act of writing reveals that it's not a decision at all, just anxiety.
- Set a decision deadline. Past a certain point, more analysis doesn't improve outcomes — it just postpones the discomfort.
- Delegate the low-stakes reversibles. Not because your team will get them all right, but because their approximate call is worth more than your perfect call made three days late.
And one more, which took me longer to accept: sleep is a decision-making tool. Not a lifestyle virtue. A tool. On the mornings after fewer than six hours, my error rate on complex calls roughly doubles. I don't have a study to cite. I have my own calendar and a long trail of poor judgment I can now trace back to those mornings.
Putting it together: a simple decision protocol
You don't need to run every framework every time. You need a default sequence that catches the common failure modes without eating your afternoon.
Ask first: is this reversible? If yes, decide in under five minutes and move on. If no, run it through 10-10-10 to strip the emotional charge, then a quick inversion to find the failure paths, then check the 5 C's to see which quality is actually blocking you. Write the decision and the reasoning in one paragraph. Set a review date. Done.
The founders I've seen build the most get this down to a reflex. Not because they're smarter, but because they've decided in advance how they'll decide — and that leaves room for the part that actually matters: doing the work.
The next time a decision sits in your head for more than a week, ask yourself one question. Is it genuinely hard, or have you just not committed? Those two situations call for completely different responses, and confusing them is how nine weeks disappear.
