You’re doing everything right. Closing tickets fast. Keeping systems running. Getting solid performance reviews. And somehow, the person who got promoted over you has fewer certifications, less experience, and started after you.

It stings. And the advice you get afterward is always the same vague nonsense: “just keep doing great work” or “your time will come.” Meanwhile, someone else is already sitting in the role you wanted.

Here’s what nobody told you: the people who get promoted aren’t waiting for a leadership title. They’re already leading. They just haven’t been given the business card yet.

The uncomfortable truth about IT career advancement is that doing your job well is the baseline. It gets you a “meets expectations” on your review and a 3% raise. It doesn’t get you promoted. What gets you promoted is demonstrating that you’re already operating at the next level before anyone asks you to.

The Promotion Paradox Nobody Talks About

There’s a weird catch-22 baked into most IT organizations. To get promoted into a leadership role, you need to show leadership skills. But to show leadership skills, you supposedly need to be in a leadership role.

So how does anyone ever get promoted?

They don’t wait. They start doing the work of the next role while still in their current one. Not all of it. Nobody expects you to run department strategy from a help desk seat. But the small, high-visibility behaviors that signal “this person is ready.”

Think about the last person who got promoted at your company. Odds are, they were already doing some version of the job before they got the title. They were the one people went to with questions. They ran the meeting when the manager was out. They wrote the runbook nobody asked them to write.

Hiring managers consistently say they promote people who’ve already proven they can handle the responsibility, not people they hope will grow into it.

What Leadership Actually Looks Like at Every Level

You don’t need to be a director to lead. Leadership at every IT level looks different, but it exists at every rung.

On Help Desk

At the help desk level, leadership isn’t about managing people. It’s about being the person who makes the team better. That means:

  • Writing documentation that actually gets used. If you’re solving the same problem for the third time and there’s no KB article, write one. Not because someone told you to, but because it’s the obvious thing to do. Good IT documentation saves everyone time and makes you the person who builds things, not just the person who fixes things.

  • Training new hires before anyone asks. When the new person starts and your manager is too busy to onboard them properly, step in. Walk them through the ticketing system. Show them the common gotchas. This is leadership.

  • Flagging patterns, not just tickets. Anyone can close a ticket. Fewer people notice that the same printer issue has come up 15 times this month and flag it as a systemic problem. That’s the difference between a technician and someone who thinks like an engineer.

If you’re still building your foundational skills, platforms like Shell Samurai let you sharpen your Linux and command-line abilities while developing the kind of troubleshooting instincts that set you apart from other help desk techs.

As a Sysadmin or Network Admin

At this level, leadership means owning outcomes, not just systems:

  • Proposing solutions, not just identifying problems. Saying “the backup system is unreliable” is a complaint. Saying “I’ve tested three backup solutions, here’s a comparison with costs and my recommendation” is leadership. That’s making leadership care about the things you care about.

  • Running blameless postmortems. When something breaks—and it will—be the person who organizes a blameless postmortem rather than pointing fingers. This requires real emotional maturity and it gets noticed.

  • Mentoring junior staff. You don’t need a title to be a mentor. If a junior admin keeps making the same mistake, pull them aside and help. Not in a condescending way. More like “here’s what tripped me up too.”

At the Senior or Lead Level

Here’s where leadership starts looking more strategic:

  • Representing your team in cross-functional meetings. Volunteer for the project kickoff with the dev team. Be the person who translates tech into business language.

  • Making decisions and owning the consequences. When there’s ambiguity—and there’s always ambiguity—make a call, communicate it clearly, and accept responsibility if it doesn’t pan out. Managers notice who makes decisions and who perpetually asks for direction.

  • Building consensus without authority. Getting three teams to agree on a migration timeline when none of them report to you? That’s harder than managing direct reports. And it’s one of the most valuable leadership skills in IT.

Five Behaviors That Signal “Promote This Person”

You probably already know the basics: show up on time, don’t cause drama, do quality work. Great. That qualifies you to keep your job. Here are the behaviors that qualify you for the next one.

1. You Document Everything (Especially the Hard Stuff)

This deserves its own section because it’s so underrated. The IT pro who writes down how they solved a complex problem—and puts it somewhere others can find it—is demonstrating several leadership qualities at once: communication, strategic thinking, and a team-first mindset.

Your manager doesn’t have time to track every clever fix you pull off. A brag document solves this, but sharing your knowledge through runbooks and KB articles solves it AND helps the team.

2. You Volunteer for the Unglamorous Work

Everyone wants to work on the shiny new cloud migration. Almost nobody volunteers to document the legacy system or inherit the mess the last admin left behind.

Guess who managers remember when promotions come up? Not the person who only wanted the cool projects. The person who did what needed doing without being asked.

A caveat: don’t volunteer for everything. That path leads to burnout and being taken advantage of. Be strategic. Pick the unglamorous work that has visibility—the cross-team migration nobody wants to coordinate, the vendor evaluation that affects the budget, the onboarding process that’s obviously broken.

3. You Manage Up Without Being Told

Managing up isn’t brown-nosing. It’s making your manager’s job easier by anticipating needs, providing context before they ask for it, and framing your work in business terms.

When your manager asks “how’s the server migration going?” the average response is “fine, on track.” The leadership response is “We’re 70% through. Hit a snag with the DNS cutover that delayed us two days, but I’ve already adjusted the timeline and looped in the networking team. Here’s the updated schedule.”

One response generates follow-up questions. The other generates confidence.

4. You Give Credit Generously

Here’s a counterintuitive one: leaders give credit away constantly. When your team does something well, name specific people. “Sarah figured out the root cause” or “Mike’s script saved us four hours on this.”

This feels risky. Won’t it make you invisible? No. It makes you the person who builds other people up. Managers see this. Peers remember it. When your promotion comes up, these are the people advocating for you.

5. You Have Hard Conversations

Someone’s not pulling their weight. A process is broken. A vendor is underperforming. The average IT pro grumbles about it privately. The leader addresses it.

You don’t need authority to say the hard thing. You need tact. “Hey, I’ve noticed the backup verification step keeps getting skipped. Can we talk about why and figure out a better process?” That’s not confrontational. It’s constructive. And it’s something most people avoid, which is exactly why it stands out.

How to Lead a Project Without a Title

One of the best ways to demonstrate leadership is to lead a project. But here’s the thing—you don’t need to be assigned as the project lead to lead it.

Find the Gap

Every IT department has projects that should exist but don’t. Maybe the disaster recovery plan hasn’t been tested in two years. Maybe the onboarding process for new hires involves 47 manual steps that could be automated. Maybe nobody’s evaluated whether your monitoring tools actually catch the problems that page people at 3 AM.

These aren’t assigned projects. They’re leadership opportunities disguised as gaps.

Start Small and Visible

Don’t propose a six-month infrastructure overhaul as your first unofficial project. Start with something you can deliver in a few weeks:

  • Audit the current backup verification process and propose improvements
  • Create a shared dashboard showing key infrastructure metrics
  • Build a standardized troubleshooting guide for the five most common escalations
  • Set up automated alerts for the issues that keep surprising your team

Get Buy-In Before Executing

Here’s where amateur leaders screw up: they just start doing things without telling anyone. Then they’re surprised when nobody cares about their finished product.

Before you start, tell your manager what you want to do and why. Frame it around business value, not your personal interest. “I want to build a dashboard” is weak. “We’ve had three incidents this quarter where we didn’t catch the problem until users reported it. I want to build a monitoring dashboard that gives us early warnings. Should take about two weeks of spare cycles.” That gets a yes.

Present the Results

When you finish, don’t just quietly deploy it and hope someone notices. Present it. Send a summary to your team. If it saved time or prevented outages, quantify it. “This dashboard caught a disk space issue 4 hours before it would have caused downtime” is the kind of thing that shows up in performance reviews.

The Mistakes That Kill Your Leadership Credibility

Trying to lead without a title can backfire spectacularly if you do it wrong. Here are the mistakes that’ll make people resent you instead of respect you.

Overstepping Into Someone Else’s Territory

There’s a line between “helpful initiative” and “stepping on toes.” If another admin owns the firewall and you start making recommendations about firewall policy without being asked, you’re crossing it. Lead in the spaces where there’s a vacuum, not where someone else is already doing the work.

All Talk, No Execution

Some people love to point out problems and propose grand solutions but never actually do the work. If you’re going to identify a gap, be prepared to fill it. Otherwise you’re just creating work for other people, and they’ll notice.

Refusing to Do Your Actual Job

This is the biggest trap. You get so focused on “leadership behaviors” that your ticket queue backs up, your response times slip, and your day-to-day work suffers. Leadership extras are in addition to your core responsibilities, not a replacement for them.

Nobody promotes the person whose queue is a disaster, regardless of how many side projects they launched. Handle your workload first. Then lead.

Taking Credit for Team Efforts

We already covered giving credit generously. The opposite, taking credit for collaborative work, is career poison. Get caught doing it once and your leadership credibility evaporates. In the age of shared Slack channels and transparent ticketing systems, it’s also really easy to get caught.

Being the Self-Appointed Expert

There’s a difference between being helpful and being the person who constantly corrects others or inserts themselves into every conversation. If your default response to a teammate’s approach is “well actually, you should do it this way,” you’re not leading. You’re annoying.

Building Your Case for the Actual Promotion

At some point, you need to convert these leadership behaviors into an actual promotion. That doesn’t happen by accident.

Keep a Running Record

Your brag document should capture the impact, not the task. “Wrote backup runbook” tells your manager nothing. “Wrote backup runbook that reduced onboarding time for new admins from 3 weeks to 1 week” gets their attention. Track every project you led, every problem you solved proactively, every time someone came to you for guidance.

Have the Conversation Early

Don’t wait for your annual performance review to express interest in advancement. Tell your manager directly: “I’m interested in moving into a senior/lead/management role. What do you need to see from me to make that happen?”

This does two things. First, it puts your manager on notice that you’re serious. Second, it gives you specific criteria to work toward. If they say “I need to see you lead a cross-team project,” now you know exactly what to do.

Know When the Promotion Isn’t Coming

Sometimes the honest answer is that there’s no room for growth where you are. The team is small. Your manager isn’t going anywhere. The company doesn’t have the role you want. If you’ve been demonstrating leadership for a year and the response is still “just keep doing what you’re doing,” it might be time for a lateral move or a new job.

This isn’t failure. It’s strategic. Every leadership behavior you’ve built is portable. Interviewers at your next company will see someone who leads naturally, and that’s worth more than any title on your current business card.

If you’re considering your options, make sure your resume reflects your leadership work and not just your technical responsibilities. And if you need to job search while still employed, do it carefully.

When Leadership Isn’t What You Actually Want

Full disclosure: not everyone should be chasing a leadership track. And that’s fine.

Some of the happiest, most respected IT pros are individual contributors who go deep instead of wide. They’re the person everyone consults for the hard technical problems. They don’t want to manage people or run meetings—they want to build and fix things.

If that’s you, stop feeling guilty about it. The industry needs both leaders and deep specialists. You might find your sweet spot going deep on cybersecurity or stacking certifications instead. But even as an IC, the behaviors we’ve discussed—documentation, communication, mentoring, initiative—still apply. You’re just applying them to technical influence rather than organizational authority.

The key is making a deliberate choice. Don’t drift into leadership because you feel like you’re supposed to. And don’t avoid it because it seems scary. Pick the path that aligns with how you actually want to spend your days—then go all in.

For more on navigating this decision, the IT generalist vs specialist question is worth thinking through.

The Bottom Line

Nobody is going to tap you on the shoulder and say “you’re ready to lead.” That’s not how IT careers work. The people who advance are the ones who start leading long before anyone gives them the title, the raise, or the corner office (or more realistically, the slightly larger monitor).

Start this week. Pick one thing from this article—one documentation project, one hard conversation, one gap you can fill—and do it. Not because someone asked you to. Because that’s what leaders do.

And if you’re still building your technical foundation, that’s fine. Leadership isn’t about being the most senior person in the room. It’s about making the room better because you’re in it.

FAQ

Can I demonstrate leadership on help desk?

Yes. Help desk is actually one of the best places to demonstrate leadership because expectations are lower. Writing documentation, training new hires, identifying recurring issues, and suggesting process improvements all show leadership initiative. The bar for “going above and beyond” is lower on the help desk than it is at the senior level, which means your efforts stand out more. Several IT directors started by distinguishing themselves at the help desk level.

What if my manager doesn’t notice my leadership behaviors?

Make sure you’re making your work visible. Send weekly updates. Share wins in team meetings. Keep a brag document and reference it during your performance reviews. If your manager still doesn’t notice after months of documented initiative, that tells you something about the organization—and it might be time to look elsewhere.

How do I lead without coming across as a know-it-all?

Focus on asking questions rather than giving answers. “What if we tried X?” lands better than “We should do X.” Share your reasoning openly and invite pushback. The worst leaders are the ones who can’t be wrong. The best ones make it safe for others to disagree. Also, pick your moments. You don’t need to lead in every meeting or weigh in on every decision. Strategic restraint is itself a leadership skill.

Should I tell my manager I’m trying to develop leadership skills?

Absolutely. Frame it as a career development conversation: “I’d like to grow into a leadership role over the next year or two. Are there specific projects or responsibilities I could take on to develop those skills?” This gives your manager context for the behaviors you’re demonstrating and makes them more likely to actively support your growth. It also prevents any misreading of your initiative as overstepping.

What if leadership behaviors aren’t rewarded at my company?

This happens more than people admit, especially at smaller companies or MSPs where the structure is flat and there’s nowhere to promote you into. If you’ve been demonstrating leadership for six months to a year with no recognition, document your accomplishments thoroughly and start applying elsewhere. The leadership skills you’ve built are highly transferable—interviewers notice candidates who can speak to specific examples of initiative and impact.