1. definition of problems 2. Data collection, what is going on 3. Cause analysis, why, what is going on here 4. Solution planning n implementation 5. EValution of effect, did it work? 6. Standardization, make it simple from all experiment 7. Evaluation of process dont get caught in a loop, every solution is a new problems
Very relevant to this day ... but as good as the suggestions are, if WITHOUT the urgency of direct actions, problem solving won't get no where. The spirit of urgency will get you the willingness to DO suggested steps. Your gratification is inspiring when you look back from how much were addressed in the fight.
This is one of the best, most concise presentation I've ever come across in the field of problem solving. The methodology itself is beautiful, but the way the information was systematically rolled out was impeccable. Sehr schön.
This is FREAKING AWESOME! Dude, where have you been during this past and previous semesters!!!!! I hope every person studying business management out there watches this video.
I watched this video 10 times and I’m in love with it. It’s very valuable and you’re a awesome presenter! Wanna hear more of tools like these in future! Best ~ G
This presentation was engaging. I normally get sick of videos for school and stuff but this was super simple and easy to understand! Didn't even feel like it was close to a 5 minute video! Thanks for the content :)
thanks for the initiative to put up this video. Sorry stupid question but can you please make a more detailed video on solution implementation and cause analysis/
it shouldn't . the reason behind this is to understand the process that we too from 1-6 and to seek for learnings and improvements that we could take next time we will be starting from 1 . hope that helps
Technically no because you already found & implemented the solution in step 4 and surveyed the effects in step 5, therefore after you standardize it in step 6, the last step serves as "feedback" for future references. That's at least my take on it since it's similar to the model we use in IT Security. Step 6 "Lessons Learned"
More of the same. It looks like 8D to me. What do we do if the problem goes away because if other reasons than the ones we figured out? It's like anything else. Practice makes perfect regardless of technique. Whatever works for you stick with it and don't get hung up on fancy names, dr this and that.
Well presented and in an effective/efficient manner. However, I agree with another Comment here, regarding - Step 7, should come before Step 6. Evaluations related to the subject processes must be evaluated prior to my approving any Standardization Plan, as the (+/-) directly affect the costs, in both manhours and general overhead associated with the solution. (From the perspective of COO, Operations/Sr Management)
@rajan kakita, True & not true 🤔 a step, process or technique is just a way of doing something. Maybe the title needs to be different but unless you can successfully argue & show that those 7 steps don't solve problems. Then the title is true & correct 🤔👌🏿
what if you are given a problem like : choose 5 random numbers, and a target number, now write a program to find a way to mathematically (+,-,/,x) use the 5 numbers to make the target number. how do I fit the 7 steps here?
This is a great checklist, but doesn't really explain how to achieve these steps. There are papers and books written on each topic. I suggest this as a supplement to other resources.
hmm this method allows you to find a solution, but it won't help you find the best solution. you also need to come up with alternative solutions and selection of solution before implementation
he kind of covered that, he said come up with a solution, evaluate it to see if it worked. if it didn't find an alternative r another solution. so u r saying come up with multiple solutions first, which can b time consuming n maybe unnecessary. where he is saying, come up with a solution if it works move on.
