Healthy Growth vs. Swelling

Healthy Growth vs. Swelling

There is a form of organizational growth that looks unmistakably healthy on the surface — headcount is up, revenue is up, the office is busier, the calendar is fuller — and is, on closer inspection, something quite different. The growth is real in the sense that the organization is larger than it was. But the growth has not been integrated. The new people have not developed into the culture and the operating model. The new clients have not been served consistently enough to know whether the model scales. The new processes were created in response to immediate pressure and have never been reviewed to see whether they actually work well or just work at all. The organization is bigger. It is not stronger. 

This is what I mean by swelling rather than growing. Swelling is size increase that has outpaced the organization’s structural capacity to absorb it. It produces the appearance of success — and in many cases, the metrics of success — while the underlying organization is becoming progressively less coherent. The people who have been there longest tend to feel it first: things that used to work simply do not work the same way anymore, the culture is different in ways that are hard to name, the decisions that used to get made quickly now require three conversations and a committee, and nobody is quite sure who owns what anymore. 

The distinction between growth and swelling matters for how leaders diagnose what is actually happening in their organization, and what they should do about it. 

The Diagnostic Questions 

Distinguishing healthy growth from swelling requires asking a different set of questions than the ones that normally appear in a growth review. 

The typical growth-review questions are quantitative: how much did revenue grow, how many people did we add, how many new clients did we bring on, what is the expansion rate. These are legitimate questions. They are also almost entirely silent about whether the organization is becoming more capable as it grows or simply larger. 

The diagnostic questions for distinguishing growth from swelling are about integration and coherence. Are the people we added in the last twelve months operating at the level of effectiveness we expected by now? When something goes wrong — a client is unhappy, a delivery is late, a process breaks down — is the root cause something we would have caught before we grew, or is it a symptom of something that emerged from the growth itself? Is the quality of our delivery to existing clients holding steady as we serve more of them, or are we noticing quiet degradation that we are attributing to other causes? 

These questions are harder to answer than the quantitative ones, because they require honest observation of what is actually happening inside the operation rather than review of what the reports are showing. They require the willingness to look at the client who has been slightly less engaged than usual and ask whether that is about them or about a change in how we are serving them. They require the willingness to look at the employee who is performing below what they are capable of and ask whether the environment has set them up to succeed or whether the growth created conditions they cannot thrive in. 

The Technology Signal 

For technology and security companies specifically, there is a concrete indicator of swelling that is worth watching: the relationship between the growth rate and the evolution of the security and technology infrastructure that supports the growing organization. 

Healthy growth maintains or improves the coherence of the technology environment because the organization is deliberate about evolving its infrastructure alongside its scale. New clients are onboarded into a documented, consistent process. Security controls are reviewed and updated as the environment changes. The identity and access architecture reflects the current organization rather than the organization as it was configured two years ago. Data handling practices are current with the compliance requirements applicable to the current business, not the requirements that were applicable when the last review was done. 

Swelling, by contrast, tends to produce technology and security environments that have grown faster than the architecture. There are systems added during rapid expansion that were never fully integrated. There are users and permissions that were created during onboarding surges and never cleaned up. There are security controls that were adequate for the previous scale but are not adequate for the current one. There are compliance obligations that have emerged as the client base expanded into new verticals that the security program has not caught up to yet. 

The gap between where the technology and security infrastructure is and where it needs to be at the current scale is one of the clearest indicators of organizational swelling, because it is a domain where the shortcuts taken during rapid growth are visible to anyone who looks carefully. The organization that has been growing in a controlled way has been maintaining the infrastructure alongside the growth. The organization that has been swelling has been deferring the infrastructure decisions because there was always something more urgent to address. 

The Momentum Problem 

One of the things that makes swelling difficult to diagnose and address is that the momentum of growth creates very strong internal pressure to continue doing what is producing the growth, even when what is producing the growth is not sustainable. 

When revenue is increasing, when new clients are being added, when the team is expanding — the signals are all positive, and the suggestion that the organization needs to slow down and consolidate is countercultural. It feels like a counsel of excessive caution. The leaders who are managing the growth and proud of what they have built are not naturally receptive to the argument that something about the way the growth is happening is going to cost them later. The clients who are happy with the relationship they have are not monitoring whether the quality of the service they receive is as consistent as it was when the organization was smaller. 

The time to diagnose swelling is not when it has already become visible in client retention or employee turnover. It is while the organization is still growing, when the momentum is still strong enough to allow for deliberate consolidation without the crisis urgency that makes everything harder. The leader who can hold the question — are we growing or are we swelling — during the period when everything looks good is the leader whose organization tends to be stronger three years later than the leader who only asked the question when the signals started turning negative. 

Stabilize Before You Expand Again 

The operational principle that distinguishes healthy growth from swelling is sequencing: stabilize before you expand. Growth that outpaces the organization’s capacity to integrate it creates conditions for the next wave of growth to compound rather than resolve the coherence problems. 

This does not mean growing slowly. It means being deliberate about what needs to be consolidated, documented, and embedded in the operating model before the next expansion layer is added. It means treating the technology and security infrastructure review not as a periodic maintenance task but as a prerequisite for growth decisions — ensuring that the environment you are expanding is architecturally sound before you expand it rather than discovering that it was not after you have added more complexity to it. 

It also means being honest about the difference between the organization’s stated capacity and its actual capacity — between how many clients the model says it can serve and how many clients it is currently serving at the quality level that justifies the relationship. That gap, if it exists, is a swelling indicator. It is also, if addressed deliberately, the most straightforward path to growth that compounds on itself rather than growth that eventually requires painful unwinding. 

The Client Experience as a Leading Indicator 

One of the most reliable early signals of swelling rather than growth is a change in the quality and consistency of the experience for the clients the organization was serving before the growth accelerated. 

This is a counterintuitive place to look during a growth phase, because the attention naturally goes to the new clients being brought on and the new capabilities being developed. The existing clients are, almost by definition, not the priority in the moment — they are already there, presumably satisfied, generating the revenue that the organization is trying to scale. The assumption, often implicit, is that the delivery model that earned their trust is still running the same way it was. 

It usually is not. The people who were serving those clients are now also onboarding new clients. The processes that were well-understood when the team was smaller are now being handled by people who learned them in a more compressed way during a period of rapid hiring. The institutional knowledge that made the delivery model work — the contextual understanding of what the client actually needs, the history of how the relationship developed, the judgment calls that experience makes obvious — is distributed more thinly across a larger team. The senior people who carried that knowledge are now in more meetings, managing more relationships, and spending proportionally less time with any individual client. 

The client does not always notice immediately. The degradation is often subtle — a response time that is slightly slower, a deliverable that is technically correct but lacks the insight of previous work, a conversation that is efficient but feels more transactional than it used to. These signals tend not to generate direct feedback because most clients do not frame their dissatisfaction as “your team grew and the quality changed.” They experience it as a vague sense that the relationship is not quite what it was, and they file it away and re-evaluate at renewal. 

The organization that is growing in a healthy way is monitoring this signal intentionally — not waiting for renewal behavior to reveal it, but actively seeking feedback from its most established client relationships and taking the responses seriously as indicators of whether the growth is being integrated or whether it is coming at the expense of the foundation that made the growth possible. 

The People Signal 

The internal version of the same diagnostic is the quality of experience for the people who were in the organization before the growth accelerated, particularly those in senior or knowledge-intensive roles. 

Healthy growth tends to be experienced by this group as energizing: new colleagues bring new capabilities, the expanded scope creates genuine opportunity, and the culture holds because it is being actively maintained and transmitted. Swelling tends to be experienced as disorienting: the culture is different in ways that are hard to articulate but consistently felt, the decisions that used to be made in one conversation now require a committee, and the institutional knowledge that gave the senior people their effectiveness feels less valued in an environment that is moving too fast to stop and draw on it. 

The turnover risk in this group is particularly significant. The people who have been in the organization longest are not always the most expensive to replace in salary terms, but they are almost always the most expensive to replace in capability terms. They carry the organization’s history, its client relationships, its institutional knowledge about why things are done the way they are done and what happens when they are not. When they leave during or after a period of rapid growth, the organization frequently discovers that the processes that were running on their judgment need to be rebuilt from scratch — a discovery that is usually made in the context of a delivery failure or a client relationship problem rather than as a deliberate choice. 

Swelling that is caught early, diagnosed honestly, and addressed through deliberate consolidation tends to resolve before it reaches this point. The organization that asked the question — are the people who have been here the longest thriving in this environment, and if not, what does that tell us about the way we are growing — while the momentum was still strong has the capacity to make adjustments. The organization that waited until the signal was undeniable is usually managing the consequences under much less favorable conditions. 

What Consolidation Actually Requires 

The word consolidation is often used as if it simply means slowing down — reducing the rate of new client acquisition or new hiring until the organization catches up with itself. This captures part of it. The more complete picture is that consolidation requires active work on the things that growing organizations tend to neglect in favor of the things that generate the metrics of success. 

Documenting the processes that are currently running on individual expertise rather than institutional knowledge. Reviewing the technology and security infrastructure to ensure that it reflects the current organization rather than the organization as it was configured during a different phase. Deliberately transmitting the culture and judgment principles that made the early delivery model work to the people who joined during rapid growth and learned the processes without the context behind them. Rebuilding the feedback loops with long-standing clients that may have atrophied as attention went to new relationships. Identifying the capabilities the organization is currently reaching for but does not have embedded, and building them structurally rather than just hiring individuals who carry them. 

None of this is exciting relative to the story of growth. It is quieter, less visible on any dashboard, and harder to celebrate than a new client announcement or a hiring milestone. It is also the necessary foundation on which the next phase of growth can actually be built — rather than the next phase of growth simply becoming the next and more expensive phase of swelling, at a scale that is considerably harder to address. 

Tom Glover is Chief Revenue Officer at Responsive Technology Partners, specializing in cybersecurity and risk management. With over 35 years of experience helping organizations navigate the complex intersection of technology and risk, Tom provides practical insights for business leaders facing today’s security challenges.