More People, More Complexity

There is a particular moment that’s recognizable once you've seen it enough times.  A problem stops being a problem and becomes a project.

It usually starts with good intentions because something isn't moving the way it should. The person at the top notices, decides it needs more attention, and begins adding people. A specialist here, a coordinator there, someone from an adjacent team who might have relevant context. The logic is sound on its face – this problem matters, so let's resource it properly.

What happens next is predictable, though it rarely feels that way in the moment.

The scope expands to accommodate the new participants. A problem that had a defined boundary now must account for additional perspectives, additional workstreams, and additional questions that weren't part of the original situation. Meetings are scheduled to bring everyone up to speed.  Those meetings generate follow-up items. The follow-up items require coordination. Somewhere in the expanding circle, the original problem is still waiting but is now surrounded by everything that was added to solve it.

I've watched this happen more times than I can count. The moment the calendar invite goes out with names that weren't there before, something shifts. The people already close to the problem who understood its boundaries and who had a reasonable path to resolution are now navigating a larger room, with more complications. In many cases, the person who assembled that larger room has moved on to the next thing, confident that resources have been deployed.

The coordination burden never distributes evenly. It lands on the people who are most connected to the original problem, the most responsive, and the most capable of holding the threads together.  In some cases, it lands the person least connected to the problem, but who has the greatest bandwidth, which adds additional layers of difficulty.  No one volunteered for the expanded coordination, but this level of expanded structure must have something to keep it from collapsing.

This is what well-intentioned escalation produces. Not more capacity, but more complexity. The problem doesn't get smaller because more people are looking at it. It is harder to resolve because closing it now requires alignment across a group that didn't exist a week ago.

There's a version of this that's entirely appropriate. Some problems genuinely need more people. Gaps in expertise, capacity constraints, decisions that cross functional lines - these are real considerations, and adding the right people at the right moment is good structural thinking. That's not what this is about.

This is about the other version. The one where the problem was manageable, the path was visible, and the addition of people wasn't a response to a genuine gap. It was a response to the discomfort of a problem that hadn't been resolved on its own timeline, and the need to act on the instinct to do something, to show engagement, to apply resources as a proxy for resolution.

The people closest to the problem usually know the difference. They felt the original scope and saw the path, yet they watched it get complicated in a meeting they didn't call for reasons that had more to do with the appearance of action than the mechanics of resolution.

The original problem is still there.  It just got harder to reach.