By Shree PhadnisOne of the crucial elements of the project charter in the define phase of a Six Sigma project is the selection of project metrics. Project metrics selected should reflect the voice of the customer (customer needs), as well as ensure that the internal metrics selected by the organization are achieved. Metrics selected should be simple and straightforward and meaningful. Metrics selected should create a common language among diverse team members.
When drafting metrics for a particular project one should consider how the metrics are connected and related to key business metrics. Typically there is no one metric that fits all the requirements for a particular situation.
Developing Project Metrics
The most common approach used by teams is to understand the problem statement, brainstorm metrics, and finally decide what metrics can help them achieve better performance. The team then reviews these metrics with executive management to ensure that they are in synergy with the overall strategy of the business, and an iterative approach may be utilized.
Care should be exercised in determining what is measured. Metrics should be based on what, in fact, needs to be measured to improve the process, rather than what fits the current measurement system. Metrics need to be scrutinized from the value they add in understanding a process.
Balanced Scorecard Approach To Metrics
Many Six Sigma professionals advocate the use of a Balanced Scorecard type of approach for the selection of project metrics as a method for ensuring that the project meets both customer and business needs. The Balanced Scorecard approach includes both financial and non-financial metrics, as well as lagging and leading measures across the four areas or perspectives: Financial, Customer, Internal Processes, and Employee Learning and Growth. Lagging measures are those that are measured at the end of an event, while leading measures are measures that help as achieve the objectives and are measured upstream of the event.
Most Balanced Scorecard metrics are based on brainstorming, however the approach of brainstorming can have limited success in establishing sound metrics that have a good balance between lagging and leading measures.
Typical brainstormed Balanced Scorecard metrics utilized in Six Sigma projects can be summarized in the below. The primary issue in utilizing a scorecard is that it might not reflect the actual strategies applied by the team for achieving breakthrough in their project.
Example Project Balanced ScorecardFinancial- Inventory Levels
- Cost Per Unit
- Hidden Factory
- Activity Based Costing
- Cost Of Poor Quality
- Overall Project Savings
| Customer- Customer Satisfaction
- On Time Delivery
- Final Product Quality
- Safety Communications
|
Internal Business Processes- Defects, Inspection Data, DPMO, Sigma Level
- Rolled Throughput Yield
- Supplier Quality
- Cycle Time
- Volume Shipped
- Rework Hours
| Employee Learning and Growth- Six Sigma Tool Utilization
- Quality of Training
- Meeting Effectiveness
- Lessons Learned
- Total Trained in Six Sigma
- Project Schedule Versus Actual Date
- Number of Projects Completed
- Total Savings To Date
|
Instead of utilizing the Balanced Scorecard approach described above, the teams can employ a more effective method by answering the questions in the figure given below. This approach helps team members understand the objectives of the project from each of the four perspectives.
| The Four Perspectives |
 |
Once the team has brainstormed for each of the four perspectives, the various objectives that must be met by the project will be more clear. These objectives can then me mapped in a strategy map cutting across all the perspectives and projects of the organization. The arrows help in understanding the cause and effect linkages in the strategy. The next illustration shows an example of a strategy map applied.
| The Strategy Linkages (Example) |
 |
Conclusion
Once the strategy map for the project is determined, the team can begin brainstorming appropriate metrics for each of the objectives and, while doing so, maintain a balance in selection between leading and lagging measures. This kind of an approach ensures that the team selects a set of metrics that are aligned with the strategy used by them on the Six Sigma Project. Metrics selected in this way not only ensure that appropriate metrics are developed but also help the team in the project planning and creates a purpose of direction for the team.
References
The Balanced Scorecard by Kaplan & Norton
Managing Six Sigma by Forrest. W. Breyfogle
About The Author
Shree Phadnis is a Master Black Belt at KPMG India, and is an ASQ Certified Quality Manager and Engineer. Mr. Phadnis is a member of American Society for Quality, and can be reached at shreephadnis@usa.net.
Copyright © 2000-2008 iSixSigma – All Rights Reserved
Reproduction Without Permission Is Strictly Prohibited – Copyright Requests
Publish an Article: Do you have a Six Sigma tip, learning or case study?
Share it with the largest community of Six Sigma professionals, and be recognized by your peers.
It's a great way to promote your expertise and/or build your resume. Read more about submitting an article.
