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.

226 K. Nobeoka<br />

tion. Eng<strong>in</strong>eers can tra<strong>in</strong> on the job for the time when they will be promoted to a<br />

manager, because they can now obta<strong>in</strong> knowledge <strong>of</strong> a broad scope <strong>of</strong> component<br />

eng<strong>in</strong>eer<strong>in</strong>g. Eng<strong>in</strong>eers can now also obta<strong>in</strong> more sense <strong>of</strong> achievement regard<strong>in</strong>g<br />

specific vehicle projects. This seems to have positively affected the level <strong>of</strong> eng<strong>in</strong>eers'<br />

commitment <strong>and</strong> job satisfaction.<br />

Because each functional manager is responsible for fewer vehicle projects than<br />

before, it has become easier for a chief eng<strong>in</strong>eer to communicate frequently with<br />

functional managers. There used to be regular meet<strong>in</strong>gs among a chief eng<strong>in</strong>eer<br />

<strong>and</strong> the entire functional managers only about once every two months. Now, chief<br />

eng<strong>in</strong>eers <strong>and</strong> the six functional managers, as well as the center head, have weekly<br />

meet<strong>in</strong>gs, called the Center <strong>Management</strong> Meet<strong>in</strong>g.<br />

The <strong>in</strong>troduction <strong>of</strong> the center heads also greatly contributed to the improvement<br />

<strong>of</strong> project <strong>in</strong>tegrity. Chief eng<strong>in</strong>eers both <strong>in</strong> the old <strong>and</strong> the new organizations<br />

have not assumed formal authority over functional managers. On the other<br />

h<strong>and</strong>, center heads oversee all product development projects, <strong>in</strong>clud<strong>in</strong>g the work<br />

<strong>of</strong> functional managers. The center heads can work directly on <strong>in</strong>tegrat<strong>in</strong>g different<br />

eng<strong>in</strong>eer<strong>in</strong>g functions. Us<strong>in</strong>g this position, they also support chief eng<strong>in</strong>eers to<br />

coord<strong>in</strong>ate different functions. For example, when a chief eng<strong>in</strong>eer encounters difficulty<br />

<strong>in</strong> negotiat<strong>in</strong>g with a strong functional manager, he can discuss the issue <strong>in</strong><br />

the Center <strong>Management</strong> Meet<strong>in</strong>g, <strong>and</strong> the center head may support the chief eng<strong>in</strong>eer.<br />

Decisions made as a center can be smoothly <strong>and</strong> quickly implemented. In<br />

this sense, through the comb<strong>in</strong>ation with the center head, chief eng<strong>in</strong>eers rega<strong>in</strong>ed<br />

the strong authority that the orig<strong>in</strong>al Shusas used to enjoy.<br />

Table 1. Outcomes <strong>of</strong> the reorganization to the center<br />

Performance change Major factors<br />

Development cost<br />

-30% • Reduction <strong>of</strong> prototypes<br />

(average project)<br />

• Increase <strong>in</strong> component shar<strong>in</strong>g<br />

Number <strong>of</strong> proto-<br />

• Intensive coord<strong>in</strong>ation between diftypes<br />

-40%<br />

ferent eng<strong>in</strong>eer<strong>in</strong>g <strong>and</strong> test<strong>in</strong>g func-<br />

(average project)<br />

tions<br />

• Increase <strong>in</strong> CAE usage<br />

Lead time<br />

Shortened by a few • Reduction <strong>of</strong> prototypes<br />

(average project)<br />

months • More extensive simultaneous eng<strong>in</strong>eer<strong>in</strong>g<br />

Source: Based on "Activities <strong>and</strong> Achievements <strong>of</strong> FP21", Toyota <strong>in</strong>ternal document, 1994<br />

Table 1 summarizes achievements on some important measurements. The new<br />

organization helped reduce development costs on the average project by 30 percent.<br />

The number <strong>of</strong> test<strong>in</strong>g prototypes used <strong>in</strong> an average product development<br />

project decreased by 40 percent. This reduction <strong>of</strong> prototypes was a primary<br />

source for the reduction <strong>in</strong> development costs. The reduction <strong>of</strong> the number <strong>of</strong><br />

test<strong>in</strong>g prototypes has reflected the effective communication <strong>in</strong> the organization.<br />

In order to test many different items <strong>in</strong> one prototype, an <strong>in</strong>tensive coord<strong>in</strong>ation<br />

among different design divisions <strong>and</strong> test<strong>in</strong>g divisions is needed. For example,<br />

without appropriate communication, it is difficult to <strong>in</strong>stall the test<strong>in</strong>g items for <strong>in</strong>-

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

Saved successfully!

Ooh no, something went wrong!