Withdrawal of Team Autonomy During Concurrent Engineering
Team autonomy is an essential characteristic of cross-functional teams engaged in concurrent engineering. At the same time it is a characteristic that North American firms have considerable difficulty in successfully implementing. Delegating a good deal of decision making to teams is often counteracted by processes that during a new product program withdraw some of a team's autonomy or discretion. Data from 53 cross-functional product development teams in 14 firms indicated that withdrawing autonomy is negatively correlated with both task and process aspects of team performance. The determinants of withdrawing discretion include lack of a shared understanding of the development process, environmental change, and lack of managerial "buy-in" to team autonomy. Consequently, successful implementation of team autonomy, through mitigating withdrawal of discretion, requires a clear well-communicated model of the development process, a freezing of design revisions, and policies that encourage managers to support the team rather than interfere in its decision making.
Volume (Year): 43 (1997)
Issue (Month): 9 (September)
|Contact details of provider:|| Postal: 7240 Parkway Drive, Suite 300, Hanover, MD 21076 USA|
Web page: http://www.informs.org/
More information through EDIRC
When requesting a correction, please mention this item's handle: RePEc:inm:ormnsc:v:43:y:1997:i:9:p:1275-1287. See general information about how to correct material in RePEc.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: (Mirko Janc)
If references are entirely missing, you can add them using this form.