Scaling Structure

The Premise

Organization structure doesn't scale linearly. Companies hit predictable transitions where the current structure stops working and needs to evolve. The transitions happen because coordination cost grows faster than headcount: adding the 50th person doesn't add 1/50th more coordination complexity, it adds connections to 49 other people.

The specific numbers below are patterns, not rules. A company might hit the "first managers" transition at 15 or at 35 depending on the complexity of the work, the pace of hiring, and whether the founders are natural delegators. But the sequence is consistent: almost every company goes through these stages in this order.

Stage 1: Founder-Led (Under ~20 People)

What it looks like

Everyone reports to one or two founders. There is no formal management layer. The org chart, if it exists at all, is flat: the founder at the top, everyone else underneath. Communication happens in one room or one Slack channel. The founder has context on everything and makes most decisions.

Why it works

At this size, direct communication is still possible. The founder can know what everyone is doing, resolve conflicts in real time, and maintain alignment without formal processes. Meetings are conversations. Planning is informal. Speed comes from having one decision-maker who understands the full picture.

What starts breaking

• The founder becomes the bottleneck. Every question, escalation, and decision routes through one person. The founder's calendar fills up and important decisions wait.
• Onboarding slows. New hires can't get context without the founder's time, and the founder doesn't have time.
• People lack growth paths. There are no managers, so there's no mentoring structure and no clear career progression beyond "become more senior."

The structural response

Hire or promote the first managers. This is the hardest transition because it changes the founder's relationship with the team from direct to indirect. The founder has to let go of decisions they used to own.

Stage 2: First Managers (Roughly 20-50 People)

What it looks like

The org chart has three layers: founder/CEO, a handful of managers or leads, and individual contributors. Functional boundaries start forming: "engineering," "sales," "operations." Managers handle day-to-day team decisions. The CEO sets direction and handles cross-functional coordination.

Why it works

The CEO can still maintain context across the whole organization through 4-7 direct reports. Managers handle coaching, hiring, and daily prioritization for their teams. Communication flows through a small number of channels. Planning can still be done in one room with the leadership team.

What starts breaking

• The CEO is still the only integration point. Cross-functional decisions (product vs. sales, engineering vs. operations) all route through the CEO because no one else has authority across functions.
• New-manager growing pains. First-time managers make common mistakes: they micromanage, they avoid hard conversations, they don't delegate enough. Without management training or a People leader to coach them, these problems compound.
• Informal processes break. At 20 people, everyone knew who to ask for what. At 45, new hires don't know who owns purchasing, who approves customer exceptions, or where the product roadmap lives. Tribal knowledge doesn't scale.
• Specialists are needed. The team needs a recruiter, a finance person, a dedicated product manager. Each hire adds a new function and a new reporting relationship to figure out.

The structural response

Formalize functional departments with clear leadership. Hire a People/HR leader to support manager development. Start documenting the most important processes (planning, hiring, escalation). Consider whether the CEO's span is sustainable as the company approaches 50 people, if it's above 8, look at adding a leadership layer.

Stage 3: Functional Departments (Roughly 50-100 People)

What it looks like

Clear functional departments: Engineering, Product, Sales, Marketing, Customer Success, People, Finance. Each has a VP or Head-level leader. The CEO manages the leadership team. There are 3-4 layers in the org. Most people work within their function and coordinate cross-functionally through their leaders.

Why it works

Functional organization deepens expertise, creates clear career ladders, and works naturally for companies with a single product and market. Each VP owns their function end-to-end. The CEO coordinates across functions through the leadership team.

What starts breaking

• Cross-functional work gets slow. Anything that requires Product + Engineering + Design + CS to coordinate takes weeks of alignment meetings. Each function optimizes locally; product-level tradeoffs fall between the cracks.
• The CEO becomes a router. Every cross-functional dispute escalates to the CEO because no one else has authority across functional boundaries. The CEO spends their time resolving internal conflicts instead of leading externally.
• Functional silos form. Engineering doesn't understand customer problems. Sales doesn't understand technical constraints. CS discovers issues too late because they're disconnected from the product team.
• Management layers multiply. Engineering grows from 15 to 40 people and needs team leads, engineering managers, and directors. Each layer adds coordination cost and slows information flow.

The structural response

This is where the functional-to-divisional tension begins. Options include: creating cross-functional product teams, adding a COO/CPO to reduce the CEO's coordination load, or establishing formal coordination mechanisms (product councils, cross-functional planning cadences). The right choice depends on whether the company is staying single-product or expanding.

See Organization Structure Types for a detailed comparison of these options.

Stage 4: Divisional Tension (Roughly 100-200 People)

What it looks like

The company is too big for purely functional organization but may not yet need full divisional structure. Many companies at this stage live in a hybrid: some teams are functional, some are cross-functional, and the lines between them are unclear. The org chart looks different depending on who drew it.

What starts breaking

• The hybrid is confusing. Product teams exist but engineering career paths still run through the functional VP. Planning happens in cross-functional pods but budgets flow through functions. People have two bosses in practice but one on the chart.
• Manager-of-manager layers add overhead. Directors manage managers who manage ICs. Information takes three hops to move from the front line to the leadership team and three hops to come back. By the time it arrives, context is lost.
• The company has multiple products or segments that need different go-to-market strategies, different engineering investment, and different customer support approaches. The single functional org can't differentiate.
• Coordination meetings multiply. The calendar is dominated by alignment: product reviews, architecture reviews, roadmap syncs, cross-team standups. People spend more time coordinating than building.

The structural response

If the company has multiple products, customer segments, or geographies, this is usually where divisional structure starts making sense: each division owns its P&L or customer outcome end-to-end. If the company is single-product, the response is usually to create an operating layer (COO, Chief of Staff) and formalize cross-functional teams with real authority.

This is also where Decision Rights become critical. At 150 people, you can't rely on everyone knowing who decides what. It needs to be explicit and documented.

Stage 5: Scaled Organization (Roughly 200-500 People)

What it looks like

The organization has 4-6 layers, multiple divisions or business units, shared services (HR, Finance, IT, Legal), and formal planning processes. The CEO manages through a small executive team. Most employees don't interact with the CEO directly. The org chart is too large to fit on one screen.

What the design needs to support

• Autonomous units with shared services. Each division or business unit needs enough independence to move fast. Shared services (People, Finance, IT) need to serve all units without becoming bottlenecks.
• Clear governance. Who decides resource allocation between divisions? How are shared priorities set? What escalation path exists for cross-division conflicts? These questions need explicit answers, not informal workarounds.
• Talent systems at scale. Career ladders, performance evaluation, succession planning, and leadership development become structural necessities. You can't rely on managers "just knowing" who's ready for promotion.
• Communication systems. Information can't flow through the hierarchy fast enough. The organization needs all-hands meetings, written updates, internal comms practices, and ways for leadership to hear from the front line without intermediaries.

Common mistakes at this stage

• Over-centralizing decisions. If every meaningful decision requires executive approval, the organization can't move faster than the executives' calendars allow.
• Under-investing in shared services. HR, Finance, and IT become bottlenecks when they're staffed for a 100-person company but serving a 400-person one.
• Letting the org chart drift. At this size, the chart is too complex for anyone to hold in their head. If it's not maintained as a living document, structural problems go undetected for months.

Warning Signs You've Outgrown Your Structure

These signals suggest the current structure is lagging behind the organization's needs. They apply at any stage:

• The CEO is the bottleneck. Most important decisions wait for one person's approval.
• New hires take months to become effective because they can't figure out who owns what or how decisions are made.
• Coordination meetings outnumber work meetings. The calendar is dominated by alignment, not execution.
• Good people are leaving because they feel stuck, unheard, or confused about their role.
• The same problems keep recurring. The handoff issue that was "fixed" six months ago is back because the structural root cause was never addressed.
• The org chart doesn't match reality. People know who actually manages them, but it's different from what the chart shows.
• The leadership team spends more time on internal issues than external ones. Customers, market, and product take a back seat to organizational firefighting.