Building a Management Team Below the Founder

A management team below the founder is the layer of senior leaders who run functions, business units, or the whole operation, so that day-to-day decisions stop flowing through one person. Researchers call it the top management team, and practitioners call it the leadership team or the second layer. In a founder-led company it usually doesn't exist at the start. It has to be built on purpose.

The hard part isn't hiring titles. It's moving real decision rights from the founder to people who may decide differently. This article covers why the layer is hard to build, the common structures, how roles tend to get added, how decision rights shift, and the trade-offs a founder accepts along the way.

What the management layer below a founder actually is

In a very small company, the founder is the management team. Everyone reports to them, and they make most of the calls. As the company grows, a group of people takes ownership of outcomes the founder used to own: revenue, delivery, finance, people, product. The layer is defined by two things: its members hold accountability for a result, and they hold the authority to decide how to get it.

That second part separates a real management team from a group of senior employees. If every meaningful decision still goes to the founder for approval, the company has a layer of titles and no layer of management. The test is simple: when the founder is unreachable for two weeks, what stops?

Why this layer matters: upper echelons theory

Donald Hambrick and Phyllis Mason published "Upper Echelons: The Organization as a Reflection of Its Top Managers" in the Academy of Management Review in 1984. According to Penn State's account of the paper, it set out to link organizational outcomes with the values and experience of the organization's upper management. The same page reports it was selected as the best paper of the journal's first decade.

The practical reading for a founder is that strategy isn't made by one person in isolation. What a company does reflects the experience and perspective of the group at the top. A founder who builds a team of people who think like them gets a narrow set of views. A founder who builds a team with different backgrounds gets more of the company's problems seen before they become crises. That's an implication of the theory, not a rule it states, so treat it as a design consideration.

Why founder-led firms struggle to build it

Three forces tend to work against the layer.

The founder is the bottleneck by design. The company grew because the founder made good calls quickly. Handing those calls to someone else feels like a step backward, and for a while it often is.

Span of control stretches. A founder with ten direct reports across sales, delivery, finance, and admin can't go deep on any of them. Span of control is the number of people reporting directly to one manager, and no source gives a universal right number. What's true in general is that the more varied the work reporting to one person, the less attention each part gets.

The company outgrows its management style. Larry Greiner's growth model describes this pattern. In his framework, as summarized in a Journal of Organization Design review, creativity-led growth is broken off by a crisis of leadership, and direction-led growth is broken off by a crisis of autonomy. The review adds that Greiner predicts a business manager will be hired in the second stage, while in the first stage only the founder or founders manage the firm. Our explainer on Greiner's growth model walks through all the phases.

The crisis of autonomy is the one that matters most here. Once managers exist, the people closest to customers and operations want to make their own decisions. If the founder keeps directing from the top, the new layer becomes a relay station and the good managers leave.

Common structures for the management layer

There's no single correct design. These are the models founder-led companies commonly use, and each fits a different situation.

The COO model deserves a note, because it's the most debated. In a Harvard Business Review article on the COO role, Nate Bennett and Stephen Miles argue that asking what makes a great COO is like asking what makes a great U.S. vice president: the answer depends entirely on the CEO. In other words, the role has no standard job description. It takes whatever shape the founder and the company need, which is why defining it explicitly matters. For a sample scope, see the chief operating officer job description template.

The sequence in which roles tend to get added

No source defines one correct order of hires, and anyone presenting a fixed sequence as law is overreaching. What the sources and common practice support is a principle: add leaders where the founder's attention is the binding constraint.

Greiner's model offers the clearest published anchor. Per the Journal of Organization Design review above, the first stage has only the founder managing, and a business manager arrives in the second stage. After that, his model moves toward functional specialists, then toward managers who own results in their units, which matches the structures in the table.

In practice, a founder-led company usually adds roles in a pattern like this (illustrative, not a prediction):

1. The function the founder is weakest in or least wants to run. A founder who came from product often needs commercial or financial leadership first. A founder who came from sales often needs delivery or operations.
2. The function where mistakes are most expensive. Finance and legal exposure often force an early hire even if the founder would rather not.
3. The function that is growing fastest. Whichever team is adding people quickly needs a manager before it needs a process.
4. A coordinating role. Once several function heads exist, someone has to resolve conflicts between them, which is where a COO, general manager, or a regular leadership team meeting comes in.

The sequence matters less than the handover. Each hire needs a clear outcome they own and a defined set of decisions they can make without asking.

How decision rights shift

Decision rights are the formal answer to "who gets to decide this?" In a founder-led company they are often implicit: the founder decides everything, and nobody wrote it down. Building a management layer means writing it down.

A workable shift usually happens in stages:

• Founder decides, manager informs. The manager gathers facts and recommends. The founder still makes the call.
• Manager decides, founder is consulted. The manager makes the call after hearing the founder's view.
• Manager decides, founder is informed after. The manager acts and reports the result.
• Manager decides, no report needed. Routine matters within a defined boundary.

Moving a type of decision down one step at a time, with a threshold such as budget size or customer impact, lets both sides build trust. A delegation of authority matrix puts these thresholds in a single reference, and a RACI matrix helps when the question is who does what on a shared piece of work rather than who approves it. The skill side of this, passing work down without losing quality, is covered in delegation as a competency.

Signs the founder is the bottleneck

These are general patterns, not measured thresholds. If several apply, the management layer is either missing or isn't being allowed to work.

The trade-offs: rich versus king

Building the layer costs the founder something, and the cost isn't only money. Noam Wasserman's research on founders frames it as a choice. In "The Founding CEO's Dilemma: Stay or Go?", a Harvard Business School Working Knowledge interview published in 2005, he asks whether the need is to control the company, to be king, or the drive for success, particularly financial success, which may require stepping aside once certain milestones are reached. His later Harvard Business Review article, "The Founder's Dilemma", reports on 212 American start-ups founded in the late 1990s and early 2000s and finds that most founders surrendered management control long before their companies went public: by the time the ventures were three years old, 50% of founders were no longer the CEO.

Two points from that research bear on the management layer. First, in the 2005 interview Wasserman says that when founder-CEOs do really well, the chance they'll be replaced rises, and that whenever founders raise a new round of financing, the chance of being replaced goes up dramatically. Second, the interview describes this as a paradox of success: the growth that makes a strong management team necessary is also the growth that puts the founder's own role in question.

These findings come from venture-backed start-ups, so they don't map directly onto a family-owned distributor or an owner-managed agency with no outside investors. The underlying trade-off still applies. A founder who wants to keep full control will tend to build a smaller, more loyal, less independent team. A founder who wants the company to be worth more will tend to hire people with real authority, accept disagreement, and share ownership or influence.

Neither choice is wrong. The failure mode is wanting both and building neither: hiring strong managers and then overruling them.

A practical way to start

If you're a founder with a team and no management layer, the sequence below is a reasonable starting point.

1. List the decisions you personally make in a month. Tag each as strategic, operational, or routine.
2. Pick one function and one outcome. Name a leader, give them a result to own, and write down which decisions are theirs.
3. Define a tie-breaking rule. When two leaders disagree, who decides, and when does it come to you?
4. Set a short, regular leadership meeting. Its job is to resolve cross-functional issues, not to report to the founder.
5. Document how the work gets done. Process documentation lets a new leader run a function without relying on the founder's memory.
6. Review after a quarter. Look at which decisions still route through you and ask why.

For more on how this fits into the larger shift from founder-run to company-run, see the hub on professionalizing a business. The broader question of leading at scale is in managing at scale.

Key Facts

• Hambrick and Mason's 1984 Academy of Management Review paper set out to link organizational outcomes with the values and experience of upper management, per Penn State.
• In Greiner's model, creativity-led growth ends in a crisis of leadership and direction-led growth ends in a crisis of autonomy, per a Journal of Organization Design review.
• That review also reports Greiner predicts a business manager is hired in the second stage, with only the founders managing in the first.
• Noam Wasserman's HBR article studied 212 American start-ups and found that by year three, 50% of founders were no longer CEO (HBR, 2008).
• Wasserman says founder-CEOs are more likely to be replaced after raising a new financing round and when the company does well (HBS Working Knowledge).
• Bennett and Miles argue the COO role has no standard definition and depends on the CEO (HBR, 2006).

Related reading

• Professionalizing a business
• Delegation of authority matrix
• Key person risk
• The second-in-command role
• Advisory boards for private companies
• Greiner's growth model
• Early stage vs growth stage