Streamline offboarding with draw.io diagrams

A smooth offboarding reduces friction

Offboarding is never a fun topic, but it is a vital process.

Diagrams can help make this task smoother and less painful for everyone involved. Ensuring the offboarding process is documented reduces confusion and friction points across teams, and having key processes documented by the departing colleague ensures key information doesn’t go missing once they’ve handed in their equipment.

While draw.io is known for complex use cases such as UML, ERD, and BPMN diagrams, today we’ll be looking at how it can help HR teams to optimize offboarding processes and keep things streamlined and consistent.

In this blogpost we’ll look at 3 diagrams that will help with the offboarding process, including capturing and keeping key processes up to date in your team as part of good housekeeping and knowledge sharing, and visualizations that help for a smooth offboarding and onboarding of new hires.

Don’t lose valuable information

Diagrams are incredibly effective for offboarding because they convert tacit knowledge (the “know-how” in a colleague’s head) into explicit knowledge (documented, visual instructions) that a team can actually use, long after an individual has left the company.

When a colleague leaves, the goal is to minimize disruption to workflows and avoid “knowledge leakage,” where precious knowledge is lost when a person leaves. You also want the new person joining to be onboarded as quickly as possible, and keeping clear, accessible documentation as part of their onboarding ensures this.

3 diagrams for a smooth offboarding

Here is how different types of diagrams facilitate a smooth transition:

1. Offboarding process flowchart

A swimlane diagram is ideal for capturing the process of offboarding a colleague. It shows the key stakeholders involved: the employee, their manager, HR, and IT, and outlines the process from start to finish and how these stakeholders interact.

The best part about this diagram is that it documents crucial parts of the process: capturing learnings from the exit interview that the manager can take forward, so there are no lingering problems that contribute to a colleague deciding to depart. Additionally, the process of returning equipment and disabling logins and accounts ensures there are no security breaches once the colleague has left.

Pro tip: Creating the offboarding process diagram in Confluence allows you to link to other key Confluence pages, like in the example below – the team RACI chart is added as a link to the relevant text.

To add a link:

1. Right-click on the relevant shape,
2. Click on Edit Link…
3. Paste the link into the text box,
4. Click OK.

We’ll now look at RACI charts in more detail:

2. RACI charts

RACI charts provide an overview of the various roles and responsibilities within a team: those who are Responsible, Accountable, Consulted, or Informed on a given task or dependency.

Updating RACI charts after a former colleague leaves should be standard practice in any offboarding process. It ensures everyone knows who to go to in the interim period while waiting for the position to be filled. Then, the RACI charts should be updated once again when the new colleague joins and is up to speed, so everyone knows who to go to for their specific area of responsibility.

Pro tip: Rather than trying to cram all information into one RACI chart, you may need multiple charts, even for just one team. You can use draw.io’s multipage diagramming feature to keep all RACI charts in one place, separated out onto different pages.

For example, you might have the following RACI charts for recurring tasks within different areas of your team operations:

• HR and overall strategy
• Marketing tasks
• Sales tasks
• Admin tasks

3. Stakeholder maps

Stakeholder maps indicate the health of stakeholder relationships. The power-interest grid or Mendelow’s Matrix is one type of stakeholder map used in many areas of business and marketing, and consists of four quadrants:

• Manage Closely (High Influence, High Interest)
• Keep Satisfied (High Influence, Low Interest)
• Keep Informed (High Interest, Low Influence)
• Monitor (Low Interest, Low Influence)

As part of offboarding, a colleague leaving can help their successor navigate delicate interactions beyond a traditional org chart, using the map to highlight things like dependencies, communication channel preferences, and approvals.

Pro tip: Use the draw.io Board editor to build your stakeholder map. Both editors have the exact same features; they just offer two different editor styles: the Diagram editor for technical flowcharts, ERDs, etc., and the Board editor for creative brainstorming, mind maps, and more free-form visualization.

With the draw.io app, Confluence users can create unlimited diagrams and whiteboards with draw.io at no extra cost.

FAQs

How do I ensure information doesn’t go missing when a colleague departs?

A combination of good document housekeeping and Confluence search will help you here.

Encourage departing employees to move pages, like a handover document and related resources, from their Personal Space in Confluence to the shared Team Space.

Because draw.io diagrams are embedded directly into Confluence pages, any text within them is indexed by Confluence search. This makes “lost” knowledge easy to find for the rest of the team.

Is the colleague still able to access the Confluence pages they’ve created after they leave?

Because draw.io diagrams inherit the security settings of the host page, once a departing colleague’s access to a space or page is removed via Confluence permissions, they automatically lose access to any diagrams embedded there. Access is revoked the moment their Atlassian account is suspended or removed by your site administrator at admin.atlassian.com.

What if the departing colleague was the “owner” of the diagram?

Since draw.io diagrams are stored as attachments within the Confluence page, ownership stays with the page. Anyone with edit permissions for that page can pick up right where they left off.

Can I create these offboarding diagrams in Jira too?

Yes! If you use draw.io for Jira, and your offboarding involves a Jira ticket checklist, you can embed your draw.io process diagrams directly into the ticket so the HR or IT assignee sees the process overview instantly.

The visual path to a seamless transition

Offboarding with draw.io for Confluence transforms complex, undocumented knowledge into clear, accessible assets, ensuring seamless transitions and preventing critical information loss. By embedding offboarding diagrams directly into Confluence pages, organizations can maintain smooth business operations, improve knowledge sharing in and across teams, and accelerate new employee onboarding.

Want to dive deeper into the world of draw.io? Access our linktr.ee page to follow us on social media and learn how others use draw.io, as well as pick up some helpful tips and tricks.