Decision-Making Frameworks for Founders Under Pressure
Speed matters more than perfection. Three decision-making frameworks that help founders move fast without moving stupid.
Framework 1: Reversible vs. Irreversible
This is the most important framework. It determines the speed at which you should make a decision.
What makes a decision reversible?
A reversible decision is one you can undo at reasonable cost:
- Hiring someone who doesn't work out. You part ways. Cost: wasted time and a small recruiting expense.
- Trying a new marketing channel that doesn't perform. You stop. You spent $50K instead of $500K.
- Picking a new project management tool the team hates. You switch back. You lost a week of productivity.
- Changing your pricing page layout. You revert it tomorrow.
What makes a decision irreversible?
An irreversible decision is one you can't undo, or can only undo at catastrophic cost:
- Merging with another company. The legal, cultural, and financial entanglement can't be unwound cleanly.
- Moving all infrastructure to a proprietary platform you can't migrate out of.
- Firing someone without proper documentation who then sues.
- Making a public commitment to a customer you can't fulfill.
- Granting equity. You can't take it back.
- Where you incorporate. Changing jurisdictions is extremely expensive.
The rule
Reversible decisions should be made quickly. The cost of being wrong is small. The benefit of learning by trying is large. Bias toward action.
Irreversible decisions should be made carefully. Get input from people who understand the consequences. If you can't undo it, invest the time to get it right.
The trap
Most founders treat reversible decisions like irreversible ones. You spend two months deciding which CRM to use. You hold meetings. You create comparison matrices. Meanwhile, your team is still using four different systems to track customers. The perfect decision is the enemy of the good decision.
Quick classification exercise for your current decisions:
| Decision | Reversible? | Recommended Speed |
|---|---|---|
| Which analytics tool to use | Yes | Decide this week |
| Hiring a VP of Sales | Mostly yes | 2-4 weeks of diligence |
| Taking venture investment | No | 4-8 weeks of deliberation |
| Changing your pricing model | Mostly yes | Decide in 1-2 weeks, test |
| Customer contract terms | No | Get legal review, take time |
| Product direction pivot | Depends on runway | Match speed to remaining runway |
Framework 2: The 70% Rule
Most startup founders wait too long because they want certainty. They want 90% or 95% confidence. They want to run the analysis one more time. They want the data that will prove they're right.
The problem is that you almost never get to 90%. Especially not in the time window that matters. While you're waiting for perfect data, the window closes. The talent gets hired by someone else. The market shifts. The opportunity is gone.
What 70% confidence looks like
The 70% rule is simple. Make decisions at 70% confidence. That means:
- You've thought through the major implications
- You've talked to 2-3 smart people with relevant experience
- You've identified the top 3 risks
- You don't think you're making a stupid mistake
- You acknowledge you could be wrong and you're okay with that
At 70% confidence, you decide. You commit. You implement with the assumption that you'll learn as you go and adjust if needed.
Building the instincts to make it work
You can't make 70% confidence decisions if your judgment is bad. You get good instincts by making many decisions and learning from the outcomes. Part of your job as a founder is building decision-making capability across your team. Not by adding more layers of approval. By empowering people to make good decisions at 70% confidence.
Practical approach: After every major decision, write down your confidence level and your reasoning in two sentences. Revisit it 90 days later. Over time, you'll see where your instincts are calibrated well and where they're off. This is how you train your judgment.
Framework 3: First Principles
When you're under pressure, it's easy to copy. What did the last successful company do? What are other companies in this space doing? You default to patterns you've seen.
First principles means you start from the ground up. You identify the core truths about your situation. You reason from those truths instead of copying patterns.
A pricing example
A founder is trying to decide on pricing. Every SaaS company she sees charges monthly. So she assumes she should too. That's pattern copying.
First principles reasoning: - What do my customers actually want? (Predictable costs, not surprise bills) - What creates minimum friction? (Matching their budget cycle) - What maximizes their ability to commit? (Annual pricing if they buy during budget season) - What does my cash flow need? (Upfront annual payments help with runway)
Maybe annual pricing makes sense even if everyone else does monthly. Maybe pay-as-you-go is better even though it's operationally complex. The answer comes from your specific situation, not from the industry template.
The first principles checklist
When facing a novel decision:
1. What question am I actually trying to answer? 2. What do I know to be true? (Not assume. Know.) 3. What am I assuming? (Write these down explicitly.) 4. Which assumptions matter most? If they were wrong, would my decision change? 5. What would I do if I weren't worried about looking stupid?
Most founders use first principles without naming it when they're early-stage. When you're so new that you don't know the industry patterns, you reason from first principles by default. As you get more experienced, the temptation is to shortcut and copy. That's usually fine. But the moments when first principles wins are the moments when your situation is genuinely different from the template.
When to Decide Fast and When to Slow Down
The speed of a decision should match the stakes and the reversibility:
| Reversible | Irreversible | |
|---|---|---|
| High Stakes | Moderately fast. Be thoughtful but don't be paralyzed. You can course-correct. | Slow and deliberate. Multiple perspectives. Think through downsides. |
| Low Stakes | Fast. Just decide. The cost of being wrong is tiny. | Moderately careful. It won't kill you, but you can't fix it. Make sure you're not doing something dumb. |
The challenge for founders is that many important decisions cluster in the high-stakes, irreversible quadrant. Where you incorporate. Who you hire as co-founder. Whether you take investment. What your customer terms are. These need the most thought.
But even with irreversible decisions, there's such a thing as analysis paralysis. At some point you have to commit. You have to accept the risk. Set a deadline for the decision and honor it.
Decision Fatigue and Protecting Your Judgment
You make dozens of decisions a week. Most of them are small. What tool to use for X. Whether to say yes to a meeting. What to fix first. The small decisions don't matter individually. But collectively, they drain your judgment for the decisions that do matter.
Three antidotes to decision fatigue
1. Delegation. Certain categories of decisions should not be your job. Once you've set the framework, your team decides:
- Don't make hiring decisions that should be made by the hiring manager
- Don't make technical decisions that should be made by your CTO
- Don't make marketing decisions that should be made by your head of marketing
- You set the values and constraints. They decide within those.
2. Systems. Routine decisions should not require your judgment:
- What time does the standup happen? That's decided.
- How do you handle a customer complaint? That's a process.
- When do you promote someone? That's a framework with clear criteria.
Systematic decisions free your judgment for decisions that actually need it.
3. Physical basics. Your decision-making quality degrades noticeably when you're sleep-deprived or sedentary. You make riskier bets. You get irritable in conversations. You change your mind more often. If you're running on fumes, your decisions get worse. This is not motivational advice. It's operational reality.
The Post-Mortem: Learning Without Blame
You will make bad decisions. Everyone does. The question is whether you learn from them.
How to run a decision post-mortem
After a decision plays out, look back:
- What was your reasoning at the time?
- What information did you have?
- What did you get right? What did you get wrong?
- What would you do differently if you could replay it?
The post-mortem is not a blame session. The person who made the bad decision should be part of it. They have the most context. They can explain the reasoning.
Three possible outcomes
1. The decision was fine given what you knew. You just got unlucky. That's okay. Nothing to change. 2. You learn a framework that would have caught the mistake. In the future, you'll make better decisions in that category. 3. The problem was execution, not the decision. You decided right, but the implementation went wrong. That's a different kind of learning.
Most founders skip the post-mortem. They just move on to the next crisis. That's inefficient. The best operators invest in learning from decisions.
Building a Decision Log
Write down your major decisions. Not all of them. The ones that matter. For each one, capture:
- The decision (one sentence)
- Your reasoning (2-3 sentences)
- Key factors that influenced you
- What you were uncertain about
- Date
Then review it every six months. What actually happened? Did your reasoning prove right? What would you do differently?
This serves two purposes. First, it helps you see patterns in your own thinking. Do you tend to overestimate adoption? Underestimate implementation time? Get too optimistic about team capacity? You can see the bias and correct for it.
Second, it's a record of your reasoning that you can come back to. You can explain to someone else why you decided something. You can teach the next generation of leaders about the decisions you faced.
Most founders don't do this because it feels like extra work. It takes 5 minutes per decision. The learning compounds. Better decisions today lead to better decisions next quarter, which leads to a stronger company.
For how decision-making evolves as your team grows, see From Chaos to Process: Scaling Operations. For making decisions with your board's input, see Running Effective Board Meetings as a First-Time CEO.
Ready to sharpen your decision-making process? Contact us to work through your current decisions.
Related Guides
Automating Operations: What to Build vs. What to Buy
Automation isn't about replacing people. It's about freeing them from work that doesn't require judgment. Know what to build, buy, or leave manual.
Running Effective Board Meetings as a First-Time CEO
Board meetings shouldn't be a performance review you dread. Make them the most useful two hours of your quarter.
From Chaos to Process: Scaling Operations at 10, 50, and 100
What works at 10 people breaks at 50. Map the operational transitions your company will face and evolve your systems at each stage.
Need help with operations?
We build operational systems and automation for startups. Let's talk.