Why management is a different skill from the work itself, why founders struggle to delegate, matching delegation level to trust, common new-manager mistakes, and managing former peers.
Being excellent at a job (writing great code, closing great deals, delivering great service) does not automatically make someone a great manager. Management is a genuinely different skill: it's about enabling other people to do great work, not doing the work yourself. This distinction trips up founders constantly, because the instinct that made them successful individually (do it yourself, do it well, do it fast) can actively work against them once their job is to build a team that does the work instead.
"I can do it faster myself" is true today and false over time
In the short term, doing a task yourself is almost always faster than teaching someone else to do it. This makes delegation feel inefficient in the moment. But it's a trap: every task you keep doing yourself is a task that never gets built into someone else's capability, which means you stay the bottleneck indefinitely. The founders who successfully scale past themselves are the ones who accept short-term slowness in exchange for long-term capacity they don't personally have to supply forever.
Match the delegation level to the person's experience and your trust in the specific task
| What it looks like | Best for | |
|---|---|---|
| Do exactly as instructed | Detailed, step-by-step direction with little independent judgment | Someone brand new to a task, or a task with very low tolerance for variation |
| Research and report back | They investigate and bring you options, but you decide | Building judgment on a task before handing over real decision authority |
| Recommend and I'll decide | They form a real recommendation; you retain final sign-off | Someone developing good judgment who isn't fully trusted with the final call yet |
| Decide and inform me | They make the call and tell you afterward | Someone with a track record of good judgment on this type of decision |
| Fully autonomous | No check-in required at all | A trusted, proven owner of a clearly bounded area |
Why matching the level matters: delegating at too low a level for someone's actual ability is a common way capable people get frustrated and disengaged. Delegating at too high a level for someone's actual readiness sets them up to fail, and can quietly erode your trust in delegation altogether after one bad outcome. The level should shift over time as trust and track record build, delegation isn't a single decision, it's an ongoing calibration.
Effective delegation is usually about being clear on the what and the why, while giving real latitude on the how. Micromanagement (dictating not just the goal but every step to reach it) tends to signal a lack of trust, slows the person down, and prevents them from developing their own judgment. The more useful discipline is investing real effort up front in making sure the goal and its context are genuinely understood, then stepping back on execution details unless something goes visibly off track.
| Why it happens | What to do instead | |
|---|---|---|
| Avoiding hard conversations | Discomfort feels worse than the cost of letting an issue slide | See Performance Management: small issues addressed early stay small |
| Treating everyone the same instead of individually | Feels fair on the surface, but different people need different support and communication styles | Adapt your approach to the individual, while keeping standards and expectations consistent |
| No regular 1:1s once things get busy | 1:1s feel cuttable when the calendar is full | This is usually exactly when they matter most: they're often the first place a brewing problem surfaces |
| Not giving credit, or quietly taking it | Easy to do unintentionally when reporting up to your own leadership or investors | Visibly and specifically crediting your team's work builds the trust that makes delegation possible in the first place |
| Promoting the best individual contributor into management with no support | It feels like a natural reward for strong individual performance | Being good at the job and being good at managing people doing the job are different skills: provide real support and expect a learning curve |
A specific, common, genuinely awkward situation: managing someone who was recently your peer, or being promoted over people you used to work alongside as equals. This deserves direct, explicit handling rather than hoping it resolves itself: acknowledge the shift openly, be consistent and fair (avoid both over-correcting into distance and under-correcting into favoritism), and give it real time. The relationship doesn't have to become distant, but it does have to genuinely change, and pretending otherwise usually just delays an awkward conversation everyone can already sense needs to happen.
Checklist
0/5Quick Check
Why is "I can do it faster myself" a trap for a founder trying to grow a team?
A strong individual contributor is promoted directly into a management role with no additional support. What's the risk?
Key Terms
Ask a question about this lesson or share your take.
Loading…