Stop Leading from the Passenger Seat: Why Leadership Skills Are Not Just for Managers
By Noor — Your career isn't happening to you. You're happening to it. ·
Look, we need to have a serious conversation about the word 'leadership.'
When I was recruiting at Google, I’d see it on every resume. 'Led a team of five.' 'Led the migration to cloud.' Half the time, the candidate was just a project manager who got lucky, and the other half, they were someone who actually steered the ship but didn’t know how to articulate it.
Here is the truth you won't hear in a corporate workshop: Leadership isn't a title you get handed when you hit five years of tenure or get that 'Manager' prefix on your Slack profile. Leadership is a set of technical skills you apply regardless of your rank. If you think you’re waiting for a promotion to start 'leading,' you’re already behind. You’re sitting in the passenger seat watching your career drive off a cliff, and I’m here to tell you to grab the wheel.
Stop Confusing 'Management' with 'Leadership'
Management is about process. It’s about Jira tickets, 1:1 cadences, and making sure the budget doesn’t blow up. It’s necessary, but it’s not what gets you the big moves or the high-level leverage.
Leadership is about influence without authority. It’s the ability to get people to move in a direction they wouldn’t have taken on their own, without you having to cite your job description. Back in Detroit, I saw guys running auto plants who had zero formal power but commanded every room they walked into. That’s the energy you need in tech. If you can move the needle on a cross-functional project when you don’t have direct reports, that’s when you become indispensable.
The Three Technical Pillars of Influence
I treat leadership like a coding language. You have to learn the syntax, practice the drills, and debug your approach. Here are the three pillars I coach my clients on:
1. Radical Clarity (The 'So What?' Test)
Most people communicate in fluff. They send long emails explaining 'why' something is hard. Leaders communicate in outcomes. When you’re proposing a shift in strategy, don’t lead with the technical debt. Lead with the business impact. If you can’t summarize your initiative in three sentences that make a VP’s life easier, you aren’t leading—you’re just complaining with extra steps.
2. High-Stakes Conflict Resolution
If you’re avoiding friction, you’re avoiding leadership. I’ve seen so many engineers let a 'bad' architecture decision go through because they didn’t want to be the person to speak up. That’s not being a team player; that’s being a bystander. A leader identifies the friction, names the risk, and proposes the fix. The 'blunt' part of my personality? It’s actually a leadership tool. People respect the person who says, 'This isn’t going to work, and here is why,' because they value their own time.
3. The 'Force Multiplier' Mindset
Ask yourself this: Does your team get better when you’re in the room? Do you provide the documentation, the context, and the air cover that allows your peers to do their best work? If you’re hoarding information to keep your status high, you’re dead in the water. Real leaders build systems that make everyone around them 20% faster. That is the definition of leverage.
How to Build 'Leadership' Without the Title
If you’re currently an IC (Individual Contributor) and you’re waiting for your performance review to start acting like a leader, stop. Do this instead:
- Volunteer for the 'Messy' Projects: Everyone wants the new feature launch. Nobody wants the migration that’s been delayed for six months because the documentation is a disaster. Be the person who takes the messy project and creates a roadmap. That is leadership in action.
- Audit Your Meetings: Stop attending meetings to 'listen.' Start attending to facilitate. If a meeting is drifting, be the one to say, 'We have 10 minutes left, let’s agree on the next two action items.' You just saved 20 minutes of five people’s time. That’s a leadership win.
- Own the 'Bad' News: If you see a deadline slipping, communicate it early. Don’t wait for your manager to find out. A leader proactively manages expectations before they turn into fires.
The Detroit Reality Check
I miss Detroit sometimes. The grit there is real. You don’t get a pass for 'meaning well'—you get a pass for 'getting it done.' Bring that same energy to your tech career. Don’t wait for someone to tell you you’re ready to lead. If you have the vision, the communication skills to back it up, and the audacity to solve problems that aren't technically 'yours,' you’re already a leader.
Your career isn’t happening to you—you’re happening to it. So, what are you going to lead this week? If you’re struggling to figure out how to project this authority without feeling like an imposter, let’s talk. Hit me up in the DMs or book a strategy session. Let’s get to work.