14.11.2012 Views

Management of Technology and Innovation in Japan

Management of Technology and Innovation in Japan

Management of Technology and Innovation in Japan

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

212 K. Nobeoka<br />

launched an <strong>in</strong>itiative, called the Future Project 21 (FP21), to study any problems<br />

<strong>in</strong> its product development organizational structure <strong>and</strong> processes. The leader <strong>of</strong><br />

the project was Yoshiro K<strong>in</strong>bara, an executive vice president <strong>in</strong> charge <strong>of</strong> product<br />

<strong>and</strong> technology development. A manager at Toyota expla<strong>in</strong>ed that no specific<br />

threats triggered this project. At that time, Toyota was actually do<strong>in</strong>g better than<br />

most <strong>of</strong> its competitors. People at Toyota, however, recognized that organizations<br />

sometimes needed to be reviewed <strong>and</strong> overhauled to cont<strong>in</strong>ue to be competitive <strong>in</strong><br />

a chang<strong>in</strong>g environment. This belief helped Toyota improve problem sens<strong>in</strong>g capabilities,<br />

while it was still relatively successful.<br />

Soon after the FP21 started its studies, the team identified two potential problems<br />

for the future. These problems led Toyota to conclude that it would need a<br />

major reorganization. First, there was an organizational problem. A primary po<strong>in</strong>t<br />

was that Toyota’s product development organization had become less efficient <strong>in</strong><br />

communication <strong>and</strong> had come to need more coord<strong>in</strong>ation tasks than before to<br />

manage new product development. Second, the competitive environment for the<br />

<strong>Japan</strong>ese automobile <strong>in</strong>dustry started chang<strong>in</strong>g drastically around 1990, which<br />

seemed to require Toyota to change its product development strategy <strong>and</strong> organization.<br />

The follow<strong>in</strong>g sections discuss these two problems <strong>in</strong> more detail.<br />

Organizational Problems<br />

Figure 1 shows Toyota's product development organization before its reorganization<br />

<strong>in</strong> 1992. There were as many as sixteen design eng<strong>in</strong>eer<strong>in</strong>g functional divisions,<br />

<strong>and</strong> each had a functional manager. There were about fifteen projects proceed<strong>in</strong>g<br />

concurrently, even though Figure 1, a simplified model, depicts only n<strong>in</strong>e<br />

projects. Each project had a chief eng<strong>in</strong>eer, who was located <strong>in</strong> the Product Plann<strong>in</strong>g<br />

Division under general managers.<br />

The product development organization was actually a huge matrix organization<br />

rather than a project-based organization. Chief eng<strong>in</strong>eers <strong>and</strong> general managers <strong>in</strong><br />

the Product Plann<strong>in</strong>g Division did not directly oversee the eng<strong>in</strong>eer<strong>in</strong>g divisions <strong>in</strong><br />

this organization structure. However, chief eng<strong>in</strong>eers at Toyota were supposed to<br />

have considerable authority over the entire product development process, <strong>in</strong>clud<strong>in</strong>g<br />

different eng<strong>in</strong>eer<strong>in</strong>g stages, manufactur<strong>in</strong>g, <strong>and</strong> product concept creation. Accord<strong>in</strong>g<br />

to the def<strong>in</strong>ition by Clark <strong>and</strong> Fujimoto (1991), chief eng<strong>in</strong>eers at Toyota<br />

were supposed to be typical examples <strong>of</strong> heavyweight product managers.<br />

However, the product development organization at Toyota had become much<br />

larger than before, <strong>and</strong> chief eng<strong>in</strong>eers started to f<strong>in</strong>d it difficult to control <strong>and</strong> <strong>in</strong>tegrate<br />

different functional divisions when develop<strong>in</strong>g a new product. As the<br />

number <strong>of</strong> product development projects <strong>in</strong>creased, the number <strong>of</strong> eng<strong>in</strong>eers also<br />

<strong>in</strong>creased. At the same time, the degree <strong>of</strong> specialization <strong>in</strong> the eng<strong>in</strong>eer<strong>in</strong>g divisions<br />

had become narrower, reflect<strong>in</strong>g the <strong>in</strong>creas<strong>in</strong>g number <strong>of</strong> different eng<strong>in</strong>eer<strong>in</strong>g<br />

divisions. As <strong>of</strong> December 1991, there were about 7000 people <strong>in</strong> the sixteen<br />

product development eng<strong>in</strong>eer<strong>in</strong>g divisions. They were work<strong>in</strong>g, on average,<br />

on fifteen concurrent projects. In addition, Toyota had a Research <strong>and</strong> Advanced

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!