As the discussion goes on, the same explanations come up again. Unexpected bottlenecks appear. A key person gets pulled into another urgent task. Priorities keep shifting.
Each time, the bottleneck shows up somewhere else - making it look like the problem is a lack of resources.
The conclusion feels almost inevitable: you don't have enough resources. That's the last thing you want to hear. You already know how hard your teams are working - and it's not clear that adding more resources will fix this, while it would almost certainly increase your budget.
So what is actually going on here?
The problem is not a lack of resources, and it is not a lack of hard work.
When too many projects run at the same time, critical resources become overloaded. The overload keeps shifting from one area to another, making it look like capacity is missing in multiple places. But the real problem is simpler: too many projects are running through the same resources at the same time.
If this pattern looks familiar in your organization, it’s worth a conversation.
MxN - The Real Cause Behind Delays
Most organizations are not running one project; they are running many projects through the same shared resources.
Take a typical setup: 30 projects running in parallel across multiple teams totaling around 80 people. Everyone is already stretched. The same critical resources are pulled into multiple projects, and priorities keep shifting. When one project slips, it doesn't stay contained. It pulls attention from other work, delays decisions, and creates a domino effect across the entire portfolio.
This is why complexity explodes: critical resources are pulled between projects, and management shifts into constant firefighting. Adding more people into a system that isn't flowing doesn't solve the problem - it puts more pressure on the existing bottlenecks and increases cost.
When organizations reduce parallel work, timelines do not just stabilize - they get shorter. It sounds counterintuitive: you would expect projects waiting to start to be delayed. The opposite happens. When active projects stop competing for the same resources, they finish faster. Capacity frees up earlier, and the next projects start sooner. Over time, more projects get completed - not fewer.
Reducing the number of active projects is necessary, but not enough. Interruptions, urgent work, and constant context switching keep pulling people away from planned work, breaking execution even when load is reduced. Without a mechanism to absorb this work without disrupting active projects, teams remain in constant firefighting.
Our Approach (CBS): Change the System, Not the People
This is what we call the CBS Flow Acceleration Method. Instead of trying to "optimize everything" at once, we reduce simultaneous workload and create flow:
- Fewer parallel projects (at least 30%) - Concentrating effort speeds completion and reduces conflicts.
- Building clear "flow lanes" (pipeline lanes) - defining what type of work belongs in each lane.
- Controlling project entry ("traffic lights") - like roads: you don't add cars to a traffic jam; you regulate flow.
- Ensuring readiness before entering the system - reducing waste and rework.
- Identifying and protecting the constraint - aligning priorities around the true pace-setter.
- Short management cadence - focusing on flow status: how much remains, how close we are to the goal (like Waze, looking at time remaining), enabling real decisions.
What We Deliver
We run a focused analysis that shows you:
- 1. Your primary constraint - what actually limits your delivery
- 2. The root causes that prevent it from operating efficiently
- 3. The overload on your critical resources (MxN) and its impact on your organization
- 4. Your realistic improvement potential (in %)
- 5. What needs to change to realize that potential
After the analysis, you can decide whether to move forward with us into the improvement phase.
If you want to understand what this could look like in your organization, let’s set up a conversation.
Real Example: What Happens When You Reduce Parallel Work
An Israeli mid-sized industrial engineering company (around 150 employees) asked us to help. They were running about 35 projects and multiple product versions in parallel through a shared team. Priorities kept shifting, delays accumulated across projects, customer satisfaction dropped, and average delivery slipped by about 4 months per project.
Their VP of Engineering described the turning point clearly: "We thought we needed more people. In reality, we needed to limit parallel work and manage the load on our key resources."
We cut active parallel work by 1/3 and rebuilt entry rules so only fully ready projects entered execution. Within 16 weeks, average cycle time dropped by 35%, due date performance climbed above 90%, and high-level management escalations dropped by 75%.
Most importantly, leadership could trust delivery commitments again and started committing to dates with confidence. By finishing fewer projects at once, the organization shipped more strategic outcomes per quarter.
"After the shift, we finally had control over delivery. For the first time, our management team could focus on sales instead of execution."
Common Mistakes That Keep Projects Stuck
Most organizations recognize the problem and try to fix it on their own. The trouble is that the fixes usually target symptoms, not the system. Worse, the way delivery is typically managed - by utilization, by task completion, by adding resources - reinforces exactly what's causing the delays. These are the patterns we see repeatedly:
- Starting new projects before existing ones are truly ready to move.
- Overloading shared experts and assuming multitasking will speed delivery.
- Managing by utilization instead of flow, which hides bottlenecks.
- Avoiding clear prioritization - treating all projects as highest priority out of fear that lower-priority work will be delayed or not completed.
- Tracking tasks instead of focusing on what actually determines project speed.
Why This Approach Works
Flow-based management follows a simple principle: prepare work properly, concentrate critical resources and management attention, and execute projects as quickly as possible. When the system is aligned and focused, issues get resolved faster, bottlenecks are easier to spot, and work moves.
You are not delaying committed projects. You are staggering when they start. By starting projects later - when the system has the capacity to execute them - each project finishes faster than it would have under constant overload. The portfolio as a whole delivers more, not less.
Because projects start only when the system is ready to execute them, commitments become reliable. Leadership regains a clear view of progress, and dates can be trusted again.