How it worksSupportPricingFAQ
Resources
BlogBest Practices
About
Talk to usLogin
← Back to the blog

How do you keep projects from fizzling out after a few months?

November 18, 2026 · 5 min read

Anyone who has introduced new tracking knows it: while it's new, you're happy to do it, then it becomes a chore. That is how projects fizzle out after a few months, because reporting never became a habit. You prevent it with an owner who knows what they're signing up for, fixed reviews and consequences when no report comes.

Why do projects fizzle out after a few months?

At the start of a project there is usually euphoria: it has been approved, the kick-off is done, and everyone wants it to work. What is often missing afterwards is proper change management. So reporting never becomes a habit, and once the novelty has worn off, tracking becomes a chore. You have to force yourself to keep doing it, and at some point it peters out.

Are a clear owner and regular reviews enough?

The standard answer to projects that fizzle out is: a clear owner, regular reviews and consequences when nobody reports, in other words an escalation. That answer is correct. If you have to force yourself to keep up the reporting, you need someone who asks, and a fixed date on which it shows that nothing came in. It matters that the owner knows from the outset what they're signing up for.

Where it gets difficult, though, is putting it into practice: most projects that fizzle out have neither reviews nor an owner, or the project owner is not accountable to anyone. The business case has then served its purpose with the approval and ends up in a drawer.

At Bayescase, program management software (for innovation, transformation or cost programs, for example), we turn the business case into targets after approval: actual figures update the forecast, and deviations show up early.

Why are projects neither continued nor stopped?

On top of that comes something you should always keep in mind in large companies: without a process, little happens, and without an incentive for the people involved, little happens either. An owner and fixed reviews are exactly that kind of process, and whether anyone enforces them depends on interest.

A lack of interest cuts both ways. If nobody has an interest in a project, it falls asleep. If nobody has an interest in it being officially stopped either, it keeps running as a zombie.

If nobody has an interest in a project, it falls asleep. If nobody has an interest in it being officially stopped either, it keeps running as a zombie.

So the trick is to have someone with an interest in a project being pursued, who can then also push colleagues, or in it being stopped. Ideally that is the same person, someone who looks at all projects at once: a program or portfolio manager.

For that person to really want both, they need an incentive themselves. A program manager should be measured and incentivized on the success of their program, that is, on the efficiency and effectiveness of their investments and projects. Then it is in their own interest to stop bad projects early (how to make that traceable is covered in the post on prioritizing a project portfolio) and to make sure good projects deliver what they should.

What you can do differently from Monday

Go through the projects in your program that haven't reported anything for a few months and ask for each one: Who is the owner? When is the next review? What happens if the report doesn't come? Wherever an answer is missing, set it, and tell the owner clearly what they're signing up for. Then clarify who in your program is measured on the result of the whole portfolio. If that person doesn't exist, you are missing exactly the one person with an interest in projects either continuing or being stopped.

Frequently asked questions

How do I keep projects from fizzling out after a few months?
With a clear owner who knows from the start what they're signing up for, regular reviews and consequences when nobody reports. On top of that you need someone, such as a program or portfolio manager, who is measured on the success of the whole program and therefore insists on it.
Why do innovation projects fizzle out after the kick-off?
At the start, euphoria carries them, but without proper change management reporting never becomes a habit. Once the novelty has worn off, tracking becomes a chore and peters out. Most projects that fizzle out then lack reviews and an owner who has to be accountable.
What is a zombie project?
A project that nobody has an interest in continuing, but nobody has an interest in officially stopping either. So it keeps running, even though nobody is pushing it. What helps is a person with an interest in projects either delivering or being stopped early.
Who should follow up on projects in a program?
Ideally a program or portfolio manager who is measured and incentivized on the success of their program, that is, on the efficiency and effectiveness of their projects. They then have their own interest in pushing good projects and stopping bad ones early.
Lukas Mayer

Written by

Lukas Mayer

Co-Founder & COO, Bayescase

What will your strategy deliver?

In a short conversation we take one of your initiatives and show how an idea becomes a business case with targets and tracking.

Talk to usarrow_forward