What do you say when a project is completed?

What it took, who carried the difficult parts, and what shipped. A completion message that only celebrates the outcome skips the bit the team actually experienced, and they will notice the omission before they notice the praise.

Should you name individuals in a team message?

Yes. “Thank you everyone” spreads credit so evenly that it lands on nobody, and the people who took the worst weeks can tell. Name two or three and say what each of them did.

How do you recognise a project that went badly?

Say what happened and thank people for how they handled it. Teams trust a manager who describes a difficult project accurately far more than one who describes every launch as a triumph, and the second kind devalues the praise for the ones that were.

Is it worth recognising a cancelled project?

Often, yes. A prototype that answered its question and got stopped did its job. Leaving that work unacknowledged teaches people that only shipped things count, which makes them reluctant to stop bad projects early.

When is the right time to send it?

Within a few days of the launch. The energy for it drains fast, and a thank-you that arrives a month later competes with whatever the team is now behind on.

Recognition messages

Project Completion Messages: 12 Ways to Mark a Launch

The moment a project ends is the moment everyone forgets what it took. A message sent that week is worth three sent later.

The week after is the only window

A launch has a short half-life. For a few days everyone still remembers the fortnight that went wrong and who fixed it. A week later the next project has started and the detail has gone.

Which is why late recognition for a project reads as an afterthought even when it is sincere. The facts have faded for the sender, so the message comes out general, and the reader can tell.

Describe the project people were actually on

The quickest way to make a launch note ring false is to call the project smooth. Everyone who was there remembers the scope change and the awful fortnight in the middle.

Naming the hard part costs nothing and buys the rest of the message its credibility.

12 messages you can send

Shipped. Eleven weeks, two scope changes, one genuinely awful fortnight in the middle. Thank you all, and particularly Ines and Tom, who took the fortnight.
Manager, to the team
Names the hard part and the people who absorbed it.
Migration done. Zero customer-visible downtime, which was never the plan and is entirely down to Ravi’s rollback script.
Peer, to the team
Credits one specific thing for the outcome.
Congratulations on the launch. The version we shipped is noticeably better than the one we designed, and that’s because people kept arguing after the spec was signed off.
Manager, to the team
Praises a behaviour most organisations discourage.
Thank you for holding the deadline when I wanted to move it. You were right and the quarter is better for it.
Manager, to an individual
The sender concedes something, which makes it real.
That’s the redesign live. Sofia rewrote the whole onboarding flow twice because the first version tested badly and she said so herself.
Peer, to an individual
Recognises someone reporting their own failure.
Project’s finished and I want to name the unglamorous part: Marek spent three weeks on data migration that nobody will ever see working.
Manager, invisible work
Points directly at the work that has no launch moment.
We shipped late and it was the right call. Thank you for the extra fortnight and for not shipping the version we would have had to apologise for.
Manager, late launch
Reframes a slip as a decision, honestly.
Launch went out this morning. Support has had four tickets all day, which after the last one is a small miracle. Thank you, QA.
Peer, cross-team
Uses a number, and a comparison the reader will feel.
That project is done. It was not fun, several of us were short with each other, and we got there. Thank you for staying reasonable when I wasn’t.
Manager, honest
Admits the friction instead of writing it out of the story.
Congratulations on shipping. Special mention to Elena for the week of chasing three other teams for answers nobody wanted to give.
Peer, coordination work
Names work that consists entirely of persistence.
First release is out. It’s smaller than we wanted and it works, which is the correct trade and was Nour’s argument from the start.
Manager, scope
Credits a judgement call by name.
We didn’t finish this one and I want to say thank you anyway. The prototype answered the question, which is what it was for.
Manager, cancelled project
Recognition for work that produced no launch at all.

What makes one land

Send it the same week. Recognition for a project loses most of its value once the next one has started.
Name individuals inside the team message. “Thank you all” on its own reads as a formality, and the people who carried the worst parts know exactly who they were.
Include the hard part. A launch note that describes the project as smooth tells everyone who was there that you were not paying attention.
Recognise the work with no launch moment: migrations, cleanup, the tests that meant nothing broke.
A cancelled project can still deserve thanks. Work that answered a question and stopped is a success with no announcement.

Questions people ask

What do you say when a project is completed?: What it took, who carried the difficult parts, and what shipped. A completion message that only celebrates the outcome skips the bit the team actually experienced, and they will notice the omission before they notice the praise.
Should you name individuals in a team message?: Yes. “Thank you everyone” spreads credit so evenly that it lands on nobody, and the people who took the worst weeks can tell. Name two or three and say what each of them did.
How do you recognise a project that went badly?: Say what happened and thank people for how they handled it. Teams trust a manager who describes a difficult project accurately far more than one who describes every launch as a triumph, and the second kind devalues the praise for the ones that were.
Is it worth recognising a cancelled project?: Often, yes. A prototype that answered its question and got stopped did its job. Leaving that work unacknowledged teaches people that only shipped things count, which makes them reluctant to stop bad projects early.
When is the right time to send it?: Within a few days of the launch. The energy for it drains fast, and a thank-you that arrives a month later competes with whatever the team is now behind on.