Let me paint you a picture.
It’s Monday morning. First day as the new Chief Operating Officer of Meridian Group — a growing, ambitious company right here in Metro Detroit. You’ve spent the last three weeks wrapping things up at your old job, fielding congratulations on LinkedIn, and quietly envisioning the impact you’re about to make.
You walk in the door with your laptop bag over one shoulder, a coffee in hand, and the kind of energy that only exists on Day 1 of a new job.
By noon, you’re tethered to your phone’s hotspot, trying to reset a password to a system you’ve never been given access to, while a cheerful out-of-office reply from the IT department informs you that ticket response times are “typically 24–48 business hours.”
Welcome to Meridian Group, Xavier.
The First Week, Unfiltered
Xavier Thompson had been in operations leadership for over fifteen years. He’d managed teams, led turnarounds, and navigated some genuinely difficult business environments. He was not, by any stretch, a person easily rattled.
But nothing quite prepares a senior executive for the specific, slow-burning frustration of a broken onboarding experience.
By Tuesday afternoon, Xavier had submitted four IT support tickets:
- Ticket #1: Laptop not configured. Standard software not installed. Sitting in a cardboard box on his desk the way it arrived from the manufacturer.
- Ticket #2: No access to the company’s shared drive. His EA had more visibility into the company’s files than he did.
- Ticket #3: VPN credentials never issued. Remote access? Not an option.
- Ticket #4: His email signature was pulling in the name of the person who previously held his role. Which made for a particularly interesting introduction to the board members he was emailing for the first time.
By Wednesday, he’d sat through two meetings where he couldn’t pull up a single document being discussed. He nodded along and took notes by hand like it was 1987.
By Thursday, he missed a critical leadership call entirely. The Zoom link had been sent to an email alias from his predecessor — one that had never been updated to reflect the fact that a new COO existed.
By Friday, Xavier was drafting a list — not of strategic priorities, not of operational improvements — but of everyone he needed to follow up with just to get access to the basic tools required to do his job.
He wasn’t upset in a dramatic way. He was something worse: quietly, competently concerned.
If this is how we treat a C-level executive on Day 1, what does onboarding look like for the 200 people below me?
The Ripple Effect Nobody Sees
Here’s the thing about a broken onboarding experience — it doesn’t just inconvenience the new hire. It costs the business in ways that rarely show up on a spreadsheet.
In Xavier’s first week, Meridian Group absorbed the following costs without ever realizing it:
Lost executive productivity. A COO’s time is expensive. By conservative estimate, Xavier spent 30–40% of his first week navigating access issues rather than doing the job he was hired to do. For a company that just made a senior leadership hire, that’s an immediate return-on-investment problem.
Delayed strategic momentum. Xavier had been brought in specifically to drive operational efficiency. He had ideas, frameworks, and a 90-day plan ready to execute. All of it was sitting idle while he waited on a ticket queue.
Confidence gap in the leadership team. Two of Meridian’s department heads noticed that their new COO couldn’t access documents in meetings. It didn’t torpedo anyone’s confidence — people understand Day 1 chaos — but it set a tone. And first impressions, even small ones, accumulate.
Near-miss with a client. On Thursday, a department head forwarded an urgent client request to Xavier’s inbox, expecting a quick operational decision. Xavier didn’t have access to the client account history, the associated project files, or the internal communication thread around the issue. The response was delayed by a full business day. The client noticed. It was handled — but only just.
None of these things made headlines. None of them showed up in a monthly report. But they were real, they were costly, and every single one of them traced back to the same root cause.
So What Actually Went Wrong?
This is the part where it would be easy to blame IT. But Xavier — being Xavier — didn’t do that.
When he finally connected with Meridian’s internal IT contact at the end of the week, he didn’t find negligence. He found a single, overwhelmed IT generalist managing the technology needs of a 200-person company, with no formal onboarding workflow, no asset management system, no documented provisioning checklist, and no process for coordinating with HR when a new hire — especially a senior one — was starting.
The problem wasn’t a bad person. It was a bad system. Or more precisely: the absence of a system.
Meridian had grown quickly over the past few years — from a scrappy 40-person operation to a 200-person company with serious revenue and real infrastructure needs. But its approach to IT had never scaled with it. Technology was still being managed reactively, ticket by ticket, problem by problem, with no strategic oversight and no one accountable for the employee experience from a technology standpoint.
The company had outgrown its IT setup. It just hadn’t realized it yet.
Xavier realized it in about four days.
The Phone Call
On Friday afternoon, Xavier closed his laptop — his unconfigured, unmanaged, still-not-quite-right laptop — and pulled out his cell phone.
He scrolled to a contact he’d carried over from his previous company and hadn’t needed to use in a while.
Xpert Technologies.
He’d worked with Xpert at his previous employer for the better part of five years. They weren’t just a vendor who showed up when things broke. They were the team that made sure things didn’t break in the first place — that had built systems, established processes, trained people, and treated technology as a strategic function rather than a necessary inconvenience.
When he left his last company, he’d honestly taken for granted how well things worked. You only notice a great IT partner when you suddenly don’t have one.
He made the call.
It wasn’t a formal RFP. It wasn’t a committee decision. It was a COO who had seen the difference between what good looks like and what he was currently living through, reaching out to a team he trusted.
“I need help,” he said. “Not emergency help. Systemic help.”
The Xpert team was on-site the following week.
What Came Next
Within 30 days of that phone call, Meridian Group had:
- A formal IT onboarding workflow integrated with HR, so that every new hire — from intern to C-suite — had their equipment configured, accounts provisioned, and access granted before their first day, not after their first week
- A device management platform that allowed IT to remotely configure, update, monitor, and if necessary remove access for any company device on the network
- A documented technology roadmap — the first time anyone at Meridian had ever looked at their IT environment and asked where are we, where are we going, and what do we need to get there?
- A technical team at Xpert who understood Meridian’s business, not just their ticketing queue
Xavier finally got his laptop configured properly. The email signature was fixed. The shared drives were accessible. The VPN worked.
It sounds small. It wasn’t.
Because the real value of that phone call wasn’t fixing Xavier’s laptop. It was the moment Meridian Group stopped treating IT as a cost center and started treating it as a function worth investing in.
The Part That Should Make Every Executive Uncomfortable
If you’re reading this and you’re in a leadership role — COO, CEO, CFO, doesn’t matter — here’s the question I’ll leave you with:
Do you actually know what the onboarding experience looks like for the people joining your company?
Not the HR side. Not the culture and values piece. The technology side. The “can you actually do your job on Day 1” side.
Because for a lot of growing companies, the honest answer is: no. And the cost of that gap — in productivity, in perception, in momentum — is real, even when it’s invisible.
Xavier found out the hard way. He also found out that fixing it wasn’t as complicated as he expected.
It started with a phone call.
Meridian Group is a fictional company. Xavier’s story is inspired by real challenges faced by real businesses navigating growth — and by the very real difference a proactive IT partner makes. Xpert Technologies partners with growing companies in Metro Detroit and beyond to build technology environments that support people from Day 1.
If Xavier’s first week sounds a little too familiar, let’s talk.
#ITSupport #BusinessGrowth #EmployeeOnboarding #ManagedServices #MetroDetroit #OperationalExcellence #XpertTechnologies