← Back to Blog
28 August 2026

Hierarchical Organizational Structure: What It Gets Right and Where It Breaks

Every organization, whether it employs ten people or ten thousand, must answer a fundamental question: who decides what, and who answers to whom? For most of business history, the answer has been the same. Build a pyramid. Stack authority at the top, distribute responsibility downward, and create clear lines of accountability from the front lines to the executive suite.

The hierarchical organizational structure remains the dominant model across industries, governments, and institutions worldwide, and for good reason. It solves real problems. It creates order, establishes decision-making authority, and gives employees a defined place within a larger system. But it also carries well-documented weaknesses that can slow companies down, stifle innovation, and frustrate talented people who feel buried beneath layers of management.

This analysis cuts through both the enthusiasm and the criticism to give you an honest, grounded look at how hierarchical structures actually function. You will learn where this model genuinely excels, where it predictably fails, and how to think critically about whether it serves your organization's specific needs. Understanding these dynamics is essential for anyone navigating, managing, or redesigning how teams work together.

What a Hierarchical Organizational Structure Actually Is — and Why It Emerges

At its most elemental, a hierarchical organizational structure is a pyramid of authority. A small number of individuals at the apex hold the broadest decision-making power; the largest population sits at the base, executing within narrowly defined boundaries. Directives travel downward through successive management layers, and accountability flows upward along the same vertical chain. The steeper the pyramid, the more layers stand between a frontline employee and the person ultimately responsible for strategic direction. This is not merely a diagram on an org chart; it is a description of how information, permission, and accountability actually move through an organization in practice. According to EBSCO's Research Starters analysis of hierarchical organizational structure, this model has historically dominated organizational design precisely because it creates legible lines of authority at scale. The Cone Model, which we will return to throughout this analysis, treats this triangular geometry as genuinely necessary but structurally insufficient on its own.

The critical question is why this shape keeps appearing, across centuries, industries, and cultures, rather than being designed away. The answer is mathematical before it is political. A 2019 study drawing on complexity research derived hierarchical structures as the mathematically optimal resolution of a specific tension: the productivity benefits of larger groups against the rising communication coordination costs those groups generate. The larger a group becomes, the more potential communication pathways exist between members, and coordination overhead begins to consume the very gains that scale was supposed to deliver. Hierarchy compresses those pathways by routing decisions through designated nodes, trading some informational richness for functional coherence. This means hierarchy is not an artifact of authoritarian tradition or a mechanism designed to concentrate power; it is an emergent solution to a real structural problem.

The anthropologist Robin Dunbar identified the approximate threshold at which that structural solution becomes unavoidable. Beyond roughly 150 people, the human brain can no longer maintain the quality of individual relationships needed to sustain informal coordination. Trust, reciprocity, and social accountability, the invisible infrastructure of small-group cohesion, simply cannot scale past this cognitive ceiling without external support. At roughly 150, an imposed social structure stops being a choice and becomes a functional necessity. The nested groupings that precede this limit, approximately 5, 15, 50, and then 150, each represent a distinct quality of relational tie, progressively weaker as the circle widens.

One company treats this finding not as theory but as operating policy. W.L. Gore and Associates, the manufacturer behind Gore-Tex, deliberately splits any division that reaches approximately 150 people into two smaller units. The logic is straightforward: once a unit crosses that threshold, the informal relational fabric that enables coordination, accountability, and trust begins to fray. Rather than compensating with additional management layers, Gore resets the scale entirely. As Organimi's comparison of hierarchical and flat structures notes, hierarchical models become notably more prevalent as headcount grows, which is precisely the scale-dependency Gore's policy operationalizes.

The framing distinction that matters most here is this: hierarchy emerges from structural necessity, not from a desire to concentrate power. Acknowledging that distinction does not require pretending hierarchy is cost-free. Communication silos, stifled insight from lower levels, and competitive ladder-climbing are real and documented consequences of poorly designed hierarchical systems. But those are design failures, not evidence that the structure itself is the problem. Conflating the two makes it impossible to diagnose what actually needs fixing. The honest analytical starting point is that hierarchy arrived because human cognitive limits made it arrive, and the real question is not whether to have structure but whether the structure you have is well designed for the relational load it carries.

The Genuine Strengths of Hierarchical Structure (The Steelman)

The case for hierarchical organizational structure deserves to be made seriously before it is interrogated. Too many critiques of hierarchy begin with its failure modes, skipping past the structural logic that made it the dominant form of large-scale human organization for millennia. That is an analytical error. If you want to understand where hierarchy breaks, you first have to understand precisely what it gets right.

Accountability without ambiguity. The most immediate and durable advantage of a hierarchical structure is the clarity of its reporting lines. Every person knows who owns a decision, who answers for an outcome, and who to escalate to when a situation exceeds their authority. This is not a soft benefit. It directly reduces coordination friction at the decision points where ambiguity is most costly. Research consistently distinguishes hierarchical structures by their "clearly defined roles," in contrast to flat structures where broader, overlapping responsibilities create the conditions for diffusion of responsibility, the well-documented tendency for individuals to assume that someone else is handling a problem when ownership is unclear. Clear accountability does not guarantee good decisions; it does guarantee that someone is responsible for making them.

Speed under pressure. When a situation demands a fast, unambiguous call, the deliberation cost that consensus-oriented structures must pay becomes prohibitive. A clear chain of command removes that cost. Information flows up, authority flows down, and execution proceeds without negotiating who has the right to decide. Hierarchies outperform flatter structures precisely in the conditions that most stress organizations: time-scarce, high-stakes moments where the price of getting the process right exceeds the price of getting the answer slightly wrong. This is why military command doctrine and emergency response systems retain strong hierarchical architecture even as their cultures have evolved significantly in other respects.

Scalability beyond the cognitive ceiling. The mathematics of human relationships impose a hard constraint on coordination. Every new member added to a group multiplies the number of potential communication links by n(n-1)/2, meaning a team of 10 has 45 potential pairings while a team of 150 has more than 11,000. Robin Dunbar's research established that the human brain can maintain stable social relationships with roughly 150 people, with meaningful inner layers at approximately 5, 15, and 50. Hierarchy is the structural mechanism that makes coordination above that ceiling possible, not by eliminating the constraint, but by nesting smaller coherent units inside larger ones so that each person only needs to maintain relationships within their local layer. Without that nesting architecture, organizational structure breaks down under its own communicative weight, as two independent field studies across 56 and 67 work teams confirmed: team structure positively predicts performance by improving coordination, with the effect amplified as teams mature.

Flat structures obscure hierarchy; they do not remove it. This point deserves particular emphasis because the flat-structure movement has often presented itself as a clean alternative rather than a trade-off. When formal power gradients are removed, informal ones re-emerge, typically organized around charisma, tenure, technical expertise, or proximity to key information. The difference is that informal hierarchies are unacknowledged and therefore harder to challenge or correct. Holacracy implementations have repeatedly surfaced this dynamic: the managerial work does not disappear; it gets redistributed to employees and teams who must now absorb responsibility for coordination, prioritization, and conflict resolution without the structural support to do it consistently. Even the most celebrated flat alternatives retain hierarchical scaffolding at their core. The question was never hierarchy or no hierarchy; it was always which hierarchy, designed how.

The honest foundation for critique. The steelman case for a hierarchical organizational structure rests on coordination theory, cognitive science, and communication mathematics, not on tradition or deference to authority. A rigorous analysis of organizational structure acknowledges these advantages as structural, not incidental. Any serious critique of hierarchy must start from this acknowledgment, because the alternative is to argue against a caricature. The Cone Model's framework does exactly this: it accepts the triangle of positional authority as structurally necessary, then asks what the triangle alone cannot provide, and builds from there.

Where Hierarchical Structure Breaks — Precisely

The strengths catalogued in the previous section are real, but they operate within boundaries. When those boundaries are exceeded, hierarchy does not merely become less efficient; it begins to generate predictable, structural damage. The failure points are not random. They follow geometry.

The Cognitive Ceiling on Span of Control

Research consistently places the optimal span of control between 5 and 10 direct reports, the threshold beyond which coordination costs begin to outweigh productivity gains. A 2025 peer-reviewed study published in Work examined first-line healthcare managers across a repeated cross-sectional design and found that expanded span of control is directly associated with increased work-related stress, reduced job satisfaction, and degraded leadership performance. This is not a soft finding; it is longitudinally credible evidence that overloading span damages both the leader and the quality of what the leader can provide.

The cognitive science parallel sharpens the picture. Humans can hold approximately 7 items, plus or minus 2, in working memory at any one time. That is not a management opinion; it is a documented constraint in cognitive architecture. When direct reports exceed that number, the leader faces something more serious than a workload problem. Attention itself becomes the binding constraint, and span-of-control analysis confirms that this cognitive limit has a direct structural counterpart in how many people any single leader can meaningfully manage. The numbers converge for a reason.

What Hierarchy Cannot Deliver Downward

Span of control analysis typically asks how many reports a leader can supervise. It rarely asks what, precisely, a leader can actually provide. This is where a more fundamental structural gap appears.

Of the 21 things people need to flourish at work, only 7 require the leader directly: Direction, Vision, Mission, Mentoring, Reward, Advocacy, and Autonomy. The remaining 14, including Belonging, Safety, Correction, Teamwork, Trust, Training, Recognition, Friendship, Encouragement, Accountability, Celebration, Challenge, Forgiveness, and Care, must be generated peer-to-peer. Hierarchy cannot deliver them downward from a single apex. They are lateral in nature; they require people at the same level to provide them for one another. A hierarchical design that does not provision for horizontal peer relationships structurally blocks the majority of what human beings need to do their best work. The leader, no matter how skilled or attentive, cannot compensate for an architecture that suppresses the conditions under which those 14 needs are met.

The Geometry Problem at the Top

Most span-of-control literature optimizes in one direction: downward. It asks how many reports a manager can handle. It does not ask what happens to the person at the apex as the hierarchy grows taller. This is the most conspicuous analytical gap in conventional management thinking, and it is consequential.

As layers accumulate, the leader's altitude increases and the number of genuine peer relationships available decreases. There are simply fewer people at an equivalent level. The relational pool at the top is shallow by design. This is not a character flaw, and it is not solved by coaching the leader to be more open or more connected. It is a geometry problem, built into the structure itself.

CTO Tal Rotbart identified this mechanism precisely in February 2026: organizations hit a cognitive ceiling not because of total headcount but because of the size of internal relationship networks. Once that network exceeds cognitive capacity, performance degrades. Critically, the instinct to substitute process for structural redesign, adding approval layers, reporting frameworks, and documentation requirements as workarounds, makes the problem measurably worse. Process increases coordination costs rather than resolving the underlying design flaw.

The leader at the top of a mature hierarchy is not lonely because of personal limitations. The structure produced that outcome from the moment the first extra layer was added.

The Oldest Documented Fix: Jethro's Counsel to Moses (Exodus 18)

The scene in Exodus 18 is deceptively simple: Moses sits from morning until evening adjudicating disputes for an entire nation, while the people queue in the heat and his father-in-law Jethro watches. What Jethro says next is the oldest documented piece of management advice in the Western canon, and its logic remains structurally precise some 3,400 years later.

Notice what Jethro does not say. He does not tell Moses he lacks faith, discipline, or leadership character. He does not prescribe rest, reflection, or a wellness practice. His diagnosis is architectural: "What you are doing is not good." The system itself is broken. One person is absorbing every judgment, every dispute, every relational and decisional load for a community of hundreds of thousands, and there is no tiered structure beneath him to distribute that weight. Moses is exhausting himself, and the people are standing all day. The damage is bilateral, and the cause is not personal failure; it is a design flaw.

A Prescribed Structure That Anticipates Modern Science

The cure Jethro prescribes is explicit and tiered: appoint capable leaders over groups of ten, fifty, one hundred, and one thousand. Simple cases are resolved at the lowest tier; only the genuinely hard ones escalate to Moses. This is not a vague exhortation to delegate more. It is a nested hierarchy of delegated authority, with defined spans at each level and a clear escalation protocol. The leadership lessons embedded in Jethro's advice to Moses show that the prescribed tiers map strikingly onto what Robin Dunbar would identify roughly three millennia later as humanity's nested relational layers: the intimate group of roughly five, the sympathy group of around fifteen, the band of fifty, and the community threshold of approximately one hundred and fifty. Jethro did not have neuroscience; he had observation. The structural conclusion was identical.

Load Distribution, Not Succession Planning

A critical distinction often missed in readings of Exodus 18 is that Jethro's model implicitly defines a deputy function at every tier. Moses retains jurisdiction over the hardest cases; real authority, not advisory input, is delegated downward to leaders selected for character, trustworthiness, and integrity. This is not succession planning. It is structural load distribution: a recognition that the apex cannot and should not bear the full relational and decisional weight of an organization, and that genuine authority must reside at each tier for the structure to hold. The character criteria Jethro specifies for tier leaders reinforces that this delegation is substantive, not cosmetic.

The Structural Precedent That Changes the Argument

The historical weight of this text matters analytically. Frederick Winslow Taylor published his Principles of Scientific Management in 1911. Henri Fayol's administrative theory appeared in 1916. Every modern organizational behavior framework, every management consulting methodology, every leadership development curriculum in existence postdates Exodus 18 by at least three thousand years. And the oldest documented management intervention in that canon is not a call for better personal qualities in the leader. It is a structural redesign.

That precedent carries a pointed implication: if the first recorded answer to leadership overload was to fix the architecture rather than the person, the burden of proof falls on those who argue that personal development is the primary variable. The Cone Model's span cycle, which narrows fractally as organizational altitude rises and resets to a full relational circle at each order of magnitude, is the modern articulation of the same structural insight Jethro reached by watching Moses work.

 

Dunbar's Nested Layers and the Fractal Span Cycle

Dunbar's Nested Layers and the Fractal Span Cycle

Robin Dunbar's research did not simply identify a ceiling. It identified a nested architecture, and that distinction changes everything about how organizations should be designed.

The four primary layers sit at approximately 5, 15, 50, and 150 people. Each threshold represents a qualitatively different kind of relationship, not merely a larger quantity of the same thing. The innermost circle of roughly five individuals receives close to 40% of a person's total relational energy; the next ten absorb a further 20%, meaning 60% of relational investment is committed to just fifteen people. Move to the 50-person layer and the ties are real but noticeably thinner; at 150, the relationship is recognizable but requires consistent structural reinforcement to remain stable. As Dunbar's own work and subsequent BBC reporting confirm, 150 alone does not tell the whole story, because the nested layers within it determine the actual texture of organizational life.

Why the Layers Are Not Arbitrary

These thresholds appear consistently because they are grounded in neuroscience, not sociology. The size of the human neocortex sets a hard ceiling on the complexity of relationships a person can actively maintain. This is why the same layered groupings appear in hunter-gatherer societies, Roman military units, religious communities, professional sporting squads, and corporate divisions. A 2025 peer-reviewed study in PLoS One examining individual differences in relational energy allocation confirmed that while individuals vary (the outer layer ranges from roughly 100 to 200 depending on personality), the structural scaffolding of the layers themselves remains consistent. The variation is in density, not in the existence of the thresholds. Organizations that ignore this are not simply making a management error; they are working against cognitive architecture that has remained stable across millennia.

Relational Physics, Not Hierarchical Preference

The Cone Model's fractal span cycle maps directly onto this architecture. The span of roughly ten at the base, narrowing to approximately five at the next altitude, then to two at the apex, follows Dunbar's layers with structural precision. This narrowing is not a preference of senior leaders or a symptom of their remoteness; it is what genuine trust costs at each scale. As Tal Rotbart argued in February 2026, organizations do not freeze because of total headcount but because informal trust networks cross Dunbar thresholds without any structural redesign to absorb the crossing.

Critically, the Cone Model identifies that relational load does not simply fade as altitude rises. It oscillates. At each power of ten, the span resets to a full circle of roughly ten, so a leader moving from managing a team of ten to leading a unit of one hundred experiences a temporary relational expansion before the narrowing resumes. This oscillation explains why certain leadership transitions feel structurally harder than others, not because of personal capability gaps, but because the relational geometry has genuinely shifted.

The Design Implication

The practical conclusion is not to flatten the hierarchy. Flatness without relational architecture simply redistributes the isolation. The design question is more precise: at each layer of the organization, are the fourteen peer-generated needs (belonging, safety, trust, accountability, friendship, encouragement, and the rest) being met horizontally, between peers, or are they being routed upward through an apex that was never designed to carry them? When the answer is the latter, no amount of leadership coaching or cultural initiative resolves the problem. The structure itself must be designed so that each layer generates its own relational sufficiency, with the apex freed to supply only what peers genuinely cannot provide for one another.

 

The Cone Model as the Modern Version of the Same Insight

The Cone Model as the Modern Version of the Same Insight

The Cone Model takes the pattern Jethro identified, the span cycle Dunbar's research quantified, and the fractal geometry visible in Roman and military unit structure, and synthesises them into a single organizational shape. That shape is the cone: a triangle representing positional authority and downward direction, with a circle representing horizontal peer trust and mutual support, reconciled inside one structure. Viewed from the side, it is a hierarchy. Viewed from above, it is a team. The insight is that these two shapes are not competing philosophies requiring a compromise. They are the same organization seen from different angles, and both are structurally necessary.

What the Triangle Alone Cannot Deliver

The triangle is what most organizations already have. It provides the clarity, accountability, and directional force that the previous sections established as genuine strengths of hierarchical structure. What it cannot provide is the other two-thirds of what people need to flourish at work. The Cone Model identifies 21 conditions required for people to thrive professionally. Seven of those conditions must come from the leader: Direction, Vision, Mission, Mentoring, Reward, Advocacy, and Autonomy. The remaining fourteen, including Belonging, Safety, Teamwork, Trust, Friendship, Recognition, Encouragement, Accountability, and Care, are generated peer-to-peer within a healthy circle. No leader can manufacture these from above. The arithmetic is instructive: with ten direct reports, attempting to provide all 21 elements personally creates 210 care touchpoints. That load does not stretch a leader; it breaks them. The circle is not a cultural supplement to good leadership. It is the structural mechanism that delivers the majority of what people actually need, and it only exists if it is designed in.

The Missing Piece at the Apex

The most consequential structural addition the Cone Model makes is at the top, not the bottom. At the apex of every cone sits not one leader but two: a leader and a genuine deputy holding real delegated authority. This is the element that the Cone Model framework identifies as the structural cure for leadership isolation, and it maps precisely onto Jethro's prescription for Moses. Jethro did not advise Moses to become more resilient, more emotionally intelligent, or more efficient with his time. He told Moses to stop standing alone. The deputy role does exactly that. Critically, this is not succession planning and should not be treated as such. A succession plan is about organizational continuity after a leader departs. A genuine deputy is about structural completeness while the leader is present. Without a peer at the apex who holds real authority and provides genuine reciprocal support, the top of any hierarchy is lonely by design. The leader's personality, coaching investment, or self-awareness cannot solve a structural deficit.

Fractal Completion at Every Altitude

The geometry does not apply only at the top. Cones stack fractally: the same triangle-plus-circle structure repeats at every tier of the organization. Each leader at each altitude has both a positional authority structure pointing downward and a relational peer structure extending horizontally. This is the insight that prevents the relational model from becoming a base-of-pyramid privilege, where senior leaders remain isolated while only front-line teams experience genuine belonging. You can explore how this plays out in practice through a practical examination of the cone model for team support networks, which illustrates the repeating geometry at the team level.

The Cone Model does not replace hierarchical organizational structure. It completes it. A triangle without a circle is a machine for producing isolated leaders and underserved peer needs, regardless of how talented the people inside it are. Adding the circle does not soften the hierarchy or dissolve accountability. It gives the hierarchy the structural conditions under which both leaders and teams can actually do what they are there to do.

What This Means for Leaders Inside a Hierarchy Today

The analysis developed across the preceding sections has a practical endpoint: three diagnostic questions every leader inside a hierarchical organizational structure can apply today, without waiting for a structural overhaul to begin.

The Span Audit

Start with the most measurable variable in any hierarchy: how many direct reports does each leader actually manage, and at which points does that number exceed relational capacity? Dunbar's nested layers establish a biological ceiling, not a theoretical one. Humans sustain roughly five intimate relationships, fifteen close ones, and fifty active social contacts before cognitive load collapses the quality of connection. The Cone Model's fractal cycle maps onto those layers directly, narrowing from approximately ten at the first tier to five at the next altitude and two at the apex. When a mid-level leader carries twelve or fourteen direct reports, the span audit makes visible what intuition has already registered: meaningful relational management at that count is structurally impossible, not a reflection of the individual leader's capability. Audit every tier. Mark the overloaded nodes. The span audit converts an invisible design flaw into a legible one.

The 7/14 Check

The second diagnostic targets the distribution of relational work across the organization. Of the twenty-one things people need to flourish at work, only seven require the leader directly: Direction, Vision, Mission, Mentoring, Reward, Advocacy, and Autonomy. The remaining fourteen, including Belonging, Safety, Friendship, Accountability, Encouragement, and Care, are peer-generated by design. They emerge from horizontal relationships within well-structured teams, not from vertical authority. When horizontal peer trust is absent or underdeveloped, those fourteen needs migrate upward. Leaders find themselves absorbing demands they were never structurally positioned to meet, and research confirms that leader loneliness correlates directly with the number of trusted colleagues available within the institution, not with personal resilience or professional experience. The 7/14 check asks one pointed question: which of those fourteen peer-generated needs are genuinely being met horizontally in your organization, and which are quietly queueing at the leader's door?

The Apex Test

The third diagnostic focuses on the very top of the structure. Does the most senior leader in the organization have a genuine deputy with real delegated authority, or is there a nominal second-in-command who holds no independent relational or decisional weight? The Cone Model places two people at the apex, not for succession planning purposes, but because the structural cure for the apex leader's own isolation is a genuine peer with shared responsibility. A deputy in title only does not solve the design problem; it decorates it.

Two free assessments on theconemodel.com are built precisely for this diagnosis. The Proximity and Lone-Wolf Check surfaces whether a leader is structurally isolated or relationally embedded. The Find Your Deputy assessment identifies whether a genuine deputy relationship exists or whether the apex remains, by design, alone. Both tools give leaders a concrete starting point, and both reframe the finding in the same direction: isolation at the top is a design problem, not a character flaw.

That reframing is the shift that matters most. If leadership loneliness is structural, the solution is not more coaching, more resilience training, or a reflexive flattening of the org chart. Flat structures without relational architecture leave peer networks unsupported and leaders just as isolated, only without the clarity of reporting lines. The solution is deliberate redesign of the relational architecture at every altitude in the hierarchy, tier by tier, span by span, with a genuine deputy at the apex and fully functioning peer circles at every level below it.

Structure Is Not the Enemy — Incomplete Structure Is

The evidence assembled across this analysis points to a single, precise conclusion: the hierarchical organizational structure is not the problem. The absence of its completing layer is. Hierarchy is mathematically justified by network coordination costs, anthropologically inevitable once groups exceed the cognitive limits Dunbar quantified, and historically ancient in a lineage running from Jethro's tiered spans through Roman cohort design to modern military units. Dismissing it in favor of flat structures does not solve the structural problem; it relocates the dysfunction while removing the accountability clarity that hierarchy genuinely provides.

The precise failure mode is the triangle without the circle. When the positional authority structure operates without a horizontal relational layer, 14 of the 21 things people need to flourish at work go unmet, because those needs (belonging, safety, trust, friendship, correction, care, and eight others) are peer-generated and cannot be delegated downward from any apex leader. The leader simultaneously becomes structurally isolated, not through personal inadequacy, but through design.

Jethro identified the structural cure three thousand years ago. Dunbar's research gave it a cognitive science foundation. The Cone Model gives it a fractal, deployable architecture with a genuine deputy at the apex as the structural remedy for leadership isolation. If you observe loneliness at the top of your organization, treat it as a design signal, not a personal failure. Begin the structural diagnosis with the free Full Cone 360° or Find Your Deputy assessment at theconemodel.com.

Frequently Asked Questions

Q: Why does hierarchy exist in the first place?

A: Hierarchy is a mathematically driven solution to a real coordination problem — as groups grow, the number of potential communication pathways between members increases faster than the group itself, and hierarchy compresses those pathways by routing decisions through designated nodes.

Q: What is the optimal span of control for a leader?

A: Research consistently places the optimal span of control between 5 and 10 direct reports — beyond that, coordination costs begin to outweigh productivity gains, and the leader's cognitive capacity for genuine relational attention is exceeded.

Q: What did Jethro's advice to Moses have to do with modern organizational design?

A: In Exodus 18, Jethro told Moses to distribute his overwhelming leadership load across tiers of ten, fifty, hundred, and thousand rather than trying to personally judge every case. This is the earliest documented structural fix for leadership overload, and it anticipates Dunbar's modern research on relational capacity by roughly three millennia.

Q: Can flattening a hierarchy solve leadership isolation?

A: No — the Cone Model argues that flattening relocates the isolation rather than resolving it. Removing formal layers doesn't create the horizontal peer relationships a leader needs; it just removes the clarity hierarchy provided, without replacing the missing genuine deputy relationship at the top.

Buy Now on Amazon Take the free 360° Assessment About the Book