Thirty active projects, eleven strategic initiatives, four transformation programs, and an innovation lab. All running simultaneously, all prioritized. The executive board insists that every single initiative is important. The division heads nod. The teams drown.
This is not an exception. It is the default state in organizations that react to every impulse without ever answering the question of what they actually want to achieve — and what they don’t. Structural overload does not arise from too little capacity. It arises from the refusal to set priorities that also mean letting things go.
The Arithmetic of Overload
The math is simple; the consequences are ignored regardless. If an organization with a hundred employees runs thirty projects in parallel, that leaves an average of three people per project — minus day-to-day operations, meetings, sick leave, vacation. In reality, most employees work on five to eight projects simultaneously. None of them gets the attention it needs.
The result: Everything takes longer. Quality drops. Deadlines get pushed. The organization produces activity, but no impact.
The Context-Switching Price
The consequence becomes visible when projects stall and teams appear stressed even though everyone is busy. Being busy and being effective are two fundamentally different states — but most management systems cannot tell the difference. They measure utilization, not impact.
Why Prioritization Fails
The diagnosis is almost always followed by the same suggestion: prioritize better. Prioritization workshops, scoring models, portfolio evaluations. And yet, little of substance changes. Why?
Because prioritization in organizations is not an analytical problem — it is a political one. Every initiative has a sponsor. Every project has a team working on it. Every strategic direction has advocates. Deprioritizing something means telling someone: Your topic is less important. Your budget is being cut. Your visibility is declining.
| Why initiatives get started | Why initiatives don't get stopped |
|---|---|
| New market opportunity identified | Sunk-cost logic: Already invested too much |
| External pressure from competitors | Political cost: Sponsor loses face |
| Board decision or consulting recommendation | Lack of transparency: Nobody has the full picture |
| Enthusiasm after an offsite or conference | Diffusion of responsibility: Nobody feels responsible for stopping |
| Funding or partner opportunity | Hope: Maybe it will work out after all |
Starting an initiative is a positive, energizing act in most organizations. Stopping an initiative is a negative, conflict-laden act. Accordingly, much gets started and little gets stopped — until the total load paralyzes the organization.
The Missing Shutdown Mechanism
Most organizations have elaborate processes for starting projects. Hardly any have a structured process for stopping them.
This is the structural root of overload. Without an explicit mechanism that regularly checks which initiatives still deliver the expected value, the portfolio grows unchecked. Every new quarter adds something. Rarely does anything fall away. After two to three years, the organization is so overloaded that even the most important initiatives can no longer make progress.
The Missing WHY
Behind structural overload lies a deeper problem: the absence of a clear WHY. Not in the sense of a corporate purpose on the website, but in the sense of an operationally effective answer to the question: What problem are we actually solving? What is the central lever the organization needs to work on right now?
Without this clarity, every opportunity becomes an initiative. Every market trend generates a project. Every consulting recommendation leads to a program. The organization reacts to everything — and shapes nothing.
That is uncomfortable, because it means saying no. No to initiatives that are reasonable in isolation but collectively exceed capacity. No to projects that are interesting but don’t serve the one central question. No to leaders who want to advance their pet topic.
Clarity as a Leadership Task
The ability to establish clarity is not a side activity for the executive team. It is their core task. And it requires three things:
First: Explicit problem definition. Not “digital transformation” or “growth” — but a precise description of the problem the organization needs to solve right now. Why now? What happens if nothing happens? What is the hypothesis for how the problem can be solved?
Second: Rigorous prioritization. Not three strategic priorities, not five, not ten. One. Two at most. Everything else is a wish list, not a priority. The test is simple: If everything is a priority, nothing is a priority.
Third: Active portfolio management. A regular, institutionalized process that reviews the entire initiative portfolio. Not for progress — for relevance. Which initiatives still contribute to the central problem? Which could be paused or stopped? What resources would that free up?
The Way Out: Do Less, Achieve More
Organizations that take the problem of structural overload seriously make a simple but radical decision: do less at once. This does not mean being less ambitious. It means concentrating ambition on fewer topics — and then executing them with the necessary intensity and speed.
The first step is not a new prioritization framework. The first step is an honest inventory: How many initiatives are actually running in parallel? How many of them would we start again today, with what we know now? And how many things that truly matter are not making progress because the capacity is tied up?
The answers to these questions are almost always uncomfortable. But discomfort is the price of clarity. And clarity is the prerequisite for organizations to stop confusing activity with impact.