Front-loading problem-solving: implications for development performance and capability

Summary form only given. Some practitioners have initiated concentrated efforts to reengineer their development processes as to move (or "load") their problem identification and solution backwards in time (to the "front" of the process). In this paper, we provide a conceptual model and some case evidence from development practice to describe the basic principle behind this rapidly emerging concept. We base our discussion on a problem solving perspective of product development. We describe and analyze a product development project as a bundle of inter-dependent problem-solving cycles that include modeling and testing via computers or physical prototypes as core activities. Using this perspective, we propose that the earlier identification and solving of a set of problems for a given developmental task can lead to faster and more efficient product development. Our evidence is mostly case-based but we feel it points towards the emergence of an important capability for improving development practice. The paper addresses the following issues: we start with a brief discussion of the benefits and potential risks of shortening product development. We then describe the problem-solving perspective of product development and apply it to automotive development. The next sections explain the basic principle of front-loading which is followed by a field study of front-loading at Toyota Motor Corporation. We conclude the paper with implications for managerial practice and research.

[1]  Steven D. Eppinger,et al.  A Model-Based Framework to Overlap Product Development Activities , 1997 .

[2]  Michael Burda,et al.  Revolutionizing product development , 1993 .

[3]  Stefan H. Thomke,et al.  The Effect of 'Front-Loading' Problem-Solving on Product Development Performance , 2000 .

[4]  T. Hout,et al.  Competing Against Time , 1990 .

[5]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[6]  K. Clark,et al.  Strategies for Managing a Project Portfolio , 1993 .

[7]  T. J. Allen Studies of the Problem-Solving Process in Engineering , 1966 .

[8]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[9]  Eric von Hippel,et al.  How learning by doing is done: problem identification in novel process equipment☆ , 1995 .

[10]  Stefan H. Thomke,et al.  Simulation, learning and R&D performance: Evidence from automotive development , 1998 .

[11]  Stefan H. Thomke,et al.  Managing Experimentation in the Design of New Products , 1998 .

[12]  D. L. Marples,et al.  THE DECISIONS OF ENGINEERING DESIGN , 1961, IRE Transactions on Engineering Management.

[13]  Michael A. Cusumano,et al.  Thinking Beyond Lean: How Multi Project Management is Transforming Product Development at Toyota and Other Companies , 1998 .

[14]  K. Clark,et al.  Lead time in automobile product development explaining the Japanese advantage , 1989 .

[15]  Christoph H. Loch,et al.  Measuring the Effectiveness of Overlapping Development Activities , 1999 .

[16]  Yaichi Aoshima,et al.  Knowledge transfer across generations : the impact on product development performance in the automobile industry , 1996 .

[17]  Arnoud Cyriel Leo,et al.  Tech Talk: How managers are stimulating global R&D communication , 1991 .