Delegation for Founders Who Can't Let Go

The founder is still writing the onboarding emails personally eighteen months in, still reviewing every piece of marketing copy, still the only person who touches the pricing model. Each individual instance feels justified: this one's important, this one's sensitive, this one would take longer to explain than to just do. The pattern, repeated across a hundred small decisions, is what actually caps the company's growth.

Why does generic delegation advice fail here?

"Hire people you trust and get out of their way" sounds right and explains almost nothing about how to actually get there. It skips the hard part entirely: how do you know when someone is ready for a specific task, what does appropriate oversight actually look like without becoming micromanagement, and what do you do with the gap between "I trust this person generally" and "I trust this person with this specific high-stakes task right now."

Generic AI prompting repeats the gap. Ask an assistant "how do I delegate better" and it tends to return generic principles, communicate clearly, set expectations, check in regularly, without the specificity to resolve the actual moment of hesitation: whether to hand off this particular task to this particular person today, and if so, how closely to watch it.

The founder-specific version of this failure is a story told so often it's become a cliche without losing its grip: "it's faster to do it myself." It usually is, for this one task, today. The cost shows up later, compounded across every task never handed off, in a company that cannot grow past whatever one person can personally attend to, regardless of how many people are on the payroll.

What does the documented management record say to do?

Andy Grove: match oversight to task-relevant maturity, not general trust

Grove's High Output Management (1983) introduces task-relevant maturity: a person's readiness for a specific task, based on their demonstrated experience with that specific kind of work, not a general trait like seniority or overall competence. The appropriate level of oversight is a direct function of this task-specific readiness, closer supervision for low readiness, more autonomy as readiness is demonstrated.

Applied: Before delegating a specific task, assess readiness for that task specifically, not the person in general. Someone excellent at execution might have low task-relevant maturity for a judgment-heavy pricing decision; someone newer to the company might have high task-relevant maturity for a technical task they did for years at a previous job. Match your oversight level to that specific assessment, not to their title or tenure.

Grove's own insight is that over-supervising a high-maturity task wastes everyone's time and signals distrust, while under-supervising a low-maturity task sets someone up to fail and then blames them for a mismatch that was actually a delegation error. The skill is diagnosing readiness accurately per task, not applying one oversight style uniformly across everyone. A founder who supervises every task at the same intensity, regardless of who's doing it or how much they've already demonstrated, is applying a single setting to a problem that genuinely varies task by task and person by person.

Peter Drucker: define the outcome, not the method

Drucker's documented management philosophy, particularly in The Effective Executive (1967), holds that effective delegation specifies the result wanted and leaves the method to the person doing the work, rather than prescribing every step. Over-specifying method under-uses the judgment you're supposedly delegating to, while being vague about the actual desired outcome leaves no way to evaluate whether the work succeeded.

Applied: When handing off a task, write one clear sentence describing what success looks like, not a list of steps to follow. "This email sequence should get at least a 20% open rate and sound like our brand voice" delegates the outcome and the judgment about method. "Write three emails using this exact structure" delegates neither.

Drucker's framing also clarifies what delegation is actually for: it isn't just redistributing effort, it's deliberately handing judgment to someone closer to the work than you are, so their specific knowledge gets used instead of being overridden by a method you designed before you knew what they'd learn in the process.

Jason Fried: delegate less work by taking on less work in the first place

Fried's Rework (2010) and the broader calm company philosophy argue that much of the delegation problem is actually a commitment problem: companies that say yes to too many initiatives create more work than any delegation system can distribute cleanly, leaving founders feeling like they have to do everything themselves because there's genuinely too much to go around.

Applied: Before solving a delegation bottleneck by assigning more tasks to more people, ask whether the task needs to exist at all. A calm company's fewer, more deliberately chosen commitments are easier to delegate well than a sprawling company's many half-considered ones, because there's simply less total work competing for the same limited pool of ready people.

How do the three approaches compare in practice?

What can you run before the next handoff?

Why it works: separating task-specific readiness from general trust in the person catches mismatches a gut-level "do I trust them" question tends to miss.

Why it works: founders who've done a task themselves for years tend to default to describing their own method out of habit, and a deliberate rewrite pass catches this before the brief goes out.

Why it works: distinguishing a volume problem from a matching problem prevents solving the wrong one, adding delegation process to a company that's simply taken on too much doesn't fix the actual bottleneck.

What's the honest limit of delegation frameworks?

These frameworks improve how a specific delegation decision gets made and briefed. None of them can tell you whether a specific person on your specific team is actually capable of growing into a task they haven't done before, that judgment requires knowing them in a way no framework can substitute for. The frameworks sharpen the decision. The read on the person is still yours, built from how they've actually performed, not from how confident they sound when you ask if they're ready.

Andy Grove and Peter Drucker both sit in the Operator & Systems category alongside W. Edwards Deming, and Jason Fried sits in the Bootstrapper category. For turning how you actually do a task into a procedure someone else can run, SOP Writer is a $79 tool built for exactly that, and for structuring a new hire's or newly delegated owner's first stretch in the role, First 90 Days Plan is a $99 tool built for the handoff itself.

All the copy-paste prompts from this guide, and the rest of the Situations series, live at /prompts too, free to copy without reading the guide first.