Almost every week, someone emails me directly instead of opening a support ticket.
They're not trying to cause problems. Usually, it's quite the opposite. They know who handles the request, figure going straight to me will be faster, and an email feels more personal than filling out a form. Or an instant message.
The same thing happens with software licenses. Someone submits a request directly through a vendor's website, and the notification eventually makes its way to me. There's no support ticket, no documented approval, and sometimes very little information about why the license is needed. The assumption is simple: I'll see it, respond, and add the license.
Most of these requests come from a good place. Almost every one of them makes operations a little more difficult.
I'll admit, I sometimes find myself grumbling about it. Not because I don't want to help, but because we have a process for a reason, and most people already know what it is. After years of working in IT, I've learned that there's a difference between getting something done and getting something done properly.
Why the Shortcut Hurts
A request sitting in my inbox is invisible to everyone but me. Nobody else on my team can see it, pick it up, or even know it exists. There's no reliable record of when it came in, what was requested, or whether the necessary approvals were obtained. If I'm out sick or on vacation, the request might sit there until I return. When someone asks what the service desk accomplished last month, that work may not appear anywhere in our reporting.
The ticket isn't bureaucracy. It's the record.
It's how work gets tracked, shared, measured, and audited. Without that record, the work might still get done, but the organization loses visibility into what happened.
Like any other department, we need to demonstrate what we're working on, where our time goes, and what we're accomplishing. We need to identify trends, justify resources, and show the value our team provides. When work happens outside the ticketing system, it doesn't stop consuming time.
We lose accountability. If it's not in the ticket, it didn't happen.
That's why I direct people back to the official request process. Not because I enjoy forcing someone to take an extra step, but because their request deserves to be tracked like everything else. While screenshots of conversations can provide useful context, they aren't always a substitute for an approval recorded by the person authorized to give it.
The ticket protects the requester, the service desk, and the organization. It also means that six months later, nobody has to rely on someone's memory to figure out what happened.
Not Every Step Is a Control
Now, here's the other side of the argument. I believe in processes, documentation, and accountability. But I've also seen processes grow well beyond the point where they're protecting anything. Just because something has an approval button doesn't make it a good control.
Every step in a process should be able to answer a few basic questions:
- What risk does this step reduce?
- Who uses the information it produces?
- What breaks if this step disappears tomorrow?
- Does the person approving it have the information and authority to make that decision?
If nobody can explain why a step exists, I think it's fair to question whether it still belongs in the process.
Sometimes the answer is straightforward. An approval might authorize spending, protect sensitive information, or ensure someone isn't receiving access they shouldn't have. Those are legitimate reasons. Other times, the answer is simply, "That's how we've always done it."
We've all encountered those processes. Approvals from people who can't meaningfully evaluate what they're approving. Documentation that nobody ever reads. Sign-offs that exist because someone solved a problem years ago, and the solution remained long after the problem disappeared.
That's how good intentions can create bad operations. Not overnight, but one seemingly reasonable step at a time.
When People Go Around You, Listen
When people attempt to bypass a process, I think managers should pay attention. It might be convenience, a misunderstanding of why the process exists, or an official process that really is more complicated than it needs to be. The challenge is figuring out which situation you're dealing with.
For example, I don't have a problem with someone sending me a Teams message asking about a software license. Maybe they want to know whether we already own it, what it costs, or whether there's an alternative. That's a conversation, and conversations are part of my job.
But when that conversation turns into an actual request to purchase software, assign a license, or grant access, it needs to enter the official workflow. The same applies when someone uses a vendor's built-in request feature. Just because a website allows an employee to request a license doesn't mean that request has gone through the organization's approval process. Technology makes it easy to ask for things. That doesn't make every method an authorized way to obtain them.
I can't stop every email, Teams message, or vendor notification from reaching me, nor would I necessarily want to. But I can make sure those requests are properly documented before the work is completed.
The communication method can be flexible. The accountability shouldn't be.
If everyone is finding ways around something, maybe it's worth asking why. Are we enforcing a necessary control, or are we defending an unnecessarily complicated workflow? Those are two very different things. I don't believe good management means blindly defending every process because you're responsible for it. Sometimes leadership means recognizing that a process needs to change.
The Gray Areas
Here's where reality gets a little uncomfortable. I'd love to tell you that every employee, regardless of position, follows the exact same steps every single time. I've been in IT long enough to know that's not how the real world works.
When a senior leader emails me directly, I'll often open the ticket on their behalf as a matter of customer service. Does that mean their request doesn't need to be documented? Absolutely not. Does it mean required approvals can be skipped? No.
I believe in fairness and consistency. If I'm asking someone in sales to follow a process, part of me believes everyone should. But management requires a little more flexibility than insisting every situation be handled identically. There's a difference between making someone's experience more convenient and removing the controls that protect the organization.
Priority should follow business impact, not titles. A routine request from an executive shouldn't outrank a critical outage affecting an entire department — but business realities do matter, and ignoring them doesn't make us better managers.
The challenge is finding the balance, and I don't always enjoy the compromises. But I try to keep the important parts consistent: documentation, authorization, accountability, and visibility. How we get there can sometimes look a little different.
The Point of the Process
Processes are never going to be perfect. People will take shortcuts. Managers will make exceptions. Technology will introduce new ways for employees to request things outside the established workflow. And sometimes the process itself will be the problem. That's part of running an operation.
But the small things still matter. A ticket that gets created. An approval that gets documented. A request that another team member can pick up when I'm unavailable. Visibility that lets management see what's going on. A record in the finance system that can explain why money was spent or access was granted.
None of those things are particularly exciting. Nobody is going to throw a party because a software license has the proper approval attached to its support ticket. But those small things are what allow an organization to operate consistently. They help managers understand workloads, identify problems, plan resources, and demonstrate the value their teams provide. More importantly, they make sure the organization doesn't depend entirely on one person remembering what happened.
That's what good processes are supposed to accomplish. Not to make everyone's job harder, create unnecessary approvals, or give managers another opportunity to say no. They're supposed to make work more predictable, visible, and accountable.
Be flexible with how the work gets started. Be consistent with how it's documented and completed.
Good intentions start the work. Good operations finish it.