The diagnosis is wrong. The delegation was just done badly. And delegation done badly is worse than not delegating at all — it destroys trust, creates rework, and reinforces the founder's belief that they have to do everything themselves.

The Delegation Failure Pattern

Most failed delegation looks like this: founder hands off a task with minimal context, team member produces something different from what was expected, founder takes it back. Both parties learn the wrong lesson — the team member that they can't be trusted, the founder that delegation doesn't work.

The problem is almost never the team member's capability. It's the handoff.

The Four-Part Delegation Framework

Define the outcome, not the method. Tell people what done looks like — the result, the standard, the deadline — not how to get there. When you prescribe the method, you own the outcome. When you define the result and give autonomy on method, they own it.

Establish check-in points, not check-up culture. Agree upfront on when you'll touch base. "Let's check in halfway through and then at completion." This gives you visibility without undermining their ownership.

Make the standards explicit. What does good look like? What would make this excellent versus adequate? Most team members want to do great work but can't calibrate without knowing what you're calibrating against.

Debrief, not just review. After something is completed, spend ten minutes on what went well and what they'd do differently. This builds judgment faster than any training programme.

What to Delegate First

Start with recurring tasks that follow a defined process — things you've done the same way twenty times. These are easiest to document and hand off cleanly. Build the muscle on low-stakes delegation before moving to complex judgment calls. The goal isn't to get tasks off your plate. It's to build a team that can own outcomes.