Trying to Write a Lean Objective

Six Sigma – iSixSigma Forums General Forums Implementation Trying to Write a Lean Objective

This topic contains 2 replies, has 2 voices, and was last updated by  James Heidt 1 year ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #55866


    I am struggling with writing a Lean Objective. I currently have zero documented data so this is truly a lean project not a six sigma project. I have interviewed people and they provided some perceived data, but nothing is better than hearsay. Unfortunately, the company does not record data nor do they want to record data. The basis of the project is to recommend a few improvement opportunities within the procurement process.

    The objective of the PIP was to define areas for improving the acquisition of credit card procurements. This project will reduce the amount of time, which the facility will be down due to lack of procured items. The cost of the facility being down is estimated to be in excess of $1,000,000 per day.



    You don’t have “zero” data. You have subjective data from your interviews. Have you done gemba walks to understand what’s really happening? Have you value-stream mapped the process? With that you should be able to identify some sources of waste and reduce if not eliminate it. Ultimately you will need to a do a project that includes implementing a process to collect and analyze relevant data. If the company is serious about improvement you should be able to get support, especially if your initial improvement recommendations are recognized as helpful.


    James Heidt

    It seems daunting if the company isn’t interested in collecting data, but focus on the best available. You know your metric – time the facility is down due to lack of procured items. Put strong effort into establishing your baseline there (even if the best is just anecdotal – ‘it happened 9 times so far this year’ with evidence is a start). As Strayer said, interview people and pick out a few promising things to focus on (as you say, with Lean mostly). Then as you see improvements you can get momentum to keep moving forward by showing you have improved on your baseline. I’ve done a few projects where I focused too much on data at the beginning and missed opportunities to just make ‘quick-win’ improvements while I waited for my data to be what I wanted, but a strong baseline was the main thing I needed, and I had that. I should have just gotten started, it sounds like maybe you should too.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.