A new employee starts on Monday. By the time they sit down, is their device ready, their accounts provisioned, their software installed, and their access configured — or are they borrowing a colleague’s login, waiting on a ticket, and forming their first impression of the company around a setup that doesn’t work?
It is tempting to treat onboarding speed as a minor convenience. It isn’t. The way your IT provider handles a new starter is one of the clearest windows you have into how they run everything else. Onboarding is a litmus test.
The right question isn’t “how many hours does it take?” — every business and every starter is different. The right question is whether onboarding is a prepared, repeatable process or an improvised scramble. The answer tells you almost everything about the rest of your IT.
Onboarding Is a Litmus Test for Your IT
When a provider onboards a new user quickly and consistently, it is rarely because they worked fast on the day. It is because the work was already done. A clean configuration standard exists, deployment is automated, and the process runs the same way every time. That kind of discipline doesn’t appear only at onboarding — it is how the whole environment is managed.
The reverse is just as revealing. A provider who improvises every onboarding is improvising everywhere — they just haven’t shown you yet. Patching, backups, security baselines, and documentation are all run with the same level of preparation (or lack of it) that you see on a new starter’s first day. Onboarding is simply the first time you get to watch it happen.
What Slow, Ad-Hoc Onboarding Reveals
When onboarding drags or varies wildly from one starter to the next, it usually points to three underlying problems:
No runbook
A runbook is a documented configuration standard for your business — the exact settings, software, security controls, and accounts every device should have. Without one, each onboarding starts with discovery: the technician works out what to do by inspecting an existing device or asking around. If your provider has no runbook for your business, your environment isn’t being managed systematically — it is being remembered, person by person.
One-at-a-time configuration
Without modern device management, software and settings are applied manually on each machine. It is slow, it is error-prone, and it produces drift — one device ends up subtly different from the next. Those inconsistencies are not just future support headaches; they are security gaps, because no one can be certain which controls are actually in place.
Reactive rather than prepared
Many providers only begin onboarding once a start date is confirmed — sometimes days before the employee arrives. With hardware and licensing lead times, delay becomes inevitable, and the work happens under pressure rather than to a plan.
The cost of all this rarely shows up as a line item, but it is real. A new hire who can’t work loses days of productivity at exactly the moment momentum matters most. Colleagues are pulled away to answer basic questions and lend logins. Security baselines go unverified. And the new starter’s very first impression of the business is one of disorganisation — a poor note to begin on.
What Good Onboarding Looks Like
A well-run onboarding looks fast from the outside because the preparation happened before the employee arrived. The session with the new starter is short and uneventful — the interesting work is already finished. Here is what that preparation and session cover:
- Device configuration — The device arrives pre-imaged with the correct operating system, security baseline, and core applications, deployed via Microsoft Intune or a similar MDM platform. The session itself applies only the user-specific layer: account linking, email profile, and application sign-ins.
- Microsoft 365 provisioning — Email, Teams, SharePoint access, and other M365 applications are provisioned from a template that matches the employee’s role, rather than configured from scratch.
- Security controls — MFA is enrolled, the device is registered in the business’s endpoint management platform, and the security baseline is verified as active before the session ends.
- Application access — Line-of-business application access (accounting software, CRM, project management tools) is provisioned according to the runbook for that role.
- User orientation — The employee is shown how to raise a support ticket, what to do if their device misbehaves, and the key security practices they are expected to follow.
The session does not end until the employee can demonstrate they can complete their core tasks. That verification is what separates a complete onboarding from a configuration exercise. Because the groundwork is done in advance, a new user at Mino IT is typically set up and productive within about two hours — not as a marketing number, but as a by-product of having a runbook and automated deployment in place. (Transitioning a whole business from another provider is a different, structured project measured in weeks, not hours.)
The Real Question to Ask a Provider
Whether you are choosing a new IT provider or assessing the one you have, ask them to walk you through how they onboard a new user. Do they have a documented runbook for businesses like yours? Is deployment automated, or done by hand each time? Does the preparation start before the start date? The answers tell you whether your IT is being run to a standard or held together by individual memory.
This is the heart of what we mean by technology governance — the structured, documented, repeatable management of your IT environment. Onboarding is simply where it becomes visible first. If you want to see how Mino IT would approach onboarding for your specific environment, book a discovery call.
And if you are weighing up a move: new clients who sign a 12-month Total Coverage agreement before 30 September 2026 get their onboarding free. See our pricing page for details.
