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 how work is done and how success is measured. A PM who treats them as paperwork will eventually lose credibility with both engineering and the customer.
Second, stakeholder management is external and unforgiving. Automotive customers, OEMs like Audi, BMW, or Ford, don’t just buy a product. They audit you. They expect transparency, escalation discipline, and predictability. Trust is built slowly and lost instantly.
Third, change management is constant. Requirements evolve, regulations tighten, platforms shift. The PM’s role is not to stop change but to contain it. That means understanding technical impact well enough to translate it into timing, cost, and risk without panic.
Finally, decisions must be data-anchored. Gut feeling matters, but in automotive, every claim is challenged. A good PM learns to walk into meetings with facts, assumptions clearly labeled, and a fallback plan already prepared.
Automotive project management rewards those who respect complexity rather than fight it. It’s not about moving faster, it’s about moving correctly, under pressure, with no room for heroics.
Personally, I learned the real meaning of automotive project management when I was asked to take over the Ford program at Mobileye. This was not a routine customer transition. It was a rescue operation, requested directly by Mobileye’s CEO, Amnon Shashua.
At that point, there was virtually no trust from the OEM, and our past performance as a company justified it. From Ford’s perspective, the program was unstable and unreliable, repeated milestone misses, long-standing bugs, and performance issues that surfaced late and were fixed too close to field testing, if at all. With a fixed model year SOP approaching, anxiety on the OEM side was understandably high.
The situation was already beyond a technical problem. It was a credibility crisis.
The first thing I focused on had nothing to do with code, schedules, or features. I worked on creating full transparency, not optimistic reporting, but an environment where the real state of the program could be exposed and discussed openly. The goal was to create the conditions for recovery together, with one clear priority, protecting the model year SOP.
The second step was presence. I flew to Ford’s headquarters and sat down with the OEM teams and management. Together, we defined an agreed-upon reporting framework between the project teams, myself, and Ford’s management. We aligned on cadence, content, and escalation rules so there would be no surprises and no interpretation gaps.
Once that framework was in place, we jointly prioritized the issues, from no-go for production down to nice-to-have. This was not about lowering quality expectations, but about focusing effort where it directly impacted SOP readiness.
When I returned to Mobileye’s HQ, I had a clear execution plan and, just as importantly, a clear communication contract with the customer. That structure reduced stress on the OEM management side and allowed us to focus on delivery instead of damage control.
From that point forward, blockers were raised immediately. Development challenges and performance trade-offs were surfaced early and discussed at the technical level with the customer. In many cases, we found common ground, sometimes by resolving issues on Mobileye’s side, and sometimes by adjusting vehicle control behavior to handle edge cases or physical limitations that could not be eliminated entirely.
Rebuilding trust was a process. It took close to six months to restore confidence at Ford’s management level, and nearly a year before the relationship shifted fully, by then, I had earned a nickname that stuck: “the Wolf.”
That experience reinforced a lesson I carry into every automotive program: in this industry, project management is as much about trust and credibility under pressure as it is about execution.
#TheWolf #RescueOperation #CrisisManagement #TurnaroundStrategy #ExtremeOwnership #TransparencyMatters #AutomotivePM #ADAS #AutonomousVehicles #SOP #Mobileye #OEMRelations #Ford #Tier1 #AutomotiveEngineering #ProjectManagement #PMP #StakeholderAlignment #RiskMitigation #GanttChartReality #ExecutionExcellence #ProgramManagement #ASPICE #ISO26262 #FunctionalSafety #SOTIF #QualityEngineering #ProcessExcellence #Leadership #RebuildingTrust #Credibility #ProfessionalMentorship #StrategicAlignment #TechnicalLeadership
Comments
Post a Comment