Normal view MARC view

Are your engineers talking to one another when they should?

Author: Sosa, Manuel E. ; Eppinger, Steven D. ; Rowles, Craig M.INSEAD Area: Technology and Operations ManagementIn: Harvard Business Review, vol. 85, no. 11, November 2007 Language: EnglishDescription: p. 133-142.Type of document: INSEAD ArticleNote: Please ask us for this itemAbstract: Companies that design complex products all have their horror stories. Yet they can all avoid mistakes by ensuring that the different teams responsible for developing the components of the product communicate more effectively. A new application of an established project management tool, the design structure matrix, can help a company not only identify where failures in planned communications could occur (usually bad), but also recognise when project teams engage in technical communications that were not planned (usually good). If a company finds that a lot of planned communication is not taking place, then it should revisit its product development organisation. Even projects that are completely organised around a product's architecture are typically vulnerable to communication breakdowns. A company can ensure that critical communication occurs by tasking special teams (or the teams involved) with making sure that the right people talk to one another. It's also important to ensure that the teams are working with the optimum communication tools.
Tags: No tags from this library for this title. Log in to add tags.
Item type Current location Call number Status Date due Barcode Item holds
INSEAD Article Europe Campus
Available
Total holds: 0

Ask Qualtrics

Companies that design complex products all have their horror stories. Yet they can all avoid mistakes by ensuring that the different teams responsible for developing the components of the product communicate more effectively. A new application of an established project management tool, the design structure matrix, can help a company not only identify where failures in planned communications could occur (usually bad), but also recognise when project teams engage in technical communications that were not planned (usually good). If a company finds that a lot of planned communication is not taking place, then it should revisit its product development organisation. Even projects that are completely organised around a product's architecture are typically vulnerable to communication breakdowns. A company can ensure that critical communication occurs by tasking special teams (or the teams involved) with making sure that the right people talk to one another. It's also important to ensure that the teams are working with the optimum communication tools.

There are no comments for this item.

Log in to your account to post a comment.
Koha 18.11 - INSEAD Catalogue
Home | Contact Us | What's Koha?