What Your Business Looks Like to a New Employee on Day One
What Your Business Looks Like to a New Employee on Day One
New employees form impressions quickly. The office, the people, the culture. And quietly, almost without thinking about it: the IT.
Whether accounts exist for them. Whether anyone set up their equipment. Whether they spend the first morning waiting for someone to figure out how to give them access to the tools they need to do their job.
The IT experience on day one is not just an inconvenience when it goes wrong. It is a signal about how the business is organised. And it surfaces something more practically useful for business owners: the gaps in how access, accounts, and documentation are managed.
What a Good Day One Looks Like
A new employee arrives. Their equipment is ready. Their accounts exist. Email, the main communication tools, the software they need to do their job. Someone has set a temporary password and they can change it themselves. They have access to the things they need and only those things.
By midday they are working. Not waiting.
This does not require sophisticated IT infrastructure. It requires someone having thought about the list of things a new person needs before they arrived, and having prepared them. Documentation of what access to create, a checklist of systems to set up, a process that does not depend on whoever happens to be in the office that day remembering what to do.
What Day One Usually Looks Like
The more common experience goes differently.
The laptop was not set up in advance. Or it was, but nobody remembered the login credentials. The email account exists but the calendar is not connected to anything. The shared drive is accessible but nobody is sure which folders they should have access to. The project management tool requires a separate invitation that someone forgot to send. The phone system needs a configuration that only one person knows how to do and they are not in that day.
By midday the new employee has met a lot of people and sent approximately one email.
None of this is catastrophic. But it is telling. Each of these small failures reflects a gap in how access and systems are managed, documented, and handed off.
What Day One Reveals About Your IT
The friction a new employee experiences is a proxy for the friction anyone experiences when they need to navigate your IT setup without prior knowledge of it.
If nobody knows which systems need a new account, documentation is missing. A new hire surfaces this immediately because they arrive with zero existing access. But the same gap appears when someone leaves and nobody can identify what access to remove. Or when an IT provider changes and the new one cannot determine what they are taking over.
If access takes days because it requires one specific person, you have a single point of failure. The person who knows how to set up the VPN, or who has admin access to the accounting software, or who manages the phone system. When they are unavailable, everything waits. This is a real operational risk that feels manageable until the person in question is sick, on holiday, or has left.
If a new employee gets access to more than they should because it was easier to add them to everything, access controls are not working. Over-provisioning is how stale access accumulates. The contractor who was added to everything three years ago and still has an active account. The former employee whose access was mostly removed but whose login to one system nobody remembered to close.
If equipment setup takes hours because nobody prepared, there is no onboarding process. This one is fixable with a checklist. But the checklist does not exist if nobody has written it down.
The Offboarding Mirror
Everything that goes wrong on day one has a corresponding risk on the last day.
The accounts that took three days to set up will take three days to close if nobody has a list of them. The system that required one specific person to configure will require the same person to remove access, if anyone remembers to ask. The over-provisioned access that felt harmless on the way in becomes a real security gap on the way out if it is not revoked.
The businesses that handle both well are the ones that have a documented list of systems, a clear process for adding and removing access, and someone who owns that process rather than it being whoever happens to think of it.
A Practical Starting Point
You do not need a formal IT onboarding programme to do this better. You need three things:
A list of every system that requires an account. Email, file storage, project management, communication tools, accounting software, industry-specific tools, any cloud services, the website CMS, the payment processor. Write it down. This list is the basis for both onboarding and offboarding.
A process for new starters. Before someone arrives: create accounts, set temporary passwords, prepare equipment, confirm access to shared resources. A checklist takes 30 minutes to create and saves hours per hire indefinitely.
A process for leavers. When someone gives notice: work through the list, remove access systematically, confirm nothing is missed. Transfer anything they owned: documents, accounts registered in their name, recurring tasks they managed.
Neither of these is technical work. It is organisational work that happens to touch IT.
The Bigger Picture
The day one experience is a useful diagnostic because it is concrete. You can observe it. You can ask a new employee afterwards how it went and get a real answer.
What it reveals is whether access, documentation, and process have been treated as things that need active management or things that sort themselves out. For most small businesses, the honest answer is the latter. Not through negligence, but because nobody explicitly assigned ownership and because the gaps are invisible until someone new arrives and has to navigate them.
The same gaps that make day one frustrating are the ones that make vendor transitions expensive, IT provider handovers incomplete, and incident response slow. They are worth closing not just for the next new hire, but because the documentation and process that makes day one smooth is the same documentation and process that makes everything else more manageable.
FAQ
How much IT preparation is reasonable before a new employee starts? At minimum: accounts created, equipment ready, and someone responsible for walking them through access on day one. Beyond that, the right level depends on the role. Someone handling finances or customer data needs more careful access setup than someone in a role with limited system access.
We are a small business with only a few employees. Do we need a formal process? A formal process is probably overkill. A checklist is not. Even a simple document listing every system that needs an account, reviewed and updated when you hire or when systems change, is significantly better than relying on memory.
Our IT provider handles onboarding. Is that enough? It depends on what they are doing. If they are creating accounts and setting up equipment, that is useful. But the list of what access to create, and the decision about what each person should have access to, is a business decision rather than an IT decision. Your provider needs input from you, not just a name and a start date.
What is the most commonly missed system when someone leaves? Email is usually caught. The ones that get missed tend to be secondary systems: project management tools, industry-specific software, cloud services that were set up independently, and shared accounts where the person's credentials were the login rather than a personal account. The only reliable way to catch these is a list.
ExplainMyIT's external monthly snapshot does not cover internal access management directly, but the on-premise network monitor does surface connected devices and active services on your network, giving you a dated picture of what is running inside your office. If a device or service appears after a new hire or disappears after someone leaves, the change shows up in the next report.
See what your external setup looks like right now or learn more about the network monitor.
Related reading: