Article 02: The Hidden Cost of Organizational Complexity
Nobody decided to make the organization complex. It became complex through thousands of individually reasonable decisions made over years by people who wer...
Get started
The numbers looked exactly right. Revenue was up eighteen percent year over year. The sales team had exceeded its targets for three consecutive quarters. New customer acquisition was strong. Retention was holding. Every metric that leadership tracked pointed toward an organization performing at a high level.
Then two things happened in the same quarter. A key account that represented fourteen percent of revenue gave notice. And a competitor entered the market with a pricing structure the sales team had no prepared response to.
Within six months, the organization that had appeared so strong was in the middle of an emergency restructuring. Costs that had been invisible during the growth period were suddenly very visible. Processes that had never needed to be efficient because volume covered their inefficiency were now exposed. The workforce structure that had been added layer by layer during the growth years was consuming cash the business no longer had the revenue to support.
The growth had not been concealing weakness. It had been funding it.
Revenue growth produces a specific kind of organizational confidence that is difficult to challenge from inside the institution. When the top line is moving in the right direction, the natural interpretation is that the strategy is working, the execution is sound, and the organization is healthy. Leaders who raise concerns about underlying structural issues during growth periods are often dismissed as overly cautious or insufficiently aligned with the momentum the business is building.
This dynamic is understandable. Growth is genuinely positive. It creates optionality, funds investment, and validates commercial strategy. The problem is not that leadership celebrates growth. The problem is that growth is treated as evidence of organizational health rather than as a separate condition that can coexist with significant structural problems.
The two are not the same thing. An organization can grow revenue while simultaneously accumulating structural costs that will become visible when growth slows. It can expand its customer base while building a workforce structure that was never designed efficiently. It can increase margin percentages while creating operational dependencies that will become fragile under stress. Revenue growth tells leadership that the commercial engine is working. It tells them very little about the structural condition of the organization that commercial engine is running on.
The organizations that learn this lesson most painfully are the ones that allow structural problems to accumulate for years behind the cover of strong revenue. When growth eventually normalizes or reverses, those problems do not gradually emerge. They arrive simultaneously and at a scale that reflects years of deferred attention.
Not all structural problems accumulate at the same rate or in the same areas during revenue growth periods. Some are more reliably produced by growth itself and more reliably concealed by it.
Workforce structure is one of the most consistent. When revenue is growing, organizations add headcount in response to demand. Each addition is individually justified. A new account requires additional support. A new product line requires dedicated resources. A new geography requires local presence. The additions feel like investment rather than cost because they are connected to specific revenue-generating activities.
What accumulates over time is a workforce architecture that was never designed as a whole. Roles that overlap. Layers of management that were added to supervise additions that were added to supervise earlier additions. Support functions that expanded to serve a scale of operation the business may no longer sustain. The workforce grew with the revenue but it did not grow with the same deliberateness. It grew reactively, and reactive growth produces structural inefficiency that is invisible when revenue is covering it.
Process complexity is a second area. Organizations under growth pressure typically solve problems by adding process rather than redesigning it. A coordination breakdown between two teams produces a new approval requirement. A quality issue produces a new review layer. A compliance requirement produces a new reporting obligation. Each addition is a reasonable response to a real problem. Collectively they produce a process landscape that is significantly more complex than the organization’s actual operating requirements justify.
Cost structure is a third. During growth periods, organizations make commitments that reflect their growth trajectory rather than their current operating reality. Leases are signed for space the business expects to need. Technology contracts are structured at scale. Compensation expectations are set in a market where the business was competing for talent with confidence in its trajectory. When growth slows, these commitments do not slow with it. They continue drawing cash at the rate they were established, against a revenue base that may no longer support them.
The metrics that most leadership teams track during growth periods are calibrated to measure growth rather than structural health. Revenue, margin, customer acquisition, retention, and pipeline are all forward-looking commercial indicators. They tell leadership whether the business is growing. They do not tell leadership whether the organization supporting that growth is structurally sound.
The metrics that would reveal structural weakness are harder to track and less intuitively connected to organizational health. Revenue per employee trends that are declining even as total revenue increases. Management span ratios that are narrowing as layers multiply. Process cycle times that are lengthening as coordination requirements expand. Fixed cost as a percentage of revenue that is creeping upward even when margin percentages hold.
These indicators are available in most organizations. They are rarely assembled into a coherent view of structural health and presented alongside the commercial metrics that dominate leadership attention. The result is that leadership has an excellent view of how the organization is performing commercially and a very limited view of how the organization is performing structurally.
This asymmetry is not intentional. It reflects how performance management systems are designed. They are built to measure and communicate commercial performance because that is what drives the decisions that most leadership teams are primarily responsible for. Structural health is assumed to be the responsibility of functional leaders who are each managing their own domain and none of whom have a mandate to assess structural health across the enterprise.
“We had dashboards for everything that mattered commercially. We had nothing that showed us what the organization was actually costing us relative to what it was producing. That gap was where the structural problems lived.”
Structural weakness inside a growing organization does not look like failure. It looks like normal organizational behavior operating at slightly below its potential. Teams that are busy but not as productive as their size suggests. Decisions that take longer than they should because ownership is unclear. Coordination between functions that requires more effort than seems necessary. Cost that grows slightly faster than revenue in ways that feel explainable but never fully resolve.
None of these are crisis signals. Each has a plausible local explanation. The team is busy because demand is high. Decisions are slow because the issues are complex. Coordination is difficult because the work is genuinely interdependent. Costs are growing because the business is investing in its future.
The explanations are often partially accurate. They are also partially a reflection of structural problems that have been normalized over time. The organization has adapted to operating at a level of structural inefficiency that feels like how organizations work rather than how this particular organization is performing relative to its potential.
The businesses that identify and address structural weakness before it becomes a crisis are the ones that look beneath the revenue line with the same discipline they apply to growing it, and how revenue discipline reveals structural performance gaps is often where the most consequential organizational insights are found.
Recognizing structural weakness during a growth period requires leadership to ask questions that feel uncomfortable when the commercial performance is strong. Not because the answers are likely to be catastrophic, but because the act of asking them disrupts the narrative of organizational health that growth produces. It requires separating commercial performance from structural performance and being willing to find that the two are diverging.
The organizations that do this well treat structural health as a standing agenda item rather than a crisis response. They build the visibility to see structural trends as they develop rather than after they have accumulated into problems that require emergency attention. And they create the leadership culture in which raising structural concerns during growth periods is treated as strategic insight rather than organizational pessimism.
“The growth gave us permission to not look too carefully at the organization underneath it. When the growth slowed, we discovered that permission had been expensive.”
Revenue growth is a genuine achievement. It represents commercial execution, customer value, and strategic progress. But it is not organizational health. The two can coexist. They can also diverge significantly over time in ways that only become visible when the growth that was covering the divergence is no longer present to do so.
Nobody decided to make the organization complex. It became complex through thousands of individually reasonable decisions made over years by people who wer...
Get started
In most organizations, labor is the largest single cost on the income statement. It typically represents between forty and seventy percent of total operati...
Get started