Back to Course
Complex Problem Solving
0% Complete
0/0 Steps
-
Day 1 : Problems3 Sessions|2 To Dos
-
Day 2 : Helping tools2 Sessions|1 To Do
-
Day 3 : Finding the right problem3 Sessions
-
Day 4 : Prioritize3 Sessions|1 To Do
-
Day 5 : Approaching problems3 Sessions
-
Day 6 : Research3 Sessions
-
Day 7 : Framing the problem2 Sessions
-
Day 8 : Identifying root causes3 Sessions
-
Day 9 : Categorizing your problem
-
Day 10 : Problem Solving Styles4 Sessions
-
Day 11 : Mid-course assimilation & feed back
-
Day 12 : Assumptions and Constraints3 Sessions
-
Day 13 : Assumptions explained with examples2 Sessions|1 To Do
-
Day 14 : Using multiple perspectives4 Sessions
-
Day 15 : Evaluating Solutions3 Sessions
-
Day 16 : Evaluate risks2 Sessions
-
Day 17: Presenting your solution3 Sessions
-
Day 18 : Using criticism2 Sessions
-
Day 19 : Implement the solution6 Sessions
-
Day 20 : Problem solving mindset3 Sessions
-
Day 21 : It's not the End, but a new Beginning1 Session|1 To Do
Lesson 5,
Session 1
In Progress
Approaching a problem: Front End
Lesson Progress
0% Complete
Notice here that what seems to be just one problem actually has several possible entry points, and depending on the point chosen, entirely different solutions will result so the popular belief that the choice of entry point does not matter as we will lead to the same conclusion is false.
Front end entry points:Â
Most problems are attacked on the front end first, which is to say by stating the problem.
For our example the front end entry point could be assessing the previous performance of the team. Looking at their previous scores for the past few years, trying to determine when it started going wrong.