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 protectionist culture, the PM might spend the weekend scrambling to find an excuse, or worse, “massaging” the data to keep the status green. They’re protecting themselves, not the project.
In a transparent culture, they flag the issue early, not because they want to "rock the boat" but because they know that in this team, we reward the bad news early over the perfect lie late. It’s about creating an environment where people feel safe to own their mistakes and solve problems proactively, not hide them until it’s too late.
At scale, when the pressure is on, if your team’s instinct is self-preservation, no amount of process will save your delivery schedules.
When you’re juggling 20+ programs, collaboration is often the first casualty. It’s human nature that under pressure, PMs become territorial. They start hoarding engineers, hiding testing capacity, and fighting for priority.
If you tolerate this “every program for itself” mindset, you’re already in trouble. The enemy is silence, the failure to communicate and collaborate across programs, which inevitably leads to bottlenecks and inefficiencies.
My job as a leader isn’t to play referee in these resource fights. It’s to create a culture where PMs see each other as allies, not competitors. We prioritize based on the strategic value to the organization, not on who’s most afraid of their customer. When PM leads start sharing resources, swapping insights, and solving problems together, that’s when you’ve reached a true scale.
The real test of this philosophy came when I was tasked with integrating a group of PMs from a Japanese OEM into my team.
They came from a very different world, one where hierarchy and extreme risk aversion ruled. In their legacy culture, escalating a problem was seen as a personal failure. For the first few months, the friction was palpable. They were cautious, reserved, and, to be honest, a bit terrified of our level of transparency.
I didn’t hand them a new process manual. Instead, I sat in their syncs, observing. When the first hint of a risk came up, I made sure to coach them through it, leading by example. I showed them that “failing forward” was a requirement, not a punishment. By being transparent and showing that we could handle the truth, the team started to shift.
It took time, months, actually, but eventually, the lightbulb went on. The team realized that when you stop hiding the mess, you get more hands to help you clean it up. They didn’t just adopt the process; they became the strongest advocates for the culture we built. They were happier, more confident, and, importantly, they owned the culture, not just the process.
As a leader, you get the behavior you tolerate, not just the one you reward.
If you “celebrate” the PM who hits a milestone but leaves a trail of burnt-out engineers and hidden technical debt, you are building a toxic culture.
If you allow late escalations because “they eventually fixed it,” you are telling your team that transparency doesn’t matter.
This is where I firmly believe in mentorship through example. You pull people toward a standard by showing them what it looks like. When your PMs see you admit your mistakes, prioritize the team over your ego, and lean into transparency, they begin to build the muscle memory to do the same. It’s less about micromanaging and more about creating an environment where people know exactly how to act in every situation, because they’ve seen you act the same way.
Here’s the bottom line, Process gets you through the audit. Culture gets you through the launch and win for you the next program.
Don’t obsess over the perfect workflow. Don’t chase the ideal set of rules that will “fix” everything. Focus on the instincts of your leads, the behaviors you reward, and the culture you foster. When the culture is the "silent architecture" in the room, you don’t need to micromanage. The team knows how to win.
The breakthrough happens when your people live the culture, and the process becomes a natural extension of that, of you. That’s when you know you’ve truly scaled.
#AutomotiveLeadership #ProjectManagement #ScalingLeadership #CultureOverProcess #ADAS #FailingForward #TransparentLeadership #EngineeringManagement #OEM #Mentorship
Comments
Post a Comment