Building a Leadership Team When You've Never Managed Managers Before
Managing managers is a genuinely different skill from managing individual contributors, and most founders learn it entirely on the job, often while making avoidable mistakes.
In this article 8 sections
Quick answer: Managing managers requires a genuinely different skill set than managing individual contributors — evaluating someone's ability to develop and enable other people's work, rather than their own direct output, and resisting the urge to bypass the new management layer and manage their direct reports yourself. Most founders learn this skill entirely on the job, and the most common mistake is undermining a newly hired manager's authority by continuing to engage directly with their team as if the manager weren't there.
The transition from managing individual contributors to managing managers is one of the least-prepared-for shifts in a founder's leadership journey, largely because the two roles require genuinely different evaluative skills. Managing an individual contributor means assessing their own work quality and output. Managing a manager means assessing something less directly visible: how well they develop, motivate, and enable the people reporting to them — a skill that shows up in someone else's results, not their own. The SHRM's research on management transitions consistently identifies this exact shift — from managing work to managing people who manage work — as one of the hardest and most under-supported transitions in most organizations.
Why Founders Are Especially Prone to This Mistake
Founders in particular are prone to bypassing new managers, more so than executives who join a company that already has an established management layer, because founders typically have long-standing personal relationships with early team members that predate any org chart. A team member who's used to bringing questions directly to the founder for years doesn't automatically stop doing so just because a new manager has been hired above them — and if the founder continues answering those questions directly rather than redirecting them to the new manager, both the team member and the new manager quickly learn that the org chart isn't the real reporting structure in practice.
Breaking this pattern requires active, deliberate effort from the founder — consistently redirecting questions to the new manager even when it would be faster to just answer directly, and being explicit with the team about why that redirection is happening rather than let it seem arbitrary or personally distancing. This is uncomfortable in the short term, particularly with team members the founder has a long history with, but it's necessary for the new management layer to actually function as intended.
Why This Transition Is Genuinely Different
When managing individual contributors, a founder can directly assess quality by looking at the work itself — code, a sales conversation, a piece of content. When managing a manager, the founder is one level removed from the actual work, and has to instead evaluate something harder to observe directly: whether this person is developing their team's skills, making good hiring and performance decisions, and creating an environment where their reports can do good work. This requires a different evaluative lens, and founders who don't consciously adjust for it often end up either micromanaging the manager (defeating the purpose of the layer) or under-managing them (missing real problems until they've compounded).
The Most Common Mistake: Bypassing the New Manager
A founder hires their first manager specifically to reduce their own direct span of control, but then continues fielding questions directly from that manager's reports, continues making decisions about their work without looping the manager in, and generally continues operating as if the new management layer doesn't exist. This is understandable — old habits and existing relationships with the team don't disappear just because an org chart changed — but it actively undermines the new manager's authority and defeats the entire purpose of having hired them.
Hiring a manager and then continuing to manage their team directly is worse than not hiring the manager at all — it creates confusion about who's actually in charge without gaining any of the intended benefit.
Measuring a Manager's Success Correctly
A manager's own individual output is rarely the right measure of their success in the role — their job is to enable their team's output, not primarily to produce their own. The better measures are the team's engagement, retention, and collective results: is their team producing good work, are people on that team growing and staying, and is the manager surfacing real problems to you rather than either hiding them or escalating everything unnecessarily. A founder who evaluates a new manager purely on their own personal contributions is measuring the wrong thing.
Building the Information Systems That Scaling Requires
As a leadership layer forms, the informal awareness a founder used to have — knowing what's happening across the team simply by being close to everything — stops scaling naturally. This requires deliberately building systems: regular manager check-ins, a structured way for problems to escalate when a manager genuinely needs support, and enough visibility into each team's health that the founder isn't relying purely on the manager's own self-reporting. Founders who skip building these systems, assuming their prior informal awareness will simply continue, often find themselves surprised by problems that had actually been visible for a while at the team level.
Getting the First Layer of Management Hires Right
The first layer of management hires matters disproportionately, since a bad fit here is expensive to unwind — not just the direct cost of the hire, but the damage to team morale and trust that a poor manager can cause before the problem is fully recognized and addressed. Prioritizing genuine people-development skills and self-awareness in these hires, not just strong individual-contributor track records (which don't automatically predict good management ability), meaningfully improves the odds of getting this layer right the first time. The Census Bureau's Statistics of U.S. Businesses shows how quickly organizational complexity grows with headcount, underscoring why getting this first management layer right matters more than it might initially seem to a founder used to a flatter structure.
A Simple Checklist for the Transition
| Action | Why it matters |
|---|---|
| Route requests through the new manager, not around them | Protects their authority from day one |
| Measure the manager by their team's results, not just their own | Evaluates the actual job they were hired to do |
| Build regular manager check-ins and escalation paths | Replaces the informal awareness that no longer scales |
| Prioritize people-development skills in management hires | Individual-contributor success doesn't predict management success |
If you're navigating this transition alongside a broader question about your own evolving role in the company, our comparison of founder-led versus professional management covers the related, larger-scale version of this same shift.
For related reading, our piece on reading a P&L statement covers adjacent ground worth a look. And for a broader, outside reference point, the Small Business Administration's business guide is a useful resource to have on hand alongside this topic.
Conclusion
Managing managers well requires consciously unlearning some of the instincts that made a founder a good individual manager — direct oversight of the work itself gives way to evaluating someone else's ability to develop and enable a team. Most founders learn this on the job, often while making the common mistake of undermining new managers by bypassing them. Recognizing that risk explicitly, and building the deliberate systems that replace informal awareness as the company scales, makes the transition considerably smoother than learning it purely through trial and error.
