Leadership - Scaling Engineering Team From 3 to 40

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

  Scaling from three project managers to ten changes everything. Suddenly, you can’t attend every meeting. You have more than one or two OEMs to serve, often across several different programs, some legacy, some the next production production, some at the POC stage. You don’t see every email. You start hearing about problems second-hand, and that is deeply uncomfortable. Up to this point, visibility was total. You knew the customer mood. You knew the weak spots. You knew when something felt off before it showed up in a report. Scaling breaks that illusion immediately. Many people fail at this stage because they cling to control. They jump back into details, override decisions, and reinsert themselves into conversations that no longer require them. The message sent is rarely intentional, but it is received clearly: trust is conditional. The outcome is predictable. The team stops owning outcomes. Decisions are delayed. Escalations increase. People start managing upward instead of m...

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