Most businesses think about onboarding as an HR function. It is the paperwork, the benefits enrollment, the handbook signature, the introduction to the team.
The IT onboarding experience, which happens in parallel with all of that, rarely gets the same attention. It tends to be informal. Whoever is handling IT makes sure the new person has a device and can get into email. Beyond that, it is mostly reactive. Whatever the new hire cannot access, they raise, and someone figures it out.
That approach produces a first week that is, for most new employees, defined more by what does not work than by what does.
What the First Week Actually Communicates
A new employee is spending their first week building a mental model of the organization. They are observing how people interact, how decisions get made, and whether the processes they were told about exist in practice or just in documentation.
The IT experience in that first week is one of the most direct inputs into that mental model. A device that is already enrolled, configured, and ready to use on day one communicates that the team anticipated their arrival and prepared for it. A device that arrives partially set up, with some applications missing and access to three of the eight systems they need, communicates something different.
New employees rarely say “I quit because the onboarding IT was rough.” What they do is update their expectations downward. They adjust their assessment of how well the company runs. They become more likely to tolerate future friction because the first week established that friction is the norm.
What a Documented Onboarding Process Includes
A proper IT onboarding process is a checklist that runs the same way every time, for every new hire, regardless of which team member is responsible for executing it.
It starts before the employee’s first day. The device is ordered, enrolled in the device management system, and configured with the standard software load. The accounts are created: email, the project management tool, the communication platform, the file storage system, any role-specific applications. The device arrives at the employee’s desk, or ships to their home office, ready to use.
On day one, the employee turns on the device, authenticates, and has access to everything they need. The IT team receives a confirmation that the process completed as expected. If anything was missed, there is a channel to resolve it the same day.
That is a documented checklist that someone built once and runs every time. The investment in building it pays back every time a new hire starts without friction.
The Expedient Termination Problem
The new hire process has a mirror image: the offboarding process, and specifically the version of it that has to run in hours rather than days.
Most businesses plan for planned departures. The two-week notice, the knowledge transfer, the gradual handoff. What they plan for less often is the situation where someone needs to be removed immediately and completely: the termination for cause, the security incident, the sudden breakdown in trust.
In that situation, the question is not “did we get the laptop back.” The question is “has this person’s access to every company system been revoked, and can we confirm that now?” For a business with a managed environment and a documented offboarding checklist, that confirmation takes minutes. For a business running informally, it takes much longer and involves much more uncertainty.
The offboarding process built for the easy departure is insufficient for the hard one. The right process is built for the hard one and run for all of them.
The Cost of Improvised Onboarding
A team member spending two days in their first week tracking down access and waiting for equipment is a productivity cost that shows up immediately on the P&L of their salary.
For a new hire at $70,000 per year, two days of unproductive time costs around $540. Across six new hires a year, that is over $3,000 in absorbed cost, before you count the time the existing team spends helping the new person navigate access problems. Before you count the manager time spent troubleshooting. Before you count the morale impact of a rough first impression.
The documented process eliminates most of that cost. Building the checklist takes a few hours once and then runs for years. The economics favor doing it.
The Connection to Device Management
The documented onboarding process depends on having the infrastructure to execute it. A business without device management cannot provision a device before the employee arrives and have it arrive configured. A business without a password manager cannot create account access centrally and provision it before day one. A business without a documented system list cannot know, reliably, what access every new hire needs.
The onboarding process and the IT infrastructure are the same problem from different angles. When the infrastructure is in place, the onboarding process is a natural extension of it. When the infrastructure is informal, onboarding improvises around the gaps.
Designed vs Accumulated
Every business has an onboarding experience for new employees. The question is whether it was designed or accumulated.
Accumulated means it developed organically through a series of past hires, each one adding one more informal step to an informal process. It works inconsistently, depends on whoever is around to execute it, and produces a different experience depending on which team members are involved and how busy they are that week.Designed means someone mapped it out deliberately, built the supporting infrastructure, and documented it so that anyone can run it the same way every time. The investment is front-loaded. The benefit runs indefinitely. And every new hire who walks in on day one to a fully set-up device is a small, recurring return on that investment.