Why founders get stuck as the default decision maker
Early on, a founder deciding everything is a feature, not a bug.
You know the customer, the product, and the plan, so centralized choices are fast and consistent.
The problem is that this stops scaling long before most founders notice.
The question is not whether to delegate, but how to tell when the moment has arrived and what to hand over first.
This guide gives you a practical test, a way to pick which decisions to release, and a method for handing them over without chaos.
The goal is not to become distant from the work.
It is to spend your judgment where it actually changes outcomes.
In a small team, the founder is usually the fastest path to an answer.
Someone asks a question, you answer, work continues.
That habit forms because it works, and it keeps working right up until it quietly becomes the bottleneck.
The costs are easy to miss because they show up as delays elsewhere.
Team members wait for your input before acting.
You become the meeting everyone schedules around.
Meanwhile, the decisions only you can make, like where the company is going next, get crowded out by a stream of small approvals.
Max Rhodes, co-founder and CEO of Faire, described this shift in an interview with Y Combinator.
In the early days, Faire ran on a six-week product cycle, decisions were centralized, often with him making them, and the whole company met daily for standups.
As the company grew past a thousand employees, the cycle stretched to six months, decisions became decentralized, and systems held people accountable without constant touchpoints.
He compared the change to moving from driving a speedboat to driving an aircraft carrier.
Y Combinator interview with Max Rhodes
The lesson is not that every company should copy Faire's structure.
It is that the shift from centralized to decentralized decisions is a normal, planned part of growth, not a failure of control.
A practical test: three signals it is time to let go
Use these three signals together.
Any one of them alone might be noise.
Two or more at once usually mean the moment has arrived.
Signal one: the same decision type keeps reaching you
If you are answering the same category of question repeatedly, such as which customer request to prioritize or whether a refund is justified, the decision has a pattern.
Patterned decisions can be described, taught, and handed off.
One-off strategic calls usually cannot, at least not yet.
Signal two: work stalls while waiting for you
Look for queues, not complaints.
If tasks sit in a blocked state until you review them, or people batch small questions to save your time, throughput is capped by your calendar.
That is a structural limit, and no amount of personal effort fixes it.
Signal three: big-picture work keeps losing to small approvals
Notice what you never get to.
If strategy, hiring, or customer conversations are consistently displaced by routine sign-offs, your attention is being spent on the lowest-leverage layer of the company.
That is the clearest sign the current arrangement is costing more than it protects.
Which decisions to delegate first
Not all decisions are equal.
A simple way to sort them is by two questions: how reversible is the choice, and how much does it depend on information only you hold?
- Delegate early: reversible, patterned choices. Refund policies within a range, small feature tradeoffs, scheduling, and tooling picks. If a wrong answer is easy to undo, someone close to the work should make it.
- Delegate with guardrails: reversible choices with real downside. Pricing experiments, vendor selection, and hiring for junior roles. Set the boundaries and the criteria, then let someone decide inside them.
- Keep for now: hard-to-reverse calls and choices that depend on your unique context. Company direction, co-founder relationships, major spending, and early key hires. These benefit from the full picture you have.
The sorting matters more than the speed.
Founders who delegate everything at once often create whiplash, because the team lacks the context for the big calls.
Founders who delegate nothing stay the bottleneck.
The workable middle is releasing decisions in order of reversibility.
How to hand over a decision without losing quality
Delegation fails when it is a hand-wave.
It works when the decision is transferred with its context, its boundaries, and a way to learn from the outcome.
A short written handover does more than any pep talk.
Write down four things before you pass a decision along:
- The outcome the decision should serve. Not the method, the goal. What is this choice actually for?
- The boundaries. What is in range, what needs a check-in, and what is off-limits for now.
- The context only you hold. Customer history, past attempts, constraints. This is usually the real reason the decision was stuck with you.
- How you will review results. A light, regular look at outcomes, not a re-litigation of each choice.
As an illustrative example of how this looks in practice: suppose a founder has been personally approving every customer refund.
The handover note might say the goal is keeping customers who hit a genuine problem.
The boundary is that any refund within the standard policy window needs no approval, while anything unusual goes to a weekly review.
The context includes two past cases where a generous refund prevented a public complaint.
The team member now decides inside a frame, and the founder checks outcomes weekly instead of tickets daily.
This is an illustrative scenario, not a documented customer result, but the shape of it is what a usable handover looks like.
Replacing your judgment with systems, not silence
The hardest part of stepping back is that your judgment was doing invisible work.
When you stop making every call, something has to carry the alignment you provided.
That something is usually a small set of written systems.
Rhodes described how Faire handled this as it grew.
The company built a strategy doc he collaborated on with the leadership team.
He shared updates at all-hands and in biweekly business reviews with accessible notes.
He used OKRs as a guidepost rather than a measuring stick.
Teams were organized into self-sufficient groups, each working toward a metric tied to a top-level company goal.
He also noted that systems break as a company grows.
His biweekly review with each team worked with three teams and became impossible with more than fifteen, so teams were regrouped into pillars.
His stated aim was balancing time spent coordinating against time spent executing.
Y Combinator interview with Max Rhodes
You do not need that machinery at five people.
You need the smallest version of it: a short written direction the team can check without asking you, and a regular review rhythm where outcomes are visible.
If you are weighing what rhythm fits your team, consider whether to hold weekly team updates.
That question covers how small remote teams keep alignment without adding meetings for their own sake.
Common mistakes when founders step back
- Delegating without context. Handing someone a decision they cannot make well, then blaming them for the result, teaches the team to route everything back to you.
- Re-deciding quietly. If you override a delegated call without saying so, the delegation is dead. Disagree openly or let the outcome stand.
- Confusing involvement with control. You can stay deeply informed through reviews and written updates without being the approval step for everything.
- Waiting for a calm week. The right moment never feels calm. The signals above, not your schedule, should trigger the change.
What to do this week
Pick one decision type that keeps reaching you and fits the delegate-early profile.
Write the four-part handover note from the section above.
Give it to the person closest to the work, and set a single recurring review to look at outcomes.
Keep everything else unchanged for now.
Then watch the signals again.
If queues shrink and your calendar opens toward bigger questions, repeat with the next decision type.
If quality slips, the fix is usually more context or clearer boundaries, not taking the decision back.
If you want a structured way to think through a specific call before handing it off, see the founder decision memo glossary entry.
It explains a short written format for framing a decision, its options, and its tradeoffs before you commit.
The takeaway
A founder should stop making every decision when patterned, reversible choices keep reaching them.
It is also time when work stalls waiting for their input, and big-picture work keeps losing to small approvals.
The remedy is not distance.
It is deliberate handovers: clear outcomes, explicit boundaries, transferred context, and a review rhythm that keeps the team aligned without routing every call through you.
Start with one decision type, learn from the handover, and expand from there.
Being able to decentralize decision making starts with hiring the best people and then arming them with the right information. — Max Rhodes, co-founder and CEO of Faire, on what makes delegation work Y Combinator interview with Max Rhodes
Take the next step with Ideoreto. Use the ideas in this guide as a starting point for your next project.
Register for Ideoreto to get started.