Being busy is not the same as making progress

Your team is working at full capacity. The order book is looking healthy. And yet the key projects aren’t getting done - or at least not as they should. This isn’t a sign of a lack of commitment. It’s a systemic flaw. If you understand why work gets stuck, you can make the right changes - without needing more resources.

Being busy is not the same as making progress

The most persistent misconception in project-heavy organisations: if everyone is busy, the projects are running smoothly. That’s not true. Workload and completion are two different things. A machine can be running and still produce nothing of any use.

“Everyone is busy, but the important things aren’t getting done.”

This pattern arises when too many projects are running simultaneously. Everyone is working on something, but no one is finishing anything. Work in progress - that is, the amount of work that has been started but not yet completed - is the decisive lever. The more of it there is in the system at any one time, the longer each individual project takes. This is not an opinion; it is mathematics.

Little’s Law from queuing theory describes it precisely: the lead time of a project increases in proportion to the amount of work in progress. So anyone who starts more projects without completing old ones slows down all projects - without realising it. The result is an organisation that is constantly running but still rarely gets there.

The first step is therefore not a new tool or a new method. The first step is to understand how much work is currently in the system at the same time - and why that is the case.

Where work really gets stuck

When projects aren’t completed, most people look first to the staff: Who hasn’t done what? Who was too slow? That’s the wrong question. The right question is: Where in the process does work get stuck - and why?

In most organisations, there are a few structural patterns that are responsible for this. The Standish Group CHAOS Report regularly shows that only a fraction of all projects are completed on schedule. According to Standish, fewer than a third of all projects are completed on time, within budget and with the full scope of work. The reason rarely lies with individual people - but in the system surrounding them.

Typical points where work stops making progress:

• Decisions that nobody can or wants to make - because responsibility is unclear
• Interdependencies between teams that are not coordinated
• Feedback and approvals that take days or weeks
• Tasks that are reworked multiple times because the requirements weren’t clear the first time
• Work being carried out in parallel on too many projects at once

None of these points is a failure on the part of individuals. Taken together, they are a sign that the system is not designed to get things done reliably.

Multitasking costs more than it delivers

Most organisations glorify multitasking. Anyone who keeps many balls in the air at once is considered efficient. Research shows the opposite. Switching context between projects costs up to 40 per cent of productive working time - Gerald Weinberg has already proven this empirically, and recent research by Microsoft Research confirms the cognitive costs of frequent interruptions and task switching.

The problem is not that employees lack the necessary skills. The problem is that they juggle too many tasks at once. Every switch between projects costs time to get up to speed, leads to errors and lowers quality. Anyone working on five projects simultaneously will not make good progress on any of them.

For managers, this has a direct implication: the question is not how to get more work into the system. The question is how to reduce the amount of work running concurrently - without delivering less. That sounds paradoxical. It isn’t. Fewer parallel projects means faster completion of individual initiatives, faster value delivery and less waste due to context switching.

Why new projects still always take priority

If starting new projects is the problem - why does it keep happening anyway? Because the incentives are wrong. Starting a new project feels like progress. There’s a kick-off, a presentation, energy. Completing an ongoing project is usually more of a slog - there are loose ends, dependencies, a need for coordination.

On top of that: whoever starts a new project gets attention. Whoever finishes an old one is just doing their job. This dynamic is humanly understandable but organisationally disastrous. It leads to organisations starting more and more and completing less and less.

The PMI Pulse of the Profession 2024 shows that resource conflicts and unclear priorities are among the most common reasons for project delays - and both stem directly from the habit of starting too many things at once. As long as new projects are launched faster than old ones are completed, the backlog grows - and every single project takes longer.

The visibility problem: you can’t manage what you can’t see

Another key reason why projects aren’t completed: leadership can’t see where the work is. Status meetings usually report on what’s planned - not what’s actually holding things up. Status indicators show green until everything turns red just before the deadline. This isn’t intentional; it’s a structural problem.

Anyone who wants to manage projects needs visibility into the actual flow of work: where are tasks currently at? How long have they been there? What is blocking further progress? This information is available in most organisations - but it is not aggregated and not visible.

“The problem isn’t a lack of commitment. The problem is a lack of visibility into what is holding the work up.”

McKinsey has demonstrated in several studies that organisations which systematically identify and prioritise bottlenecks achieve significantly better project outcomes than those which focus on individual performance. The lever does not lie with the individual - it lies in the system. Visibility is the prerequisite for being able to intervene at all before a project goes off the rails.

What really helps - and what doesn’t

The usual reaction to too few completed projects: more process, more controlling, more reporting. More meetings to clarify the status. More project management tools. More methodology. That doesn’t solve the problem - it adds further work to the system that also needs to be done.

What actually helps is doing less, but in a more targeted way:

• Actively limiting the number of projects running simultaneously
• Make bottlenecks visible - not through more reporting, but through targeted observation of the actual workflow
• Shorten decision-making processes so that work does not pile up due to a lack of approvals
• Shift the focus from workload to completion - what matters is not how much is started, but what is finished

The Atlassian State of Teams Report shows that teams with clearly defined priorities and a reduced volume of parallel work are significantly more productive - not because they work harder, but because they are less frequently held back by context switching and dependency issues.

None of these measures requires a new tool. None requires a new methodology. All require someone with responsibility and assertiveness to start observing the system - and then make a targeted change in one specific area.

The first concrete step

If you’re currently in a situation where your team is working to capacity but isn’t getting the important things done - then the most likely cause isn’t a lack of effort. It lies in the system: too much on the go at once, too little visibility, too many bottlenecks that nobody is specifically addressing.

Scaled Innovation shows you, in 10 working days, where work gets stuck in your organisation and which change will deliver more finished results first. No new method. No new tool. Just a clear view of what is actually happening - and what makes sense to do next.

If you want to know where your projects are really being held up, get started at scaled-innovation.com.