May 2019
Intermediate to advanced
296 pages
8h 7m
English
(Derived from The Toyota Product Development System: Integrating People, Process and Technology – James M. Morgan and Jeffrey K. Liker)
| No. | Principle | Description (from Morgan and Liker) | References in main body of book |
| Process | |||
| 1 | Establish customer‐defined value to distinguish value‐added activity from waste. | Waste takes the form of untimely or incorrect engineering information. | Ch. 4 – value proposition, satisfying a range of customer needs Ch. 6 – identifying customer needs Ch. 8 – validate against customer requirements Ch. 9 – product sign‐off |
| 2 | Front‐load the product development process when there is maximum opportunity to explore alternate solutions thoroughly. | Cross‐functional collaboration is needed early in the design process to make sure that later rework, due to poor decision‐making in the early stages, is prevented. | Ch. 2 – cost of problem resolution, early problem detection Ch. 3 – technology maturity concepts |
| 3 | Create a levelled product development process flow. | A value‐stream map should connect important milestones to decisions, information flow and critical meetings – key integrating events. | Ch. 5 – goal‐directed management, value‐stream mapping, managing, and monitoring projects Ch. 9 – planning and decision making, flow of information Ch. 11 – working collaboratively |
| 4 | Utilise rigorous standardisation to reduce variation, and create flexibility and predictable ... | ||