Leadership - Scaling Engineering Team From 3 to 40

  No scaling story is clean. If you are managing 30 or 40 programs, you are statistically guaranteed to face a crisis. Programs fail. Customers escalate. Deadlines, even the "sacred" ones, are missed. On the good days, leadership is about strategy and vision. But on the bad days, leadership is about thermodynamics . It’s about how you handle the heat. In the moments when a program is crashing, your leadership is visible in a way that no dashboard or success story can ever reveal. The question isn't whether you’ll face a failure, but who you become when you do. When a Tier-1 or an OEM customer is on the phone demanding answers for a missed milestone, the natural human instinct is to pass that pressure down. We want to find who is responsible. We want to demand immediate fixes. We want to "fix" the discomfort we feel by making the team feel it even more. But panic is a contagion. If you react with blame or withdrawal, you aren't solving the problem, you are pa...

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...

Project management looks clean on paper. Gantt charts, milestones, KPIs, risk matrices. Automotive project management looks similar, until you actually do one. In general terms, project management skills are well known, scope definition, planning, communication, risk management, stakeholder alignment, and execution discipline. These are universal and transferable across industries. Enough pages where written about that to circle the earth. Automotive project management si similar, but it doesn’t forgive shallow understanding and it amplifies every weakness. Automotive projects live at the intersection of hardware, software, regulation, and long-term liability . A delay is not just a delay, it can mean missing a model year. A design flaw isn’t a patch, it’s a millions of US Dollars recall. Decisions made early echo for a decade. What does that mean for a project manager? First, process literacy is non-negotiable . ASPICE, ISO 26262, PPAP, SOTIF, these aren’t buzzwords. They shape ho...