There is a special kind of stress that comes with a dying project.
No one sends an email that says
“By the way, this project is dying.”
It just… fades.
Replies get slower.
Meetings keep getting moved.
People talk about the project in the past tense
“Yeah, we were working on that site…”
Meanwhile money has been spent, hearts have been invested, and everyone is a little embarrassed.
I have been there.
As the person who sold the vision.
As the one trying to deliver with a team.
And as the business owner who has to explain what went wrong.
This is how I now approach a project that is quietly dying, in a way that honors people, protects relationships and still fights for an excellent outcome where possible.
Step 1: Tell the truth about the health of the project
The first rescue move is not a tool. It is honesty.
Most slow dying projects stay in that in between place because no one is willing to say out loud
“This project is in trouble.”
So scope creep continues.
Energy drops.
People stop bringing their best because it feels pointless.
What to do:
- Call it by its name
“I feel like this project is not in a healthy place. Can we all agree to talk about that honestly for a moment” - Separate blame from facts
“This is not about pointing fingers. I want us to see clearly where we are, so we can decide the right next move.” - Give a simple health summary
“Timeline is off, scope has grown, trust is a bit bruised. I would rather face that than pretend everything is fine.”
Truth brings fresh air into the room.
You cannot rescue what you refuse to admit is dying.
Step 2: Do a quick, honest health check
Once the truth is on the table, you need clarity, not drama.
I use a simple check around four areas:
- Outcome
Do we still agree on what success looks like - Scope
Is what we are trying to deliver the same thing we signed up for - Time
Where are we versus where we said we would be - Trust
How does each side honestly feel about the relationship
You can literally rate each area from one to five with the client or internal team.
For example:
- Outcome: three
- Scope: two
- Time: two
- Trust: three
Then ask two questions
- “What dragged these numbers down”
- “Which one or two numbers matter most to lift first”
Now you have a shared picture, not a cloud of feelings.
Step 3: Re connect everyone to a single, simple outcome
A lot of projects die because they try to be everything for everyone.
The original outcome gets buried under
- “Since we are here, can we also…”
- “What if we add…”
- “My boss saw another site and liked…”
Rescuing a project almost always means returning to a clear, smaller promise.
What to do:
- Ask the client in plain words
- “If this project delivered one meaningful win for you in the next three months, what would that be”
- Listen for the real answer behind the nice answer
Sometimes it is
“We want more good leads.”
Sometimes it is
“We need this live so we can stop feeling stuck.” - Write that win down and repeat it back
“So if we can launch a site that does X and Y by this date, you would consider this phase a success. Is that right”
When both sides can see that single outcome, it becomes easier to let go of the extras that are choking the project.
Step 4: Cut scope with respect, not panic
At this point you will usually see the real problem:
You tried to fit too many miracles into one box.
Rescue means you gently but firmly cut the project down to something that can actually live.
What to do:
- Divide the wish list into three buckets
– Must have
– Nice to have
– Later - Protect the must haves with your life
They should directly serve the outcome you just agreed on. - Move nice to haves into a clearly named “next phase”
Not “never”.
Just “not now”. - Be very clear when you talk about it
“If we keep everything in this phase, we will continue to crawl. If we agree to launch with this tighter set, we can get you something real that earns its keep, then continue.”
Cutting scope is not a lack of faith.
It is stewardship.
You are saying “Let us deliver something real, then grow from there.”
Step 5: Create a short rescue plan everyone can believe in
A dying project does not need another huge plan.
It needs a short, believable one.
Think in terms of the next thirty to sixty days, not the whole year.
What to do:
- Define a short rescue sprint
“For the next four weeks our only focus is getting Version One live with this feature set.” - Agree on clear responsibilities
“Our team will do A, B, C. Your team will provide D and approve E.” - Put dates on specific, visible milestones
Designs locked
Content delivered
Staging site ready
Launch window - Decide exactly how you will communicate
Weekly check in call
One shared channel or thread
One place where decisions are recorded
Make sure everyone can look at the rescue plan and say
“Yes, this is realistic if we all do our part.”
If the plan feels impossible, you are just setting up a new disappointment.
Step 6: Decide with courage when to release a project
Sometimes, after the health check and hard conversations, you realise the kindest thing is to stop.
Maybe the business has changed.
Maybe trust is too damaged.
Maybe key people are gone.
Rescue is not about dragging a dead project around for pride.
It is about seeking the best outcome for everyone.
What to do when the answer is “we should stop”:
- Name it clearly and gently
“Based on everything we have seen, trying to push this version to the finish line will cost more than it will give back.” - Offer a clean landing
A stable handover package
Clear documentation
Suggestions for what they can do next on their side - Own your part with humility
“Here are things we could have done better. Here is what we learned.” - Leave the door open with integrity
“If you would like to revisit this later with a fresh brief and clearer constraints, we will be happy to explore it with you.”
Sometimes releasing a project is the most honest way to honor your team, your client and your values.
Final Thought
A project does not usually die in one day.
It fades in small steps.
You can often rescue it if you are willing to
- Tell the truth about where things really are
- Do a simple health check around outcome, scope, time and trust
- Reconnect everyone to one clear, realistic win
- Cut scope with respect so the project can breathe
- Create a short rescue plan that people actually believe in
- And if needed, release the project with courage and honor
That is how you protect excellence without pretending every story must end in a “perfect launch”.
