Part two of five in The Modern Technology Organization, a series from Paragon by Riviera Partners, the talent partner that helps top and growing technology companies scale, structure, and transform their teams. This series draws on our ebook, The Modern Technology Organization: How to Hire and Structure Teams for Today’s Org Design Models.
What we learned that works
- Flattening relocates complexity rather than removing it; the work of the missing layers lands on fewer, broader-scoped leaders.
- Stretched leaders quietly stop coaching, carrying context, and developing the next generation—weakening the internal pipeline.
- Autonomous teams accelerate work but scatter coordination, producing duplicate work, diverging systems, and unexpected dependencies.
- Flattening is a bet on the capability of the people who remain; win it deliberately by placing leadership where complexity is highest.
Somewhere in the last few years, “flat” turned into a compliment. Cutting management layers signaled a company that trusted its people, moved fast, and refused to drown in bureaucracy. Widening spans of control became a mark of operational maturity. The average manager now oversees nearly six direct reports, roughly double the number in 2019, and most leadership teams read that as a win.
For a lot of what it promises, flattening delivers. Fewer layers mean fewer handoffs. Communication runs more directly. Decisions that once crawled up and down a chain of approvals now happen closer to the work. Teams pick up more ownership, and managers see more of what their people are actually doing.
Then there is the part that never makes the slide. Flattening does not reduce the complexity of running an organization. It moves it. Knowing where that complexity goes, and who ends up carrying it, is what separates a flat company that scales from one that turns brittle without noticing.
The work in those layers did not disappear
Every management layer was doing real work, even when the work was invisible. Middle managers absorbed context and passed it between teams. They settled competing priorities before those fights reached the people building the product. They caught weak decisions early, coached people through the hard ones, and held the connective tissue that kept separate teams working from the same understanding.
Strip the layers out and that work does not leave with the boxes on the chart. It redistributes to whoever is left, which usually means fewer leaders, each now responsible for a wider scope, each carrying more context across more teams, each with less time to do any of it well.
The company gets structurally simpler and operationally more dependent on individual leadership. That is the real trade inside flattening, and it is a genuine trade: you are swapping layers for concentration. When the remaining leaders have the range and judgment to hold it together, the swap pays off. When they do not, you have moved the bottleneck off the org chart and into a handful of overloaded people, which is one of the core dynamics behind the execution gap that shows up across fast-moving tech companies.
What a stretched leader quietly stops doing
A stretched leader stops coaching, carrying context between teams, and setting clear priorities, and the whole thing looks like capable people operating in triage. Once a leader’s span stretches past what they can actually cover, predictable things start to slip.
Decisions turn reactive, because a leader in triage handles whatever is loudest instead of whatever matters most. The bandwidth math is unforgiving: Gallup found that 97% of managers now carry individual-contributor work on top of leading, and they spend a median of 40% of their time on it. Context stops circulating between teams, because the person who used to carry it has run out of hours. Priorities blur, decision rights get fuzzy, and the small ambiguities a present manager would have cleared up in a hallway now sit unresolved for weeks.
The quieter losses are coaching and development. Managers spread across too many reports stop developing the people under them, right when the company needs more capable operators. The scale of the thinning is easy to underestimate. Gusto found that 14% of managerial roles were cut across small and mid-sized businesses, and the share of workers in a people-manager role fell 34% over five years. The people who would have coached the next generation are the ones getting removed. Promotion paths narrow because there are fewer leadership roles to grow into. Over time a structure built to move faster starts producing fewer of the leaders it depends on to keep moving, and the erosion stays invisible until you go looking for your next tier of leaders and find the bench empty.
Autonomous teams solve one problem and open another
Autonomous, cross-functional teams speed up the work inside each team while scattering coordination between teams. Flattening rarely travels alone, and companies that pull out layers usually reorganize what remains into small teams built around products, platforms, or customer outcomes. Engineering, product, design, and data sit together with shared ownership over delivery. The logic holds up: combine the capabilities into one team and you kill handoffs, speed up iteration, and push decisions toward the work.
Inside a single team, it works. The trouble lives in the space between teams. When every team is autonomous, coordination becomes everyone’s job and therefore no one’s, and the result is a familiar set of failures.
Teams optimize for what they can see and control, which is their own local outcome rather than the company’s. Technical decisions drift apart, and systems slide into inconsistency as each team makes reasonable choices in isolation. Duplicate work piles up as cross-team visibility fades. Dependencies surface late and painfully, discovered at integration rather than planned for. And when priorities across teams are unclear, teams stall, unsure whether to move or wait.
This is the paradox of the network-of-teams model. It is built for speed, and it delivers speed, right up to the point where fragmentation eats the gains. As the number of teams grows, so does the need for leaders who can set clear priorities, reinforce shared context, and keep local decisions serving global outcomes. The structure hands you autonomy for free. Coherence you have to pay for.
Complexity migrates to the seams
When you flatten and network an organization, complexity migrates to the seams between autonomous teams and onto the leaders spanning them. In a layered, siloed organization it concentrates in the hierarchy instead: in approvals, handoffs, and reporting lines. Flattening moves it rather than removing it.
That migration changes how you should deploy leadership, and it cuts against most companies’ instincts. The reflex is to spread experienced leaders evenly across teams, or to stack them at the top. In a flat, networked organization the right move is to put your strongest leaders where the complexity is highest: the areas with the most cross-team dependencies and the steepest cost of misalignment. That is the logic behind placing leadership where complexity is highest, and it only becomes visible once you accept that flattening moved the complexity in the first place.
It also changes what you hire for. In a hierarchy you could get away with specialists who executed cleanly inside a narrow lane, because the layers around them supplied context and caught mistakes. Take the layers away and every person needs enough range to operate without them. That profile is harder to find and harder to assess, which is exactly why hiring for judgment becomes central, and why, as these demands compound, hiring throughput becomes the constraint on how fast the whole organization can grow.
Flattening is a bet on your people
The most useful way to think about flattening is as a wager on the capability of the people you keep. Every layer you remove bets that the leaders and individuals left behind can carry the context, judgment, and coordination that layer used to provide. Win the bet and you get a fast, direct, ownership-driven company. Lose it and you get a tidy-looking org chart wrapped around an operation more fragile than the one it replaced.
Companies that flatten well are not the ones that remove the most layers. They are the ones that flatten on purpose, watch where the redistributed complexity lands, and build the leadership density and talent quality to absorb it. Flattening is the easy part. Everything the layers were quietly doing is the part you have to rebuild deliberately.
Frequently asked questions
Does flattening an org structure reduce complexity?
No. Flattening relocates complexity rather than removing it. The coordination, context-carrying, and priority-setting that middle layers handled don’t disappear; they shift onto fewer leaders with broader spans, making the organization structurally simpler but operationally more dependent on individual leadership capacity.
What is a healthy span of control for a manager?
There’s no universal number, but research links wider spans to weaker engagement and higher turnover. Gusto found the average manager now oversees nearly six direct reports, double the 2019 figure. Beyond roughly seven reports, coaching, context-sharing, and development are usually the first things to degrade.
What is a network-of-teams operating model?
It’s a design built around small, autonomous, cross-functional teams aligned to products or outcomes rather than functional silos. It accelerates work inside each team but scatters coordination across teams, so it requires deliberate leadership to keep local decisions aligned with global goals.
Previous: Part 1 | Next: Part 3
About this series: This article and the accompanying ebook, The Modern Technology Organization: How to Hire and Structure Teams for Today’s Org Design Models, were developed by Paragon by Riviera Partners, a leader in helping top and growing technology companies hire, scale, and structure their teams. Drawing on our work with hundreds of technology organizations, Paragon partners with CEOs and HR leaders to identify, evaluate, and place the leaders and talent who can scale decision-making, maintain alignment across teams, and turn ambition into execution. Download the full ebook or learn more about Paragon.