A Decision-Making System For Founders Who Have Become The Bottleneck

If your team's most common status update is "waiting on the founder," you have a decision-making problem. It is not that you decide badly. It is that too many decisions need you to decide at all, and the ones that do often arrive without the information you need.

The answer is not to stop caring about quality. It is to build a simple system that matches each decision to the right level of attention, puts a named person in charge of it and leaves a record of what was decided and why.

Sort decisions by reversibility and impact

Not every decision deserves the same process. A useful first sort asks two questions. Can this decision be reversed cheaply if it turns out to be wrong? And how much does it affect the company if it is wrong?

Decisions that are easy to reverse and low impact, such as which tool a team uses for a project or how a feature behaves in an early version, should be made quickly by whoever is closest to the work. Treating them as major choices wastes time and teaches the team to escalate everything.

Decisions that are hard to reverse and high impact, such as a senior hire, a pricing model, a long-term contract or a change in strategy, deserve more care, more input and the founder's direct involvement. Most decisions sit somewhere in between and should be handled by the relevant leader with the founder informed.

Be honest about which category a decision belongs in. Founders tend to overestimate how hard decisions are to reverse, especially ones close to their own expertise. Many product and process choices can be changed within weeks if they turn out to be wrong.

Name one owner for every significant decision

Every decision that goes beyond a single person's work needs one named owner. The owner gathers input, makes the call (or recommends it to whoever must approve it) and communicates the result. Others can be consulted, but consultation is not a veto.

Write down which decisions you keep for yourself, and which you have handed to specific people. A short decision-rights document, updated as the company grows, prevents the most common source of friction: two people both believing the decision is theirs.

When you have handed a decision to someone, resist the urge to override it unless the stakes are genuinely high. Every override teaches the team that delegated decisions are not real.

Ask for decisions in writing

For decisions that need your approval, ask for a short written proposal instead of a meeting. A one-page format works well: the decision needed, the options considered, the recommendation, the main risks and the deadline. Writing forces the owner to think it through, and lets you respond asynchronously in minutes rather than finding a slot next week.

Set a default response time. If you commit to responding to written proposals within a set number of working days, and agree that silence after that period means approval for lower-stakes items, the bottleneck shrinks immediately.

Keep the template short on purpose. A proposal that runs to many pages is often a sign that the owner is not yet sure of the recommendation, and that is worth a conversation before it becomes a document.

For the hardest decisions, add a step before committing. Ask the group to assume the decision has failed a year from now and list the reasons why. This kind of pre-mortem surfaces risks people may be reluctant to raise in a normal discussion.

Keep a decision log

Record significant decisions in a shared log: what was decided, by whom, when, the main reasons and any conditions that would prompt a revisit. It takes a minute per decision. It saves hours of relitigating decisions that people forgot were made, and it helps new hires understand why things are the way they are.

Review the log once a quarter. Look at which decisions turned out well, which did not, and whether the process or the information was the problem. That is how the system gets better over time.

The log also helps in board meetings and fundraising, where investors often ask why the company made a particular choice. A clear record of the reasoning at the time is more credible than a reconstruction from memory.

What to do this week

List the decisions currently waiting on you and sort them by reversibility and impact. Hand the easy-to-reverse ones back to the people closest to the work. Write a decision-rights document that names who owns which kinds of decisions. Share a one-page proposal template and commit to a response time. Then start a decision log and add the next significant decision to it the day it is made.