Technomatic All articles
Workplace Automation

Sticky Notes Are Not a Joiner-Mover-Leaver Policy: Tech Onboarding for a Five-Person UK Team

Technomatic
Sticky Notes Are Not a Joiner-Mover-Leaver Policy: Tech Onboarding for a Five-Person UK Team

Photo: Michael Steele , CC BY-SA 2.0, via Wikimedia Commons

Small teams have a special kind of tech chaos. The new starter arrives, someone hands them a laptop, someone else mutters a Wi-Fi password, and the shared inbox login is in a text message from 2023. It works until it does not. The fix is not a sprawling IT policy. It is a 45-minute routine that you run the same way every time — and then mirror when someone leaves.

Minutes 0–10: identity before hardware

Create the work account first. If you use Google Workspace or Microsoft 365, the new starter should get a proper work identity, not a shared login. Add them to the right groups: everyone, the team calendar, the shared drive, the phone system if you have one. Give them access to the shared inbox through delegation or a proper shared mailbox, not by handing over the main password.

Turn on multi-factor authentication before they log in for the first time. Use an authenticator app or a hardware key, not SMS if you can avoid it. Save the recovery codes somewhere secure — a password manager entry for the business, not a note taped under the desk. If you have a break-glass admin account, make sure it is documented and not used for everyday work.

Minutes 10–20: passwords and shared resources

Invite the new starter to your password manager and put them in the right vault. Shared passwords should live there, not in email, spreadsheets or WhatsApp. If two people need the same supplier login, that is a shared credential — treat it as a risk and move it into the vault with an audit trail.

Set up the shared inbox rules, calendar access and file permissions. Check that they can open the folders they actually need, and that they cannot see the payroll folder just because someone dragged it into the wrong parent directory. Least privilege sounds corporate; in practice it just means 'give access when there is a reason'.

Minutes 20–35: the device

Use a company-owned laptop if you possibly can. Set it up with full-disk encryption, automatic updates and endpoint protection before it leaves the office. Sign in with the work account, not a personal Microsoft or Google account. Install the browser profile, the password manager extension, the video-call app and the printer driver. Test the webcam and microphone on a real call, not just in settings.

Add the device to a simple asset register: asset tag, serial number, model, assigned user, date issued, charger included, warranty end date. A spreadsheet is fine. The point is that when the laptop goes missing, you know which one it is and who had it.

Minutes 35–45: the handover

Sit with the new starter for fifteen minutes and show them how your team actually works. Where the files live. How the shared inbox is triaged. Who approves expenses. How to book the meeting room. How to report a phishing email. Write it down in a shared doc, because the second new starter will ask the same questions.

Then automate the checklist itself. A simple Trello, Asana or Notion board with the same tasks every time is enough. The goal is not to create bureaucracy. The goal is to stop the onboarding depending on whoever happens to be free that morning.

The offboarding mirror

The same checklist should work in reverse. Disable the account, revoke active sessions and app tokens, remove them from groups, transfer the shared inbox and files, collect the laptop and charger, wipe the device, and update the asset register. Check for personal accounts they may have used for work — and remove them from the password manager vault.

Do this within a day, not a month. A dormant account with access to the shared inbox is a bigger risk than a missing charger. If someone leaves badly, you will be glad the routine already exists.

What to review every quarter

Once a quarter, spend twenty minutes reviewing who has access to what. Remove anyone who has changed roles. Check that MFA is still enforced. Look at the asset register for laptops that have not been seen in months. Update the onboarding doc with anything that caused a headache.

For a five-person UK team, that is enough. You do not need a helpdesk ticketing system or a 40-page security policy. You need a boring, repeatable routine that keeps passwords out of sticky notes and makes leaving as calm as joining.

All Articles

Related Articles

The Printer Isn't Broken: A Ten-Minute Home-Office Intervention

The Printer Isn't Broken: A Ten-Minute Home-Office Intervention

The 60W Impostor: How to Identify and Label Every USB-C Cable You Own

The 60W Impostor: How to Identify and Label Every USB-C Cable You Own

Zombie Subscriptions and Stale Passwords: A 90-Minute Household Tech Audit

Zombie Subscriptions and Stale Passwords: A 90-Minute Household Tech Audit