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.
Most of the world operates without much intention. Choose to lead differently.
Reframe the Mission
The service desk is the face of IT to every employee in the organization. For most people, it is IT. Every interaction either builds trust or erodes it. For many new employees, the service desk is their first experience with IT—make it count.
When analysts understand the impact of their work, not just the ticket count but the confidence they are building or undermining, they prioritize differently. Quality follows purpose.
That is when pride starts to become possible. People take the work more seriously when they understand the trust attached to it.
A ticket queue can become a dead end quickly. Go silent, and trust fades. Respond without clarity, and confidence drops. Leave no ticket unresponded to—follow up. Close tickets too quickly, and credibility can suffer.
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.
-
Assign every ticket at intake. Nothing should sit unowned. Ownership drives accountability, and unassigned work is where things fall through the cracks.
-
Reassess the queue regularly to confirm priorities and remove blockers. What was urgent yesterday may not be today. Staying aligned prevents wasted effort and missed expectations.
-
Prioritize intentionally, not reactively. Not every ticket carries the same impact—focus on what matters most, not just what’s next.
-
Update tickets consistently—if it’s not documented, it didn’t happen. Clear updates create visibility, reduce confusion, and build trust with both the team and the customer.
-
Silence erodes trust faster than delay. Respond early, even if you don’t have the answer yet. Acknowledgment shows ownership and keeps confidence intact.
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.
Recognize good work specifically—not just “great job,” but “the way you handled that escalation under pressure reflects the standard we’re building.” Take the time to connect—pick up the phone, turn on your camera, be personable. Elevate and encourage.
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 is what shows up when ownership, clarity, and purpose are all in place.
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.