Early in my career, I watched a strong analyst leave a support team. He was capable, but he felt unsupported in ways that were entirely avoidable.
Work was assigned to him that didn’t match his expertise. Timelines were unreasonable. No one had taken the time to delegate thoughtfully—to understand what he could handle, what his workload allowed, what he needed to grow into, and where he needed support.
Instead, he was given work he had never been prepared to complete. He felt set up to fail.
That one stayed with me.
Because watching it from the outside, the failure was obvious—and I felt it. It was preventable.
The role had never been framed as something worth investing in—so no one invested in the people doing it.
When support work is treated as transactional, the people doing it start to feel disposable. Eventually, they act accordingly.
Support isn’t a transaction. It’s a service.
And service means to serve—not to take.
People don’t take pride in work they feel disconnected from. They take pride in work they feel responsible for.
When I became a manager, that was the thing I was most determined not to repeat.
The language we use around support work shapes how support teams see themselves. “Just the help desk.” “Ticket takers.” “Entry-level IT.” When the work is framed as transactional, people treat it that way.
When people care about what they do, they show up differently. They put in more effort. They take ownership. That is where pride starts, not from the work itself, but from how the work is treated.
Change the language, and you start to change the culture.
Do the small things well.
Even how you ask matters:
“Can you do this?” vs. “Can you please help with this?”
Less command. More intent. Be intentional.
That shift seems small, but over time it changes how people engage with the work and with each other. Being intentional tends to lower barriers. When you lead with a little more warmth and a little less command, people respond differently — they’re more willing to engage, more likely to ask questions, more open to feedback. That’s how trust gets built one interaction at a time.
Reframe the Mission
The service desk is the face of IT to every employee in the organization. For most people, it is IT. But what most people see is only the surface — the ticket, the reset, the fix. What they don't see is everything underneath.
When we're not on tickets we're improving backend tools, deploying new services, monitoring systems, switching platforms, and navigating a wide range of personalities across the organization. The visible work is a fraction of what actually keeps things running. Most of the organization doesn't know that — and that's partly on us for not making it visible.
My role grew naturally over time. I get done what I'm assigned — but managing isn't doing everything yourself. It's knowing where everything needs to go and making sure it gets there. The work that looks simple from the outside usually has ten invisible steps behind it. When your team understands that — when they see themselves as part of something bigger than the queue — they start to carry themselves differently.
That's where pride starts.
Every interaction either builds trust or erodes it. For many new employees the service desk is their first experience with IT — make it count. Customers don't want tickets closed. They want their problems solved — quickly, clearly, and professionally.
Practical Standards That Build Culture
Culture isn’t built through a single conversation. It’s built through consistent behavior—practiced daily until it becomes how the team operates by default.
Every ticket gets assigned at intake. Nothing sits unowned. Unassigned work is where things fall through the cracks — and when things fall through the cracks, trust falls with them. The queue gets reassessed regularly — what was urgent yesterday may not be today. Priorities shift and the team needs to shift with them. Not every ticket carries the same impact — focus on what matters most, not just what’s next.
Documentation isn’t optional. If it’s not in the ticket it didn’t happen. Clear updates create visibility, reduce confusion, and build confidence with the customer. And when you don’t have an answer yet — say something anyway. Silence erodes trust faster than delay. Acknowledge it, own it, keep moving.
Over time, these habits don’t just improve performance—they build pride in the work and in the team.
Pride Is a Leadership Outcome
You can't mandate pride. But you can create the conditions for it—and those conditions show up in how you lead every day.
Recognizing good work costs nothing. If something goes well I let them know directly — and I bring it up to someone above me when it deserves to be heard at that level. Public credit in the right room means more than a private message. Private credit still matters when public isn't the right setting. Both are free. Both land differently than silence.
Be humble enough to know that your team's wins aren't yours to keep. The manager who takes credit quietly is the manager whose team stops trying to impress them. The one who shares it openly is the one people want to work hard for.
That's the simplest version of pride as a leadership outcome — people doing good work because they know it will be seen, acknowledged, and passed up the chain by someone who actually means it.
Give your team context for why their work matters beyond the ticket count. Quality over quantity.
When analysts understand that their work shapes how the entire organization perceives IT, the job stops feeling like a queue to get through. It starts feeling like something worth doing well.
Pride isn't assigned. It's earned through ownership, clarity, and purpose.
Support isn't about getting through tickets. It's about stewarding trust at scale.