Most growing companies don't have a people problem. They have a structure problem. The wrong org design creates confusion, redundancy, and a management layer that slows everything down instead of accelerating it.
Book a Free Strategy Call →Early in my career managing operational teams across healthcare and aerospace, I learned something counterintuitive: the most expensive resource problem isn't an unfilled position. It's the person in the wrong role. An empty seat creates a workload gap. A person in the wrong seat creates confusion, rework, friction, and often drives away the talented people around them who have to compensate for the misfit.
Wrong-seat problems compound in growth-stage companies because they're often invisible for a long time. The person in the wrong seat is usually trying hard. They may even be technically competent. But their strengths are misaligned with what their role actually demands, and the gaps show up slowly: in missed deadlines, in communication breakdowns, in the quiet frustration of team members who know something isn't working but can't articulate what.
The financial cost is significant. A wrong-seat hire at the manager level costs, on average, 1.5 to 2 times their annual salary when you factor in lost productivity, management time, hiring and onboarding of a replacement, and the cultural damage done in the interim. At the director or VP level, the cost is even higher. And yet most companies invest almost no time in systematic role clarity before they hire.
This is one of the first areas I address in any team structure engagement. Before we talk about hiring plans or org charts, we audit who is currently in what seat and whether the seat itself is correctly defined. You cannot put the right people in roles that are poorly designed. Role design comes before talent selection, and most companies get that backward.
When I begin an organizational design engagement, I approach it the same way I approach any operational audit: with curiosity before conclusions. The worst thing a Fractional COO can do is walk in with a predetermined org chart template and try to fit a living business into it. Every company has its own history, culture, informal power structures, and interdependencies. The audit surfaces those realities before any redesign begins.
The org design audit has four components. First, I map the current structure - not the org chart on paper, but the actual decision-making and communication patterns. Who actually approves things? Who do people go to when they have a problem? Who has informal authority that isn't reflected in their title? These shadow structures often reveal more about how a business functions than any formal reporting chart.
Second, I conduct individual role analysis. I interview each person in a leadership or management role to understand what they actually spend their time on, what decisions they make independently, what decisions require approval, and where they feel the most friction. The gap between job descriptions and actual work is almost always significant, and that gap is operational drag with a dollar cost attached to it.
Third, I analyze workload distribution. In most growth-stage companies, work is severely imbalanced. A handful of high performers carry an outsized share of the output while other roles are underutilized. This creates burnout risk, single points of failure, and a culture where initiative isn't rewarded because the reward is more work.
Fourth, I evaluate the span of control at each management level. Managers with too many direct reports cannot coach effectively. Managers with too few are often over-involved in execution and become bottlenecks. Getting the span of control right - typically four to eight direct reports depending on the complexity of each role - is one of the highest-leverage adjustments in organizational design.
One of the most undervalued exercises in organizational design is writing genuinely useful role definitions. Not job descriptions designed to attract candidates - those serve a different purpose. I mean internal role charters that define the scope of authority, the key decisions the role owns, the outputs the role is accountable for, and the interfaces with other roles in the organization.
The distinction between authority and accountability is critical and frequently confused. Authority is the right to make a decision. Accountability is ownership of the outcome. In poorly designed organizations, these are misaligned: people are held accountable for results they have no authority to influence. This is the single most common source of leadership frustration I encounter. When someone is responsible for a metric they cannot control, the result is either learned helplessness or political behavior, neither of which serves the company.
I build what I call an accountability architecture for each engagement - a clear map of who owns what decisions at what level of the organization, what inputs each decision requires, who needs to be consulted versus merely informed, and what escalation path exists when a decision exceeds the authorized scope. This framework, sometimes called a RACI matrix though I find that term overused and often misapplied, creates the structural clarity that allows teams to operate autonomously without creating chaos.
Role charters also define success metrics for each position. Not activity metrics - outputs. A sales role is accountable for revenue generated and pipeline quality, not calls made. A marketing role is accountable for qualified leads and brand metrics, not content pieces published. A customer success role is accountable for retention and expansion revenue, not response times. Outputs-based accountability is the foundation of high-performance team culture, and it starts with how roles are defined.
"The org chart is not the organization. The real structure is the pattern of decisions, handoffs, and accountability that runs through a company every day. Designing that correctly is worth more than any hiring plan."
The team structure that works at ten employees will break somewhere between twenty and thirty. This is one of the most predictable scaling failure points in business, and yet it surprises companies every time it happens. The reason is that organizations at ten people typically operate without formal structure - everyone talks to everyone, the founder is in every decision, and it works because the team is small enough for coordination to happen informally. As headcount grows, that informal coordination system collapses.
The transition from ten to twenty-five employees requires the introduction of genuine management infrastructure for the first time. This means defining functional departments, establishing management roles with real authority, creating cross-functional coordination mechanisms, and shifting the founder or CEO out of operational decision-making and into strategic leadership. Each of those transitions is uncomfortable, and most companies resist them until forced by crisis.
I help companies get ahead of that curve. The 25-to-50 employee range requires a different structural evolution: the introduction of a management layer between frontline employees and senior leadership, the formalization of departmental OKRs, and the development of middle managers who can lead without constant executive direction. Building this layer is one of the most challenging parts of organizational design because it requires promoting people who have been strong individual contributors into roles that demand fundamentally different skills - and managing them through that transition.
At 50 and beyond, the structure must be designed for delegation and division of authority. The CEO cannot know everything that's happening. The organization needs leaders at every level who can make sound decisions within their domain, escalate appropriately when they can't, and coordinate effectively across departments. Building that capability is a multi-year investment in leadership development that needs to start well before you reach 50 people.
The management layer is where most organizational design problems concentrate. Individual contributors who are promoted into management without proper support, development, or role clarity become the primary source of operational dysfunction in growing companies. They manage the way they were managed, which is often poorly. They protect their teams from accountability because they don't understand that accountability is a service, not a punishment. They make decisions they shouldn't and avoid decisions they should make.
I have seen this pattern more times than I can count, in companies across healthcare, logistics, aerospace, and technology. The solution is not to hire externally for every management role - that's expensive, slow, and culturally disruptive. The solution is to build a management operating system that defines clearly what managers do, how they're expected to lead, and what support they receive to develop their capabilities.
A management operating system includes: structured one-on-one meeting cadences with a defined agenda, team meeting structures that focus on problem-solving rather than status reporting, clear performance management protocols including how to give feedback and how to escalate performance issues, and a leadership development curriculum that builds the skills managers need over time. Most companies have none of these. Building them is Fractional COO work.
The other critical management layer problem is what I call the approval bottleneck. When managers don't trust their own authority - or when the organization hasn't made clear what they're authorized to decide - every small decision escalates upward. This creates queues at the executive level that slow down operations, demoralize the team, and force senior leaders into tactical work that keeps them from strategy. Fixing approval bottlenecks requires role clarity, authority definition, and a CEO or founder willing to genuinely let go of decisions that are below their pay grade.
Organizational restructuring carries risk. The wrong approach to a reorganization can destroy morale, trigger unwanted attrition, destabilize customer relationships, and set productivity back by six months. I have seen poorly managed restructurings do more damage than the problems they were meant to solve. But a well-managed restructuring, executed with clear communication and deliberate sequencing, can be one of the highest-leverage investments a company makes in its operational foundation.
The first principle of transition planning is to never restructure in a vacuum. Every change to team structure should be connected to a clear business rationale that the team understands. "We're reorganizing to better serve our enterprise customers" or "We're creating this new function because we're entering a new market" are clear rationales. "We're restructuring because leadership wants to" is not, and employees will assume the worst when they don't understand the why.
The second principle is sequencing. I typically recommend a phased approach that runs over 60 to 90 days: phase one announces the new structure and roles at the highest level, answers the most urgent questions (who reports to whom, what happens to my current role), and gives individuals time to process; phase two handles individual role transitions with specific conversations, updated role charters, and clear timelines; phase three addresses process and system changes that flow from the new structure. Trying to do all of this simultaneously creates chaos.
The third principle is protecting your high performers through the transition. The people most likely to leave during a restructuring are your best employees, because they have the most options. Proactive retention conversations, clear signals about their place in the new structure, and genuine acknowledgment of the disruption the change creates are all non-negotiable. Losing one top performer to a botched restructuring can cost more than the entire restructuring was designed to save.
If your organization is growing faster than your structure can support, let's fix that before it breaks. I'll audit your current org design, identify the critical gaps, and build the accountability architecture your next stage demands.
Book a Free Strategy Call →