The observation
An operations manager’s remit has expanded to cover four distinct areas, each added at a different time as the business grew. The natural reading of this is straightforwardly positive: a capable person is taking on more, growing with the organisation, being trusted with wider responsibility as she proves herself. Nothing about that reading is wrong on its face. It is also not the complete picture, because it treats each addition as if it were assessed against everything the role already carried — when in most cases, it wasn’t.
What leaders usually conclude
When a competent person is available and a new area of responsibility needs a home, giving it to that person is often the path of least resistance, and frequently the genuinely correct call in the moment it is made. The person is capable; the area needs oversight; the fit looks obvious. What tends not to happen, at the point each individual addition is made, is a review of the role’s total shape — how much the person is already carrying, whether the new area is complementary to or competing with existing priorities, and what, if anything, should come off the role to make room for what is going on.
This is not usually a failure of judgment about any single decision. Each addition, assessed on its own terms, is defensible. The gap is that “on its own terms” is precisely the wrong frame for a role that has already absorbed several previous additions — because the question that actually matters is not whether this person could reasonably take on this one new thing, but whether this person, holding everything they already hold, can take on one more thing well.
What the evidence suggests
Consider an organisation where exactly this has happened. Four areas have been added to one role at different points, each because the person holding the role was the most competent available option at that specific moment. No addition was ever assessed against the whole of what the role had become. Two of the four areas now receive only minimal attention — not because the person is failing, but because there are, in practical terms, more demands on her time and judgment than any one person can give proper weight to simultaneously.
The mechanism at work here is accumulation without review: responsibility builds through a series of local decisions, each rational in isolation, none of which considers the aggregate. Competence, in this pattern, becomes a magnet for additional load — the very quality that makes someone a sensible choice for one more responsibility is the same quality that makes them likely to already be carrying several others, and being reliably capable offers no natural limit on how much can be added, because reliability is exactly what makes each individual addition look safe.
This connects to a genuine distinction worth drawing explicitly: headcount growth is not the same thing as organisational growth. A business can add people steadily while quietly asking its most capable existing people to absorb disproportionately more responsibility than any new hire receives, because new hires arrive into defined roles while existing high performers absorb whatever doesn’t yet have a defined home. The organisation looks like it is growing its management capacity, because headcount is rising. What is actually happening, in cases like this one, is that management capacity is concentrating rather than growing — more of the organisation’s coordination and judgment is running through fewer people, even as the total number of people increases.
Jay Galbraith’s research on organisational design offers a useful frame for why this matters beyond the immediate strain on one person. Galbraith’s information-processing view of organisations holds that as task complexity and interdependency rise, the organisation needs either more capacity to process information and make decisions, or mechanisms to reduce how much needs to be processed in the first place — self-contained units, clearer boundaries, better lateral coordination between roles. A role accumulating responsibility without review does neither. It does not add processing capacity — the person’s capacity is fixed, whatever their competence — and it does not reduce the complexity being asked of them; it simply concentrates more of the organisation’s total complexity onto one point, which is a fragile way for an organisation to be structured even when that point is currently performing well.
There is a contextual dimension that shapes how severe this becomes. In organisations that grow quickly, the mismatch between how fast responsibility accumulates and how fast anyone has time to review it tends to widen faster, simply because there is less slack in the calendar for the kind of unhurried “what does this role actually look like now” conversation the pattern requires. In organisations with a smaller, closer-knit leadership team, additions are more likely to be visible to more people at once, which offers some natural protection — though even there, if the same one or two people are consistently the most capable available option, the accumulation can still concentrate onto them specifically, protected paradoxically by the same visibility that might otherwise catch it, because everyone can see how reliable they are and nobody wants to be the one adding friction to a system that currently appears to be working.
There is also a genuine trade-off worth acknowledging rather than resolving too neatly. Deliberately capping what any one capable person is allowed to take on, in the name of avoiding overload, has its own cost: work that genuinely needs a competent home may sit with someone less equipped for it, at least temporarily, while the organisation builds additional capacity. The evidence here does not argue for never assigning new responsibility to a proven performer. It argues for making that assignment a reviewed choice against the whole of what the role already carries, rather than a series of individually reasonable decisions that nobody ever adds up.
The same pattern appears across many kinds of organisation; see Other Sectors for how it is read elsewhere.
Questions worth considering
- Which roles in this organisation have grown through a sequence of individual additions, each reasonable at the time, without ever being reviewed as a whole?
- If the areas currently attached to an overloaded role were being assigned fresh today, with full visibility of everything else that role already carries, would the same allocation be chosen?
- Is headcount growth in this organisation matched by a corresponding growth in defined management capacity, or is it concentrating responsibility onto fewer, already-stretched people?
This perspective is part of Growth.
Your team is facing similar challenges?

Subscribe to The Riddle Ledger
Perspectives are sent as they are published, with no promotional email, and you can unsubscribe at any time.
