Please enable JavaScript.
Coggle requires JavaScript to display documents.
TOSCA - Coggle Diagram
TOSCA
The Five Pitfalls Of
Problem-Solving - And How To Avoid Them
Pitfall 2: Solution confirmation-To avoid this pitfall, you must structure the problem.
Pitfall 3: Wrong framework
Be careful not to blindly apply frameworks to a problem simply because you’re familiar with them.
Pitfall 1: Flawed problem definition
A practical way to state a problem is to use the TOSCA checklist by answering the following questions
Trouble: What indicates the current situation is not the desired one?
Owner: Who is responsible for its resolution?
Success: What will success look like and when?
Constraints: What are the binding constraints on developing a solution?
Actors: Who are the relevant stakeholders?
Pitfall 4: Narrow framing
When we face complex problems involving customers or users we understand poorly, we should avoid narrowly framing them by analogy to other situations. Instead, we should use a design thinking approach to solve them, starting with understanding the problem from the perspective of the people who experience it. Doing so can help us identify opportunities for solutions that we would otherwise miss. We can then prototype multiple potential solutions and test them with real users, rather than “bet the farm” on one idea that may not work.
Pitfall 5: Miscommunication
Forbes
https://www.forbes.com/sites/hecparis/2018/08/30/the-five-pitfalls-of-problem-solving-and-how-to-avoid-them/?sh=7d7ec8143f1d
http://cracked-it-book.com/
Understand the problem (TOSCAR)
Frame the problem statement
Break into smaller problems
Convert smaller problems to data problems
This is where we ask questions such as what kind of data do you need based on the above hypotheses, which variables do you require and how would you collect them?
We apply decomposition or MECE principle(mutually exclusive and collectively exhaustive) to break the problem statement into smaller problems.
https://medium.com/analytics-vidhya/frameworks-for-converting-business-problem-into-a-data-problem-structured-thinking-d982310e3b6e