iSixSigma

Kaizen vs ss low hanging fruit

Six Sigma – iSixSigma Forums Old Forums General Kaizen vs ss low hanging fruit

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #34672

    Os
    Participant

    Hello everyone, I have concept doubts… I still cant see the difference between Kaizen “blocking & tackling” tools vs six sigma low hanging fruit concept. Basically in any six sigma project there are “quick fixes”which dont requiere big fancy statistic analysis. May be in the measure phase (cause and effect matrix, FMEA) we identify that quality problems are generated due to poor workshop order and decide to implement a 5s program to eliminate waste.Please help…Thanks in advance.

    0
    #95942

    melvin
    Participant

    Perhaps there isn’t a difference. What’s the difference between a methodology and common sense when it comes to low hanging fruit? Many would argue nothing…you don’t need a methodology to prove that something is a critical X or is producing defects — if you see the problem, go fix it!

    0
    #95945

    Os
    Participant

    Thanks Bob, i was in doubt of the concept due to a book ( The perfect engine) that puts Kaizen methodology  as a pilar for lean manufacturing, also as a very important strategy to achieve lean sigma. Basically for me there are no differences what so ever.
    The author also remark the point of several Black Belts spending 6 months to finish up a Six Sigma project and stay very distant of the workplace, and points out that applying Kaizen transforms the Six sigma methodology into lean sigma due to lean speed and employee involvement. I do not agree with this, but do anyone has additional thoughts?

    0
    #95950

    Rog
    Member

    Hi Os,
    Personally I reationalized this one by looking at the type of problem that was to be solved. I broke it down into three areas:-
    1) The complexity of the problem
    2) The number of processes involved and
    3) The added value of the project.
    You can then build up a matrix and identify the problems most likely project type. For instance something that was simple, a single process and low value might be a ‘Just Go Do It’ type of project. A complex problem for a single process with a high return is probably going to be a SS application. A complex problem with many interacting processes may be a case for using Lean principles.
    As a basic separator between Lean and SS I would take the following: Lean looks at sources of WASTE and seeks to minimize them whereas SS looks at sources of VARIATION and seeks to minimize them. Not all variation is waste and not all waste is due to variation.
    To me there is no conflict between the two. They are different in approach and to some extent complementary. A good factory design is probably based around Lean Principles a good process design probably has more of a SS basis.
    Your problem arises because both schools, to some extent, claim benefits that are actually attributable to the other.
    Rog

    0
    #95952

    Heebeegeebee BB
    Participant

    OS, you answered your own question.
    B&T is a tool, and the L-H F is a concept/methodology.
     

    0
    #95960

    Os
    Participant

    Thanks Rog your statement works for me.
    regards

    0
    #95962

    mman
    Participant

    I agree with Bob ,as with common sense you don’t need all those methodologies(Six -Sigma or Kaizen….etc..).So low hanging fruit can be caught  by any “common-sense” person then,why to complicate things if we find easy solutions. Thanks

    0
Viewing 7 posts - 1 through 7 (of 7 total)

The forum ‘General’ is closed to new topics and replies.