iSixSigma

Try-storming

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #55096

    Mohit Sharma
    Participant

    What is the difference between Brainstorming and try-storming?

    0
    #198629

    Shelby Jarvis
    Participant

    Brain storming is more of a mental exercise with a cross functional team. Try storming is going into the process and with reasonable review of risks, trying the solution.

    Some situations and teams dictate the use of “trying” through simulation while other situations enable the team to make actual changes to the process.

    From my point of view, Try Storming should be used with restraint. If your situation is of minimal risk(s) in case of error and can be easily undone, then you may have a problem which sets up nicely for Try Storming. The risk(s) include: the effect the change on other processes or teams, chasing a symptom and not the root cause (unless you have completed RCA and the try storming is a solution approach), moving away from focusing on the end goal (North Star) in favor of short term gains, etc.

    The pros to Try storming is being action oriented and rapid improvement. It is just very important to understand and mitigate the risks as appropriate.

    0
    #198630

    Chris Seider
    Participant

    Semantics :) and maybe execution of brainstorming ideas is try storming…but I’ve not heard that term.

    0
    #198653

    Norbert Feher
    Participant

    Try storming is applied when you face a problem and would like to implement some kind of quick fix. Of course this solution is not perfect but improves the current situation. Typically when You try to push out a problem from the important and urgent quarter to important and non-urgent quarter.
    Try storming is very often applied in lean to learn about a key business process.
    Six sigma is looking for the perfect fix therefore instead of trial and error DMAIC is looking for the right first time solution but of course it takes time and therefore sometimes try storming could give You faster results

    0
    #198654

    Norbert Feher
    Participant

    Have You heard aboutthe term “bad solution park”?

    It is coming from TRIZ metholody and could be used in six sigma:
    You collect all the improvement ideas during DMA phases and may return to the list in the I phase.

    It is called bad solution par / list since first ideas are never perfect. Since You collect them during Your project You can have a lot of ideas for improvement. Think about what is good/bad with the ideas and try to get better solutions out of them but only if You are aware of the root cause and have a measurement system to validate the results later.

    Instead of trystorming I often use this list and very often realize that there is always a better solution than I thought of in the beginning.

    Here is a definition:
    http://onlinelibrary.wiley.com/doi/10.1002/9780470684320.gloss/pdf

    0
    #198690

    Mike Carnell
    Participant

    @MohitSharma I have watched this post for a while and managed some level of self restraint in posting a response. I am not a big fan of either brainstorming nor best practices. I’ll explain that in a minute.

    It seems people say they love Deming and read all that he wrote but they pick and choose what they actually want to live by. One of the things he listed in his Obstacles to Improvement was example – basically people looking for solutions. That is Best Practices. Granted it may be something to look at and test but blind implementation makes no sense.

    Brainstorming. Let’s think about what this really means. Let’s say I am 3 sigma capable (Cpk =1). That means I am going to see about 3 defects for each time the operation is performed. For it to have value in a brainstorming exercise that means someone was actually watching on at least one of those 3 times, they understood what they saw and they have an idea how to fix it. There are a lot of stars that need to line up just right to have that work but it never hurts to ask what people think.

    I am with @cseider on the never having heard of trystorming. It sounds like it may be a good thing a little brainstorming and then try it out. That can make sense as long as the try part is structured – collect data and analyze it otherwise you are accepting or rejecting the try based on the same dynamics I just mentioned around brainstorming.

    At the end of the day the more you improve the less valuable observation becomes. It is either the frequency of defects or the speed of the operation that diminish the value.

    Just my opinion.

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

You must be logged in to reply to this topic.