July 8, 2026
Hi Everyone,
Ending a project well takes more than making the decision. The team, customers, and other departments need to know what happens next, who owns the work, and when each part of the closeout will happen.
Today, we’ll walk through how to wind down a project with the same discipline you’d give a launch.
Where wind-downs go wrong
Three things usually make a project wind-down harder than it needs to be:
The first is delay. BYU researchers found a pattern they called “creeping death”: the project kept losing budget, people, and support, but nobody clearly said it was over.
The second is unclear ownership. A wind-down often sits between product, engineering, finance, legal, support, customer success, and HR. When nobody owns the whole thing, every team handles its own piece.
The third is treating it as a technical project. The technical work matters, but so do the people and customer questions. Who tells customers? Who briefs managers? Who handles support tickets? Who explains where the team goes next?
If those answers aren’t clear, people fill the gaps themselves.
Set the dates before you announce anything
Start with the final shutdown date and work backward.
You need five dates:
- Announcement date
- Last day for new users or new work
- Last feature update or delivery date
- Data export or transition deadline
- Final shutdown date
Then name one person who owns the full wind-down.
That person should also name the leads for technical shutdown, customer communication, internal updates, support, and people questions.
Without this, the wind-down becomes a set of disconnected tasks instead of one managed closeout.
How to communicate it
Start with one clear reason for the decision.
That reason should not change by audience. What changes is the detail each group needs to act on it.
The project team needs to know whether their work still counts, what happens to the people who built it, and where their time goes next. Customers need dates, instructions, and a person to contact if the change creates a problem. Other departments need the practical impact on their own work. Sales may need a new answer for prospects. Support may need a script. Finance may need to know when costs stop. Customer success may need a migration plan.
Brief managers before the wider announcement so they are not processing the decision at the same time as their teams. Give them the reason, the dates, the likely questions, and the parts they can’t answer yet.
Then tell the project team directly. They shouldn’t learn about the ending through a company-wide note.
What to do after the shutdown day
The final shutdown date shouldn’t be the last time anyone talks about the project.
Run a short retrospective within a few days while the work is still fresh. The point is to understand what the company learned, what should change next time, and which parts of the work are worth carrying forward.
This also gives the team a cleaner ending. People need to know the company saw the work they put in, even if the project didn’t continue. Name the customer learning, technical work, process changes, and relationships that still have value.
The last piece is capacity. If people or budget are moving to another priority, say where they’re going. A wind-down lands better when the team can see what the company is choosing to fund next.
Go deeper
👉 Mind the Product: Leadership Lessons from Decommissioning a Product — The Mastercard case study in full, with advice on managing the emotional side of shutdowns
👉 Product School: Sunset a Product Without Losing Customers — The "launch in reverse" framework with a practical guide to customer communication, transition dates, and support.
👉 Perceptyx: The Layoff Aftermath — Data on how rumors and restructuring affect engagement and trust
👉 Asana: Project Post-Mortem Tips — A simple structure for running the closeout retrospective
Coming up tomorrow
In tomorrow’s issue, we’ll cover a five-week sprint to build five usable customer references for late-stage deals.
Thanks for reading!
P.S. If one of your projects is already winding down, use today’s issue to put dates and an owner around it.