Online Farewell Cards: Sending Off a Colleague Properly

Intro

Somebody is leaving in eight days and you have been handed the card.

The job looks small and is not. You have to collect messages from people who all intend to write something and mostly will not, you have to write your own without falling back on "it was great working with you", and you have to handle the part nobody says out loud: that some departures are celebrations and some are not, and the card has to work either way.

This covers what to write, how to get the team to contribute, and when a card is the wrong format entirely.

Timing: earlier than feels necessary

Start collecting a week to ten days before the last day. Not three days. The single biggest reason farewell cards arrive thin is that they were started on Tuesday for a Friday leaving date.

People need to see the request more than once, and the good messages come from people who sat with it for a day. Someone who worked with the leaver for four years cannot produce anything worth reading in the ninety seconds between meetings when they first see your message.

Deliver it before the last day, not on it. The final day is full of handovers, goodbyes and logistics. A card opened on the second-to-last day gets read properly, and it gives the leaver a day to reply to people, which they usually want to do.

Getting people to actually contribute

The failure mode is predictable. You post the link in a channel, seven people contribute in the first hour, and then nothing for four days.

Write the first message yourself, and make it specific. An empty board is intimidating. Nobody wants to set the tone, and the first message sets it. Write something concrete about the person, and the next contributor has a model that is not "best of luck!".

Ask six people directly. A channel post reaches everyone and obligates nobody. Six direct messages to people who worked closely with the leaver produce six real messages, and those six make the board worth joining for everyone who sees it afterwards.

Give a deadline with a reason attached. "By Wednesday, because we are giving it to him at Thursday's standup" works. "Whenever you get a chance" does not.

Chase once, and make it easy. One reminder, two days before the deadline, with the link in the message rather than "see above". Then stop. A third ask produces obligation messages, and obligation messages read exactly like what they are.

Tell people what it is for. "We are putting together messages for Ana, who is leaving after six years" gets a different response from a bare link.

What to write

The general rule: one specific thing beats three warm generalities. "Thanks for everything, you will be missed" is kind and interchangeable. "You rewrote the onboarding doc in your second week and nobody has been lost since" is a thing only you can say. The same principle runs through our appreciation message examples, if you want more to work from.

If you worked closely with them

Name something that changed because of them, and something you took from them.

“Working with you on the migration was the most I have learned in a year here. You never once made me feel stupid for asking the same question twice, and I have started doing that with new starters because of you. The team is going to feel this.„

If you know them a little

Do not fake depth. One true observation beats a paragraph of manufactured closeness.

“We only overlapped on the Q3 project, but you were the person who actually read the brief before the kickoff and it showed. Good luck with what is next.„

If they are your manager

Specificity matters more here, because generic messages to managers read as obligatory.

“You backed me on the pricing thing when it would have been easier not to, and I have thought about that a lot since. Thank you for making the case for me when I was not in the room.„

If you are their manager

Say what they contributed, in concrete terms, and say it as a statement rather than an evaluation. This is not a performance review.

“You took on the support backlog when nobody wanted it and turned it into the thing the team is now known for. That was your doing. Wherever you land next is lucky to have you.„

If the departure is difficult

Redundancy, a bad exit, someone leaving because of something that happened. The card still goes round, and forced cheerfulness is worse than brevity.

Keep it short, keep it true, do not reference the circumstances.

“I am glad I got to work with you. You made the Tuesday reviews something I looked forward to. Keep in touch.„

Nobody is obliged to be delighted. A short honest message is a kindness; a long performance of enthusiasm is not.

What not to write

• Inside jokes only three people understand. The board is read by the recipient later, alone.
• Anything about why they are leaving, unless they have made it public themselves.
• "Don't be a stranger" and its relatives. They cost nothing and say nothing.
• Complaints about their departure creating work for you. This happens more than you would think.
• Anything you would not want a future employer of theirs to read. Shared boards get shown around.

A card or a board

These are different formats and the difference matters.

A card is one page that people sign. Short messages, everyone in one view, reads quickly. Right for a team of about ten, for someone who was there a year, for a departure that is friendly and uncomplicated.

A board gives every person their own space, with room for a photo. Reads like a wall rather than a list. Right when the leaver was there for years, when more than twenty people want to contribute, or when the messages need room to be more than a line.

The practical test: if you expect more than fifteen contributors, or if several people will want to write a paragraph rather than a sentence, use a board. A card with thirty cramped signatures on it is worse than either format done properly.

Doing it with Flareeboard

If your company runs Flaree, the board is already there and does not need buying.

Create a board for the person, pick the occasion, and publish it. Everyone in the company is told it is open, through Slack if you use Slack and by email otherwise, and the person it is for is left out of that notification, so it stays a surprise. They cannot see the board at all until you deliver it.

Anyone who can send a Flaree can post. Messages run to 500 characters and can carry a photo. There is no cap on contributors or on how many times someone posts, and people can edit their own message until the board closes.

When you deliver it, the board reaches them in one moment with a full-screen reveal rather than a notification they skim. You can also turn on rewards, which gives everyone who wrote on the board the cover card and points, once per person, when it is delivered.

Afterwards, the board can be given a public link so the leaver keeps it after their account is gone. Author names on that page are shortened to a first name and an initial, and it is not indexed by search engines.

Company-wide boards are on the free plan. Boards for one person are part of Advance and open during the 90-day trial. See pricing for the detail.

Conclusion

• Start a week out.* Three days is the main reason cards arrive thin.
• Write the first message yourself*, and make it specific enough to set a standard.
• Ask six people directly.* The channel post is not the ask.
• One concrete thing beats three warm generalities.* Name what changed because of them.
• Difficult departures get short honest messages*, not performed cheerfulness.
• Deliver before the last day*, so it gets read properly and they can reply.

If your team writes its best things about people on the way out, that is worth noticing. The same mechanism works for people who are staying, which is what ongoing recognition is for. You can try a board free.