F1. Actual Product Specs Fail to Satisfy Customer

-Changes not communicated throughout the  development team
-Result of changes not tested in critical system areas
-Poor requirements scope or definition
-New requirement interpretations
-Poor VOC transfer from Marketing to Engineering


F2. Manufacturing Variance not Modeled

-Tolerance stack up causes failure
-Specs not manufacturable;  poor process capability
-Tight tolls too expensive


F3. PDP Steps are Skipped

-Some are not necessary for each project
-Lack of time or resources
-Some PDP steps are considered extra work
-Poor understanding  of certain PDP steps by development team


F4. Documentation/Compliance Not Complete

-Overall project decisions not completely documented
-Poor or no trace from critical parameters to voice inputs


F5. Engineers Don’t Use PDP

-Too hard to understand by typical engineers
-Considered a waste of time; no value add seen by development team
-Gets in the way during busy stages of development


F6. Advanced Tools Not Used or Integrated

-VOC, HOQ, Risk, CPM tools are used inconsistently since data is isolated.
-Tools not web accessible.
-Most tools not integrated into the PDP framework
-Isolated tools are not used by everyone: assigned to experts instead.


F7. PDP Template/Workflow Not Developed

-Engineers confusion means PDP abandonment and extra prototypes built

Cognition Cockpit mitigates the risks of failure during product development by addressing many of the critical product development failure modes faced by most companies. Following is a list of common ways to fail at product development:

Seven Common Program Failure Modes

Cockpit's Solutions To Mitigate These Failure Modes...

"Cognition Cockpit", "ECM", "Enterprise Cost Management", the Cockpit Logo, and Cognition graphics are all
copyright 2009 Cognition Corporation and are used here by permission | Terms of use | Privacy Policy