What a New Hire's First Morning Tells You About Your IT Team

The new hire walks in at 8:55 carrying a bag that isn't theirs yet. By half past nine they will know more about how your IT team works than any org chart could tell them. Either the laptop is on the desk with the account already alive and the mailbox loading, or they are sitting in reception while somebody says "let me check with IT". Everything that happens in that person's first six months is coloured by which version they got.

The first hour is a promise you either keep or break

The work starts weeks before the person arrives, and almost none of it is technical. An account created on the morning they start means you are typing a name into a form while they watch you mistype it. An account created a week early, with the right groups, the manager already notified, and a printed card with their login details, means they spend that first hour meeting people instead of waiting. You can tell which kind of company you have walked into within about four minutes of the door opening. Nobody says it out loud, because a new starter will not complain that the chair wasn't ready, but they file it away, and so does the manager who hired them.

Onboarding is a handoff, not a form

Most onboarding tickets die of tidiness. The asset field is filled, the laptop is signed out, the ticket is closed, and the person still doesn't know where the shared drive lives or how to approve their own timesheet. Ten minutes of sitting next to them — walking through the second factor prompt, opening the one shared folder that actually matters, telling them exactly who to call when the screen goes black — costs less than the three tickets it prevents that same week. The other quiet failure is ownership. The manager assumes IT handles it. IT assumes HR owns the checklist. The paperwork gets completed either way; the only thing that falls through the gap is the person.

The last day is where security and dignity collide

Offboarding is the same process in reverse, except everyone is uncomfortable. Revoke access too early and a colleague who gave eight years leaves feeling like a suspect, locked out mid-handover with a project still half on their desktop. Revoke it too late and an active account sits in a mailbox nobody is watching for three weeks. The version that works is boring: agree the handover date, sit with them and copy the files that genuinely belong to the company, transfer the shared mailbox with the manager copied in, then disable the account that evening and write down what was removed. Two sentences to the manager the next morning — what is gone, what is still live, what needs reassigning — prevent the awkward phone call a month later. The person leaving notices how this goes as well. Former employees talk, and a few of them come back as clients.

The parts nobody puts on the job description

None of this is in the advert. The advert says Windows, networking, ticketing systems. What the role actually asks for is remembering that a first day is an emotional event for someone who has not yet earned the right to ask for help, and that a last day is one too. You can improve both without a budget. Name one owner for each step, put a date next to it, and once a quarter create a fake employee and walk the whole process yourself to see where it breaks. Keep the asset list honest, because the day a laptop goes missing is the day the spreadsheet becomes evidence. Then resist the urge to treat provisioning as paperwork. It is the first thing a new colleague learns about how this company treats people, and the last thing a departing one remembers. Nobody recalls whether the ticket closed on time. They remember whether someone was expecting them.