Nissan used cross-functional teams to make its revival plan executable

When Renault took a stake in Nissan in 1999, Nissan had been late to respond to problems for years. Carlos Ghosn could have imposed a Renault playbook. The sharper move was to form cross-functional teams that cut across the very departments whose local optimizations had slowed decisions.

The mechanism was social as much as analytical. Purchasing, manufacturing, maintenance, engineering and sales people had to sit together, expose bottlenecks and accept tradeoffs that no single function could solve alone. Nissan later described that same cross-functional habit as critical in its 2011 disaster response.

By May 2002, Nissan said the Revival Plan's official commitments had been overachieved a year early: fiscal 2000 returned to profit, fiscal 2001 operating margin reached 7.9% versus a 4.5% target for fiscal 2002, and net automotive debt fell to 435 billion yen versus a 700 billion yen goal.

Let the silos design the anti-silo plan

The teams converted a diagnosis into shared ownership before the formal plan was announced.

Cross-functional work attacked the coordination failure, not just the visible cost base.

The same operating habit later helped Nissan allocate scarce parts across plants after the 2011 earthquake.

A turnaround plan lands harder when the people who must execute it first have to diagnose the whole system together.

Nissan treated cross-functional teams as a permanent management practice, not a one-off crisis ritual. The 2002 follow-on plan, Nissan 180, kept CFTs as one of the cornerstones of the Nissan Management Way while the company moved from survival to growth targets.