New-hire first week
One welcome video plus the four or five setup guides a new person actually needs on day one, so their first morning is self-serve instead of a series of interruptions.
Record it in this order
A three-minute welcome, camera on
Who you are, what this team does, and what their first week looks like. Camera on for this one: it is the only part of onboarding that is about belonging rather than mechanics.
Accounts and access
Capture yourself setting up a real account in each core tool. This is the guide they will follow at 9am, so it needs exact screenshots, not a list of tool names.
The one workflow they will do most
Whatever this role does twenty times a week. Record it end to end, at normal speed, including the bits you think are obvious.
Where things live
A short screen tour of the drives, boards, and channels. Say out loud which two matter and which twelve they can ignore for now.
Who to ask for what
Names, and the kind of question each person owns. This is the guide that stops them defaulting to asking you.
Why this beats a written onboarding doc
- The setup guides are click-accurate, so a new hire is not translating a paragraph into a screen they have never seen.
- The welcome video carries tone, which is the whole reason day one feels different at a good company.
- When a tool changes, you re-record that one guide rather than auditing a forty-page document.
What to annotate afterwards
- Blur anything with a real customer name or a real account number in it.
- Add a warning callout on the one step where new people reliably go wrong.
- Rename each guide to the question it answers, so "Set up your VPN" beats "IT Guide 3".
How to hand it over
Use the document builder to combine the guides into one first-week manual, then share the document rather than five separate links. On a Team plan, view analytics tell you what they actually got through, which is a better check-in prompt than "how is it going".
Related: onboarding and training.