Click to enlarge

As we've illustrated, a product design review is basically a 'walkthrough' of the PDS to examine the product design with an eye to criticism and correction of the value of features, benefits, uses, functions and proposed processes described in the PDS.

But, before doing the walk-through, it's important to plan the session carefully and determine exactly what its outcome should be and what the stakeholders need to be aware of. Walkthroughs can quickly turn into free-for-alls of conflicts, 'side bars' and 'gab sessions' if the review activity is not properly set up or if there is no facilitator. So, make sure the product/project manager has authority and responsibility to manage the design review.

Schedule the review and send out the agenda, all supporting information, questions and issues that may need resolution. And, very importantly, Make sure the attending stakeholders are adequately experienced and knowledgeable in their discipline and have a working knowledge, at least, of the other disciplines involved in the review so they can all reasonably understand the other's viewpoints. No summer interns please.

During the review keep debates among stakeholders at a minimum by keeping them focused on the product, user and business proposals. However, should some stakeholders' needs and goals conflict with other stakeholders' needs and goals, resolving the issues quickly is critical. If possible, arrange to settle known conflicts prior to the review, and resolve new conflicts during or immediately after the review. The sooner conflicts are resolved the better.

For tips on planning the product design review click on: