How to write a resignation message to your team

A resignation message needs three facts: your last working day, what you are handing over, and who people should ask once you are gone. Most of what gets added on top of those is what causes the trouble.

Hardly anyone writes one of these more than a few times in a career, which is why the same handful of mistakes turns up in almost all of them. It also gets reread long after you have gone, usually by someone deciding whether to put your name forward.

Tell your manager before you write anything

Your manager should hear it from you directly, before anyone else on the team knows and before a word of it is posted anywhere.

The order matters more than the wording here. A manager who learns you are leaving from a channel post has to handle their own surprise in front of an audience, and people remember being embarrassed long after they forget what you actually said.

Say it out loud if you can. Then send the written version the same day, because someone needs the date on record and because you want that date written the way you said it, not the way it was remembered.

The note to your manager is a date and a plan

Keep the formal note to four short parts and resist filling it out.

• One sentence saying you are resigning from your role.
• Your last working day, with the notice period already counted so nobody has to do the arithmetic.
• One line offering a handover, and a time this week to sort out what it covers.
• One line of thanks, if you mean it. One.

That is four lines, five if the handover offer needs a time attached to it. It feels too thin for something this big, so people pad it, and the padding is where the trouble starts.

Leave the reason out

Do not explain why you are leaving in writing. Not the good reason, and definitely not the honest one.

This is the part people push back on, so here is the argument. A written reason is quotable and permanent, and it will be read by people who were nowhere near the room where you decided. "I want to work on something closer to hardware" sounds gracious to you and reads as a complaint about the roadmap to whoever owns the roadmap. "For personal reasons" invites guessing, and the guesses are rarely kind.

You can say plenty of it out loud, to the two or three people who have earned it. Say it in an exit conversation if you trust the process. Just keep it out of the document that gets pasted into other documents.

The same goes for grievances. If something at that job was genuinely wrong, a farewell post is the weakest possible place to raise it, because it arrives dressed as a goodbye and it lands as a parting shot. You lose the argument by winning the room for one afternoon.

The team post is shorter than you think

The message to your team says when you finish and what happens to your work. Three or four sentences, in the channel where the team already talks.

Cut the gratitude essay. Nobody believes an adjective in a farewell post, and the people who actually mattered to you should hear it from you in a message with their name on it, not read it in a broadcast where they are one bullet in a list of shout-outs.

Two things worth leaving out that people reliably include:

• An open offer to help with anything after you leave. You will not, and everyone knows it, so it reads as politeness rather than a plan.
• Your new employer's name, unless you are genuinely happy for it to be discussed all week without you in the conversation.

A personal address is fine, and it is nice. Put it in the last line, quietly, for the people who want to keep in touch.

The handover is the real message

People will judge your exit on what they find in your absence when something breaks at 4pm on a Friday, not on your farewell note.

So put the writing effort there instead. A handover note before vacation covers the mechanics, and one thing changes when you are not coming back: write down the judgment, not the procedures. The approval step you skip on purpose and why. The client you quietly stopped chasing. Procedures survive in a document without you. Judgment walks out with you unless someone writes it down.

The kindest version of this is a list of the things that will go wrong and what to do about each. Slightly humiliating to write. Extremely useful to receive.

Do not change your voice on the way out

Write the resignation in the register you have used at work all along, because a sudden switch to formal language reads as distance, and distance right now looks like a grudge.

I think about register a lot because of what I build. Unvent rewrites what you are typing into the tone you pick, and one of the things it does on every rewrite is strip out the em dashes. That rule is there because over-polished text has a smell, and readers catch it without being able to say why. In your final week, when people are already reading everything closely for hidden meaning, sounding unlike yourself is a message all on its own.

So no "Please be advised" if you have never once been advised of anything. No sudden "Dear all" in a channel where you have said "hey" for two years. The content is the news. The voice should be the same voice as last Tuesday.

Your notice period is the actual document

How you behave in your last two weeks will outweigh anything you wrote in the note, so budget the effort accordingly.

Answer questions properly, including the ones you have already answered twice. Sit with whoever is inheriting your work for longer than the calendar block says, especially if they look nervous about it. What you do here is the part people quote later, when someone asks them about you and there is nothing in it for you either way.

Then leave on your date, and do not send a second goodbye. One is a goodbye, two is a performance.