ThemePeople & wellbeing
CardCard 33 of 65
Questions5 to explore

Offboarding

Transition, knowledge sharing & celebration

Offboarding done poorly means knowledge walks out the door and the person leaving carries an incomplete sense of ending.

In an office, the final weeks of someone's time at a company tend to have a natural texture: goodbye lunches, desk clearing, conversations that happen in passing. In a hybrid or remote team, those moments do not form automatically. The departing person may stop appearing in the chat feed and that is roughly it. The experience for them and for the team is thin.

Good offboarding covers two things equally: the human experience of leaving and the practical work of knowledge transfer. Both matter in hybrid teams, and both require intention. A structured offboarding process protects the team's institutional memory and gives the person leaving something that feels like a proper closing.

Make it explicitCreate a short offboarding template: what knowledge gets documented and where, who handles system access, and what closing ritual or acknowledgment the team will use.

How strong hybrid teams handle it

The same building block, handled well. These are patterns from teams that work well across locations, offered as illustrations to react to, not rules to copy.

Knowledge transfer before access ends

Some teams require a simple handover document as part of offboarding: key projects, contacts, where things live, decisions in progress. Written while the person still has context, it saves the team from reconstructing what they were doing from scattered traces.

A visible farewell

A team post, a short video call, or a shared message thread where people can say something to the departing member gives the leaving person a sense of closure and signals to the rest of the team that tenure is recognised, not just ended.

Access hygiene

Agree in advance who revokes which access and when: tools, shared drives, communication channels, credentials. In hybrid teams with lots of SaaS tooling, this tends to be distributed and easy to miss without a checklist.

Exit understanding

Some teams conduct a brief exit conversation, not a formal survey but a genuine talk about what worked, what did not, and what the person wishes had been different. Hybrid teams benefit from this insight disproportionately, because friction that goes unspoken is harder to detect.

Questions for your team

Use these on your own or in a group. There are no right answers, only better conversations.

What happens in your team when someone leaves, and does it feel like a proper close for them and for you?
Where does the knowledge a departing person holds actually end up, and how findable is it?
Who is responsible for revoking access to tools and systems when someone leaves, and is that tracked?
How do remote members of your team hear about and participate in farewells for a departing colleague?
What has been lost when a team member left in the past, and could a structured offboarding process have prevented it?

Watch for

In hybrid teams, the departing person's last days often pass without the team noticing, which leaves both sides with a weak ending that is hard to describe but easy to feel.
Knowledge transfer is almost always underestimated: what seems obvious to the person leaving is invisible context for everyone who comes after them.
Access removal that is not tracked and assigned tends to be incomplete; former members retain access to sensitive tools for months because nobody had a clear checklist.