Mermaid code
journey
title New hire onboarding
section Before day one
Sign offer and paperwork: 4: New hire, HR
Ship laptop and badge: 3: IT
Schedule first-week meetings: 4: Manager
section First week
Account setup and access: 2: New hire, IT
Team introductions: 5: New hire, Manager
Read architecture docs: 3: New hire
section First month
Ship first small change: 4: New hire, Buddy
30-day check-in: 5: New hire, Manager Paste this into any tool that renders Mermaid, or into the editor to change the theme and export PNG or SVG. Syntax reference: User Journey guide.
What this diagram shows
Each line follows Task: score: Actor, Actor. The low point in this example is Account setup and access at a score of 2, which is the step most companies lose a day on. The actors column shows that IT appears before and during the first week, while the buddy only shows up once the new hire starts shipping code.
A journey diagram fits better than a Gantt chart here because the question is not how long each step takes but how it feels and who shares the work.
How to adapt it
- Replace the actors with your real roles, for example
Recruiter,Team lead,Security. - Score each task from a recent new-hire survey rather than guessing; the chart is only useful if the low scores are real.
- Add a
Before offersection if you want to include interview scheduling and offer negotiation. - Keep each section under five tasks; longer sections make the colored faces hard to read.
FAQ
What do the scores mean and who decides them?
The score is the experience rating for that task, 1 being painful and 5 being smooth. Take it from new-hire feedback at the 30-day check-in so the map reflects what people actually felt.
Can one task have more than two actors?
Yes. List them comma-separated after the score. Each distinct actor gets its own color in the legend, so keep the total number of actors across the diagram under six.