You are not currently logged in.
Access your personal account or get JSTOR access through your library or other institution:
If You Use a Screen ReaderThis content is available through Read Online (Free) program, which relies on page scans. Since scans are not currently available to screen readers, please contact JSTOR User Support for access. We'll provide a PDF copy for your screen reader.
Considering Risk in Product Development
David G. Hoopes
Vol. 3, No. 2 (2001), pp. 7-15
Published by: Palgrave Macmillan Journals
Stable URL: http://www.jstor.org/stable/3867900
Page Count: 9
Since scans are not currently available to screen readers, please contact JSTOR User Support for access. We'll provide a PDF copy for your screen reader.
Preview not available
Managers and scholars emphasize the importance of product development capabilities to a firm's performance. Research on product development emphasizes the importance of interdepartmental integration in the form of project management and task teams. Use of these integrating mechanisms leads to increased shared knowledge across departments. Yet there are risks and costs in devoting time and resources to inter-departmental integration, which comes at the cost of departmental specialization. Functional departments like marketing or product engineering presumably exist so that members can specialize in a specific domain of knowledge. Thus, insufficient shared knowledge of other groups' technical constraints can lead to costly problems. However, an over-reliance on integrating mechanisms to share knowledge can prevent departments from completing their own tasks. This paper details the implicit risks in devoting too little or too much time to cross-departmental integration. It is believed that understanding the risks and opportunity costs of using integrating mechanisms will aid in their application.
Risk Management © 2001 Palgrave Macmillan Journals