Improvement Project Pitfalls

How to avoid losing months

Improvement projects rarely lose momentum because of one big mistake. More often it’s a series of small, reasonable decisions, like moving on a loosely defined problem or settling on a solution too early, that make the work harder than it needs to be. These decisions sit inside normal ways of working, so they rarely look like mistakes at the time.

Below are the seven we see most often, with how to catch each one early if you’re just starting a project, or how to course-correct if you’re already underway.

Download PDF Version

1. Starting without a clear problem

Many projects start with activity rather than clarity: there’s energy, a clear direction, and a strong sense of what needs to change. What’s often missing is a well-defined problem, which makes it difficult to judge, weeks in, whether any of that effort is actually working.

When setting up a new project:

• Check the fundamentals: is the problem meaningful, manageable and measurable?
• Ask leaders what’s genuinely causing concern or friction, not just what’s visible on the surface
• Look at strategic objectives and identify where improvement would materially support them
• Use your KPIs to highlight where performance is genuinely falling short

If the project is already underway:

• Take a step back and verify whether you’re solving a clearly defined problem, or working towards a solution that was decided too early.

2. Jumping into solutions too early

There’s always pressure to move quickly, and in many environments, action is read as progress. But the earlier a solution is locked in, the higher the risk it misses the real issue. This is one of the most common reasons projects stall or cycle back on themselves. An initial solution feels right at the time, then doesn’t hold up once the team understands the problem more deeply.

When setting up a new project:

• Follow a structured improvement cycle (define, measure, analyse) rather than jumping straight to ideas
• Get comfortable with holding a problem without immediately solving it
• Accept that PDSA starts with Study. Prioritise understanding what’s really happening before deciding what to change

If the project is already underway:

• Use governance and review points to challenge assumptions and slow things down where needed
• Capture early ideas, but treat them as hypotheses rather than answers
• Expect your thinking to evolve as your understanding improves

3. Choosing processes that move too slowly

Improvement relies on learning, and learning relies on feedback. When the process you’re studying only runs occasionally, a quarterly planning cycle or an annual review, that feedback loop becomes slow and unreliable. This can make even well-run projects feel stuck, simply because there isn’t enough evidence yet to build confidence in the decisions being made.

When setting up a new project:

• Prioritise processes that happen frequently, where changes can be tested and observed quickly
• Use faster cycles to build momentum and learning early

If the project is already underway:

• Look for ways to simulate or replicate the process to increase learning speed
• Use indirect or proxy measures where direct feedback is too slow

4. Weak or narrow business cases

When a business case focuses only on financial outcomes, it often misses a large part of the value improvement work can deliver. That narrowness can make it harder to justify decisions, maintain support, or adapt when new insights emerge. Strong business cases create alignment and narrow ones create friction.

When setting up a new project:

• Look beyond cost savings: consider customer experience, safety, quality and team impact
• Work with finance early to agree how benefits will be measured and validated
• Use charters and contracts to establish shared understanding from the outset

If the project is already underway:

• Strengthen how benefits are being tracked and reviewed
• Be prepared to revisit and refine the business case as the work uncovers new information

5. Letting scope drift

Scope rarely changes all at once. It expands gradually, usually for good reasons: a new idea surfaces, an adjacent issue gets uncovered, and the project tries to accommodate more than it can realistically deliver. The result is diluted focus and slower progress, even though every individual addition felt justified at the time.

When setting up a new project:

• Define and agree scope clearly from the start, including what is intentionally out of scope
• Use tools like process mapping or SIPOC to ground the discussion in reality
• Analyse the current state before deciding how broad the project should be

If the project is already underway:

• Revisit scope regularly as new learning emerges
• Be willing to narrow focus if it improves delivery

6. Lacking the right buy-in

Improvement work depends on people more than process: without the right involvement, even well-designed changes struggle to take hold. A lack of buy-in rarely shows up immediately. It surfaces later, as resistance, slow decision-making, or difficulty implementing changes that looked straightforward on paper.

When setting up a new project:

• Identify process owners and key stakeholders early
• Don’t believe you have no permission to improve a process if you’ve got no data to back that up
• Make sure there is genuine alignment on the purpose and direction of the work, not just sign-off

If the project is already underway:

• Revisit your stakeholder analysis and check whether anything has changed
• Confirm that the right people were involved in the original decisions
• Re-engage stakeholders where alignment has drifted

7. Underestimating time commitment

Improvement work is usually planned alongside people’s existing responsibilities. Without clear commitment and protected time, it quickly becomes something worked on inconsistently, squeezed in around the day job. This is one of the most common reasons projects lose momentum rather than fail outright.

When setting up a new project:

• Establish a clear and realistic rhythm for the work
• Agree time commitments explicitly and document them
• Assign named individuals rather than relying on roles or departments
• Be honest about what will be deprioritised to make space for the work

If the project is already underway:

• Reinforce the commitments that were originally agreed
• Use sponsors to provide support where time constraints are limiting progress

Avoiding pitfalls through awareness

The intent behind most improvement projects is usually sound. What slows things down sits in how the work is set up and managed: early decisions around problem definition, scope, alignment and pace. These choices shape how the work unfolds, often only becoming visible once progress starts to stall. Recognising these pitfalls requires an understanding of how they influence the direction and speed of the work, so teams can respond earlier and with more confidence.  When these patterns are surfaced and addressed, projects tend to regain clarity, unnecessary effort drops away, and progress becomes more consistent.

Approaching improvement work with this level of awareness creates space for better decisions and more focused effort. Where progress has already slowed, revisiting these seven areas can provide a practical route back to momentum, without needing to restart or redesign the project from scratch.

 

 

You know the tools. You have the skills.
Now see what changes when you make AI part of your improvement approach, especially in the messy reality of real projects.

Explore AI For Performance Improvement Courses

Recommended for you

Related

MEETS US AT THE GEMBA!

GEMBAfication is PMI’s new podcast for improvement professionals looking for an honest view of what improvement really looks like in practice. Because in our world, every experience is valuable.

Listen Now