The last slide clicked, with jitters in his arms the young man set his clicker down. He knew something had gone desperately wrong. A loud voice soon called out " Okay, So what's the return?" For a moment the freshly trained black belt sank back into his suit. After a deep breath he replied "we have a faster process and everyone on the floor is much happier."
If this sounds familiar then you may have experienced or felt the financial evaluation and benefits pressure before. As we all are aware six sigma is a results orientated strategy. We use quantitative data to help us make decisions and we use quantitative data to help prove our results. Ultimately, that is what we are all interested in "the results" and yet it is also the first thing most of us will forget about until the very end of a project's life cycle. So here are five tips that will help ensure you document benefits and show the financial results everyone wants to see.
Lesson one: The first lesson is always the most important!
We don't advocate batching of materials, so why would we support batching of data? The truth is data is a build up that is best defined right at the kickoff and collected all throughout the project. Just watch the face of everyone when you're headed back to your office and the data is complete already. While this is the most important lesson, it can also be one of the hardest to accomplish. So why not invest in a specialist? Grab somebody from payroll, grab somebody from HR or grab the CFO them self. Okay don't grab the CFO, but do fill one of your team slots with a financial specialist. Consider these reasons why:
Number Two: Establish it from the start
Almost every project charter requires us to establish baseline measurements or some type of starting point that improvements can be measured against.
Likewise, if "soft savings" will do the trick, everyone will know and agree from the beginning. Whether it is hard or soft savings the metrics you establish will be key drivers of the team's behavior and the project's success. Aside from using a Pareto Priority index another very helpful tool to help teams understand how to consider project benefits is the decision tree or cause map. Essentially the tree is just a flow chart which shows a process for consideration of costs and benefits. Organizations should establish their own but a general one is available for download to help you get started. After you have developed your decision tree teams can then have a standardized process they can follow when capturing and evaluating benefits. Of course there will be exceptions but whether you cover 20% of decisions or 80% of decisions it will be less information that you need to remember for the next time around.
Another way of doing this is by instituting daily huddles within your organization. The huddle can be a great opportunity to provide the entire team with updates and have a scribe capture the benefits as the project drives down the highway. Here is a standard format you can use for a daily team huddle:
Another great technique to use during a project's life-cycle are tollgates. Tollgates like driving on the freeway prevent or grant individuals and teams the authority to move onto the next stage of their project. One way to ensure that financial benefits and associated costs are captured is to establish a criterion for your "pass." The criterion will act as an assessment that teams can check their projects too and be granted "the go ahead" by one with authority. Tollgates are a great opportunity to ensure that each phase of the project is completed and up to date too. You can download a sample format for assessing projects at the "tollgate" below.
With so many different means of communication a team could end up updating each other all day long. You need to make the method of communication effective and efficient. One way to consolidate information throughout a project is by using dashboards and scorecards. As you create these efficient means of communication project benefits can be captured much easier.
Lesson Five: Compare the Actuals with Reality and Improve
We can capture all the benefits in the world, but if nothing is done with those benefits they are in fact waste. The transformation comes in the doing and the acting. The PDCA model can be applied to capturing project benefits as we learn to:
Every project is important in some way. But we must make our benefits and the improvements, changes and transformations known somehow. Incorporating these five evaluation and benefits techniques into your next project may have your presentation ending with a "That was a fantastic presentation! We were aware of the amazing changes all throughout the project and hearing the hard savings today really helped us understand your results."
Lean Strategies International LLC. accepts postings from all Lean and Six Sigma professionals to submit a post please visit: Submit a post.