Page 137 - Design for Six Sigma a Roadmap for Product Development

112 Chapter Four

allocation mechanism to target a mix of DMAIC/DFSS projects to be
revisited periodically. In a healthy deployment, the number of DFSS
projects should increase as the number of DMAIC projects decreases
over time. However, this growth in the number of DFSS projects
should be engineered. A growth model, an S curve, can be modeled
over time to depict this deployment performance. The initiating con-
dition of where and how many DFSS projects will be targeted is a
significant growth control factor. This is a very critical aspect of
deployment, particularly when the deploying company chooses not
to separate the training track of the black belts to DMAIC and DFSS
and train the black belt in both methodologies:

■ Available external resources will be used, as leverage when advan-
tageous, to obtain and provide the required technical support.
■ Promote and foster work synergy through the different departments
involved in the DFSS projects.

4.4 DFSS Deployment Strategy

A DFSS deployment strategy should be developed to articulate the basic
DFSS deployment mission, guiding principles, goals, key result areas,
and strategies for its management and operations to guide and direct its
activities. It should be part of the total Six Sigma initiative and deploy-
ment. Usually, companies embark on the DMAIC method prior to
deploying DFSS. Other companies choose to deploy both simultaneously,
adding more deployment mass and taking advantage of the successful
deployment in Six Sigma pioneering companies. Companies in this cat-
egory use benchmarking to avoid deployment failure modes.
The deployment vision is to create a long-term Six Sigma design cul-
ture. This long-term vision can be achieved by taking short-term and
calculated deployment steps forward, usually annually. The combined
effectiveness of these steps is the right-hand side of the deployment
equation. By deployment equation, we mean the momentum (MO). The
momentum can be expressed as the deployment velocity (DV) times
deployment mass (DM) or
MO DV
DM (4.1)

This equation has some scalability depending on the deployment entity.
A deployment entity may be scaled up to the enterprise level or down
to a DFSS team and pass through a business unit or a company, a divi-
sion, or a department. For example, at the division level it means the
total number of projects closed and the average velocity with which
these projects are successfully closed (ended). Initially, in the DFSS