Skip to main content

Post 7 - Leading the Leaders: The Theory of Scaling Your Influence

 



At around 15–20 project managers, the ground shifts beneath your feet. You aren’t leading PMs anymore, you’re leading PM Leads. It’s a transition that catches even the most seasoned leaders off guard, mostly because the skills that got you here, technical precision and tactical oversight, suddenly become the very things that hold you back.

At this scale, your success isn’t measured by how well you manage tasks. It’s measured by how well you manage intent.


Context Over Instructions

Leadership in this space is about providing context, not giving orders. You’ll find yourself spending significantly more time explaining the "why" than the "what." You invest your energy in calibration: defining what "good" looks like, deciding where acceptable risk ends, and clarifying exactly when an issue needs to reach your desk.

This requires a new kind of discipline: the power of restraint. Not every mistake needs your correction. In fact, some mistakes must run their course. Real learning rarely happens when a boss steps in to save the day. Your goal is to build an environment where your leads are confident enough to make the call and bold enough to fail forward.


Trusted Autonomy

As your bench of PM leads grows, so does the complexity of their individual perspectives. Your job isn't to flatten those differences, but to align them toward a shared vision.

It starts with a shared language. What are the non-negotiables of your culture? Where is there room for creative interpretation? When you stop telling people what to do, you have to ensure they understand the principles deeply enough to make decisions independently. Trust them to lead their teams, but hold them accountable for those decisions.


Coaching Through Complexity

When you stop managing the "what," you start coaching the "how."

Your PM leads will inevitably encounter difficult situations, conflicting stakeholder priorities, technical constraints, or resource gaps. In these moments, your role is less about giving instructions and more about guiding the thought process.

Becoming a sounding board helps them come to their own conclusions. It’s about teaching them to think critically and prioritize effectively in high-pressure situations. You can’t always be there to make those calls for them.


To be honest, the theory is the easy part. Living it is much harder.

I remember my first major lead project. It was a German OEM, an ADAS project based on the Mobileye EyeQ3. Back then, that was the state of the art. I led it hands-on alongside two other PMs, and for me, the technical weekly status and planning meeting with the OEM and Tier-1 was sacred.

I took those meetings almost religiously. Even when I was sick, I’d join from my home phone. I remember that I was in Costa Rica, on a family trip, sitting on a chair, viewing Mount Arenal, joining this call. That meeting was my "weekly oxygen." We’d align on every detail of the past week and, more importantly, plan the next week in detail. I’d double and triple-check everything to ensure the team was perfectly aligned. With the complexity of the algorithms and system topics we were handling, I felt like I had to be on top of everything, to be the glue.

As I moved up the ranks, I naturally continued to join those meetings. But eventually, I realized I had a great PM lead who understood everything perfectly. They were doing the alignment and the double-checks just like I used to. I decided it was time to let go and trust them.

The following week, I felt like my oxygen was missing. I didn't know the status; I didn't have the plan for next week. At first, it felt awkward, even a bit frustrated, to get a 15-minute second-hand brief from my PMs after being used to a three-hour detailed deep dive.

Finally, I understood: they were doing a great job because they had picked up the process and embedded it into their culture. It was only me that needed to adopt a new role. It wasn't easy, but letting go opened me up to see the bigger picture. It allowed me to deep-dive only in those specific places where the team truly needed my assistance and advice.

Leadership at this scale is the long game. It’s about creating a team of leaders who can take the baton from you and continue to elevate the work, even when you aren't in the room.






#ManagingManagers #LeadershipGrowth #DelegationWithClarity #PMLeadership #Empowerment #StrategicGuidance #LeadershipEvolution #BuildingLeaders #TrustedAutonomy #TeamAlignment #CoachingThroughComplexity

Comments

Popular posts from this blog

Post 1 - Beyond the Roadmap: Where Logic Meets Leadership

  Hello, I’m Yair Han. I spent my days at the intersection of AI, automotive safety, and high-stakes program leadership. This blog is where I step back from the roadmaps to explore the philosophy and logic behind the technology and leadership. Pleased to e-meet you. With over 15 years of experience at the forefront of AI-driven mobility and safety-critical systems, I am a Senior Technical Leader dedicated to bridging the gap between complex engineering and global business success. My career is defined by navigating the high-stakes intersection of hardware, software, and automotive regulation, having led over 30 global production programs from initial proof-of-concept to mass market Start of Production (SOP). As a Senior Director at Mobileye, I have built and mentored multidisciplinary divisions of over 40 professionals, fostering a culture of execution excellence and radical transparency. I specialize in "rescue operations", restoring trust with global OEMs like Ford and Audi...

Post 8 - Culture Beats Process at Scale

By the time you’re leading 30 or 40 Project Managers, the "whiteboard phase" of leadership is over. You’ve got the dashboards. You’ve got standardized workflows. You’ve got review cycles. On paper, the machine is built. But here’s the reality,  The dashboard is a liar . I’ve seen it time and again, two teams using the exact same Jira workflows, similar goals, yet one hits every milestone, while the other is in total chaos. The difference isn't the tools. It’s the culture. Specifically, it’s what your people do when the playbook doesn’t cover the crisis . Culture isn’t a set of lofty values or a catchy vision statement. It’s a set of instincts, the ones that guide decision-making in the heat of the moment. It’s that critical choice a PM makes on a Thursday afternoon, 2 hours before a steering committee, and 4 hours before the weekend starts, when they realize a key deliverable is going to be delayed, or QA found a new bug in the version we just delivered. In a protectionis...