← Writings
Culture

Building Pride in a Support Role: Invest in the People Doing the Work

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. Watching it from the outside, the failure was obvious — and it was preventable. The role had never been framed as something worth investing in, so no one invested in the people doing it.

When I became a manager, that was the thing I was most determined not to repeat.

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.

Change the Language

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.

Change the language, and you start to change the culture.

It starts with the small things. Even how you ask matters: "Can you do this?" versus "Can you please help with this?"

Less command. More intent.

That shift seems small, but over time it changes how people engage with the work and with each other. 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, catching contract renewals before price increases hit and flagging them to finance, 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.

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.

Trust Them to Finish the Work

Early on as a manager, I found a lot of routine work wrapped in approvals that didn't need to be there. An analyst would have the fix ready and then wait — for a sign-off that added time and nothing else.

I knew exactly what that felt like. I'd been stopped in the afternoon myself — work ready to go, blocked because the approver was a few time zones away and already done for the day. I didn't like it, and I didn't want my team living with it. So I cut the bloat. Unnecessary approvals came out. The ones that mattered stayed: purchases still go through approval, because spending money should.

The difference showed up in the work. Tickets closed faster because nobody was waiting on someone else's permission. Users were happier because their problems got solved without the extra overhead. And analysts could finish what they started.

That last part matters more than it sounds. Every unnecessary approval tells someone, "We don't trust you to make this call." Remove it, and you're telling them the opposite. People take pride in work they're trusted to own — and they can't own work they're never allowed to finish.

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.

Pride isn't assigned. It's earned through ownership, clarity, and purpose.

Service means to serve — and that starts with the people doing the work.

Nobody invested in that analyst. Invest in yours.

←swipe→