The new hire was starting on Monday. I had her account list in front of me and I was working through it the way I always do: ticking off each tool against the access template for her role, checking her against the last person who had held the seat.
Help Scout. Done. Slack. Done. Google Workspace. Done.
Then HubSpot. I looked at the previous agent's record. She had a basic account, the kind that lets you log in and navigate the interface. No read access to contact records or deal history.
I paused. Assumed it was a setup error from when she had joined. Made a note to add the correct access and kept going.
But something nagged at me. Before I just added the permission and moved on, I pulled up the previous agent's ticket history. I wanted to make sure there was no downstream fallout from the gap before I closed it.
What the timestamps told me
The pattern was there once I knew to look. Every time she had needed account context during a support conversation, there was a gap in the thread. Not in her replies, which were detailed and consistently well-rated. In the timestamps between them. She would respond to a customer, go quiet for eight to twenty minutes, and then send a thorough follow-up. And in a second window, in Slack, there was always a message to someone on the sales team sandwiched into that silence.
She was asking for the CRM lookup manually. Every time.
I went back further. Six months. Twelve. Eighteen. The same pattern throughout. She had been doing this since the second week of her tenure.
Counting what it actually cost
I pulled her Slack direct messages with the sales team and counted the requests that contained phrases like "can you check," "what is the status on," or "do we have an open deal with." I stopped counting at around 340 messages across 18 months. That is roughly 19 per month, roughly one per working day.
Each one was a small thing. A two to five minute interruption for whoever she pinged. A gap in the customer conversation on her end. A context switch that cost something for everyone involved. Not dramatic. Not the kind of thing that shows up on a dashboard. Just a quiet, consistent tax on every account-related conversation she had ever handled.
Her CSAT numbers were fine. Her first-contact resolution rate was above the team average. She had been praised in the last team review for handling escalations particularly well. None of that assessment was wrong. But none of it captured what was actually happening in the background.
Two conversations I was not expecting
I messaged her previous manager, who had moved to a different team a few months earlier. I asked if she had known about the CRM access gap.
She had no idea. She had assumed the access was set up correctly at the start. The agent had never raised it, never filed a ticket, never mentioned it in any 1:1. From the manager's perspective, that role had CRM access. It was on the onboarding checklist. It must have been done.
Then I messaged the agent herself. She is still at the company, now in a different role. Her reply was one of those responses that stays with you.
She said she had thought that was just how things worked. She had assumed that asking the sales team for account lookups was the intended process. It had not occurred to her that there was a faster route or that anyone expected her to have direct access. She had adapted in week two and never revisited the assumption.
What workarounds do to high performers
This is what workarounds do when they land on the right person. They settle into the background so completely that the person running them stops seeing them as workarounds. They become the job. They become how we do things here.
The workarounds that are most dangerous are not the ones that frustrate people into raising tickets. Those get found and fixed. The dangerous ones are the workarounds that high performers absorb quietly and make work anyway. Because high performers are, by definition, good at absorbing friction. They adapt, optimize their personal workflow, find the path around the obstacle, and deliver results in spite of it.
Which means the gap disappears from every metric you are tracking.
If you audit your access setup by looking at CSAT, ticket volume, or handle time, you will miss this every time. Good numbers do not mean clean processes. Sometimes they mean someone skilled is compensating for a broken one.
The agent had not done anything wrong. She had done everything right, in the most literal sense. She delivered quality outcomes under a constraint she did not know was a constraint. And the system rewarded her for it by never surfacing the underlying problem.
What I fixed, and what I should have caught first
I granted the CRM access that afternoon. I updated the onboarding checklist to make that permission a required step with an explicit verification note. That took about fifteen minutes.
Then I did the thing I should have done before the new hire was even in the picture: I audited every current agent on the team against the same access benchmark. What does someone in this role actually need to do the job well? Does every current holder of the role have all of it?
I found two more similar gaps. One agent had been manually exporting data from a reporting tool because she lacked access to the live dashboard. Another had been using a shared login for a tool where individual accounts were available and, more to the point, more secure. Both had been running these workarounds for months. Neither had raised a flag. Both had adapted so thoroughly that I had never thought to check.
Onboarding is an audit, whether you treat it that way or not
Setting up a new hire is one of the best forced audits you will ever run on your own systems, because it makes you go through the setup fresh rather than assuming the template is correct. When you copy a template, you copy every gap in that template. When you hand a new hire a checklist, you hand them the accumulated drift of every onboarding that came before.
The question worth asking when you set up a new hire is not only "does this access grant work." It is: does this person have everything they actually need to do this job well? And does every current team member have the same?
Run that check and you find the workarounds that never got raised. You find the quiet friction that your best people absorbed so smoothly that it never made it into a ticket, a 1:1, or a team review. You find the 18-month Slack ping habit that looked, from every available angle, like a perfectly functioning process.
The access gap is usually fixable in an afternoon. The harder part is accepting that the process which looked fine was never actually audited at all. Not by the person who built it, not by the manager who inherited it, and not by the agent who ran it every day without complaint.
If this sounds familiar in your own team, get in touch. A fresh look at your onboarding checklist is usually the fastest way to find out what you have been compensating for without knowing it.
Comments