When it comes to Problem solving, I recommend the following (e-)books on amazon: amzn.to/3GkJhn0 amzn.to/3hO1sHz amzn.to/3g70Xrl amzn.to/3EvpUVR I've read these books and they were inspiring me in creating this video. These links are my personal affiliate links, meaning I receive a comission when you buy one of these books via my link, and of course without you having additional costs. Thank you so much for supporting my channel financially :)
I work in research in life sciences and not very often I see this kind of video. Well done! Two thumbs up. This is worthy of recommendation even to my colleagues in scientific research because its simple to follow and very systematic, capturing the essential parts of the process to determine the root cause/s. Thank you. I wish you could do more videos like this, maybe about foresight and trade-off analyses on the solutions side.
Your video is very helpful for a starter like me, trying to get into the profession. More videos would be great. I love the way you explain the concepts coupled with the real world examples. Thanks.
Most people cannot follow this presentation because its not relative through the explanation. Problem solving is not always linear The first question should not have been Why; it should have been When do we not have enough parking spaces. Why can only come reasonably after one knows the frequency of the occurrence of failure or concern (not enough parking spaces) 1- Not enough parking spaces might not be a daily occurrence, it might only be an occurrence relative to a singular event (a ball game, concert, for instance). And therefore only occurs occasionally. 2- Not enough parking space might be a daily occurrence, which interrupts employees timely arrival to work, and is a continual deterrent which results in lost time and could result in disciplinary action against a good and decent employee. ----- These two scenarios require quite different outcomes relative to their cause and the eventual countermeasure necessary to resolve the issue. Using the process indicated in this video will not in all cases discover the relative cause(s) to the issue and therefore not provide the groundwork for valid countermeasure(s). Keep in mind that some problems cannot be fixed because we don't posses the necessary technology----- and---- in some cases its less expensive for an organization to deal with the issue than to finance the countermeasure necessary to completely eliminate its recurrence.
This is an excellent video. In my work I spend a lot of time trying to categorise complaints for improved future root cause analysis. It is difficult to name the categories to ensure we capture the appropriate level of detail regarding the various complaint aspects e.g. issue, cause, products and areas involved. I would like to see if you have atechnique for categorising in this way
Other pathway: Why was he late? Answer: he did not plan to find a parking spot Why did he not plan enough time to find a parking spot? Answer: his friend didn't warn him Why did his friend warn him? Answer: his friend assumed his friend was familiar with the area etc
When it comes to Problem solving, I recommend the following (e-)books on amazon:
amzn.to/3GkJhn0
amzn.to/3hO1sHz
amzn.to/3g70Xrl
amzn.to/3EvpUVR
I've read these books and they were inspiring me in creating this video. These links are my personal affiliate links, meaning I receive a comission when you buy one of these books via my link, and of course without you having additional costs. Thank you so much for supporting my channel financially :)
I work in research in life sciences and not very often I see this kind of video. Well done! Two thumbs up. This is worthy of recommendation even to my colleagues in scientific research because its simple to follow and very systematic, capturing the essential parts of the process to determine the root cause/s. Thank you. I wish you could do more videos like this, maybe about foresight and trade-off analyses on the solutions side.
Thank you very much for this comment. Great to see that you could benefit from it! I plan to produce more content about problem-solving. Stay tuned :)
Thank you for sharing these RCA techniques :)
Your video is very helpful for a starter like me, trying to get into the profession. More videos would be great. I love the way you explain the concepts coupled with the real world examples. Thanks.
Thank you very much for cour comment, I'm glad to hear the format was beneficial for you. More videos are about to come :)
Most people cannot follow this presentation because its not relative through the explanation.
Problem solving is not always linear
The first question should not have been Why; it should have been When do we not have enough parking spaces.
Why can only come reasonably after one knows the frequency of the occurrence of failure or concern (not enough parking spaces)
1- Not enough parking spaces might not be a daily occurrence, it might only be an occurrence relative to a singular event (a ball game, concert, for instance). And therefore only occurs occasionally.
2- Not enough parking space might be a daily occurrence, which interrupts employees timely arrival to work, and is a continual deterrent which results in lost time and could result in disciplinary action against a good and decent employee.
-----
These two scenarios require quite different outcomes relative to their cause and the eventual countermeasure necessary to resolve the issue. Using the process indicated in this video will not in all cases discover the relative cause(s) to the issue and therefore not provide the groundwork for valid countermeasure(s).
Keep in mind that some problems cannot be fixed because we don't posses the necessary technology----- and---- in some cases its less expensive for an organization to deal with the issue than to finance the countermeasure necessary to completely eliminate its recurrence.
Yes, this man is confused about life. Blind leading the blind.
very informative, thank you. only no need to draw people who solving problems while smoking it will link thinking with smoke cigarettes
Appreciate your feedback and your criticism.
found it helpful. Thank you
Awesome! Always happy to support :)
Highly informatives especially the BPMN gateways!!! Massive thanks👏👏
Highly appreciated.
Great visuals and very informative. Thank you 😊
This is an excellent video. In my work I spend a lot of time trying to categorise complaints for improved future root cause analysis. It is difficult to name the categories to ensure we capture the appropriate level of detail regarding the various complaint aspects e.g. issue, cause, products and areas involved. I would like to see if you have atechnique for categorising in this way
Thanks for you comment :). May I ask in which sector you are working? Is it Software related? This could help me trying to think about categories
@@theagilebusinessanalyst Financial Services/banking :)
A very detailed video, thanks so much 👌
You‘re welcome!
very relevant
Very Good
Appreciated!
thank you
Other pathway:
Why was he late? Answer: he did not plan to find a parking spot
Why did he not plan enough time to find a parking spot? Answer: his friend didn't warn him
Why did his friend warn him? Answer: his friend assumed his friend was familiar with the area
etc
You got the Point.
😍👏
This root cause is filled with confirmation bias on the analysis of the hypothesis. It's a good lesson, but could be better.