How to delegate effectively when you've been doing everything yourself

Delegation is the hardest skill for founder-operators to build, because the instinct that made them successful — owning every detail — becomes the bottleneck that limits growth. The shift is not about letting go of standards; it's about moving your involvement from doing to directing.

The reason most delegation fails: the founder delegates the task but not the context. They hand someone a job without explaining what success looks like, why it matters, what they can decide on their own, and what they need to check in on. That's assignment, not delegation.

True delegation has four components: outcome (what does done look like?), authority (what can they decide without checking?), resources (what do they have to work with?), and accountability (how and when will you review?). Give all four.

Start by identifying the tasks only you can do — not the ones you're best at, but the ones that genuinely require your specific judgment, relationships, or authority. Delegate everything else, systematically.

Build a delegation ladder. Some tasks should be: done and reported, done and then consulted, done with approval, or recommended and then done. Start people at 'consult' and move them to 'done and reported' as they prove judgment.

Expect mistakes. If someone you've delegated to never makes a mistake, you've either chosen too easy a task or you're hovering. Create psychological safety for errors while holding the accountability for learning from them.

TBC works with founders on the leadership transition from operator to director — building teams that execute well without constant oversight. If you're working 70 hours a week and your company still can't run without you, the structure needs to change.