Continue reading: The problem solving algorithm

The problem solving algorithm

 I have been watching several discussions over the years between brilliant people where clear perception of the problem prevented them from solving it.  It is so easy to marry ourselves with our suggestions of action (how) that we loose focus about  what the nature of the problem really was.

For cases like this, I advice teams to follow this problem solving algorithm:

  1. Surface problem
  2. Concretize problem  – write it down!  (what, when, how, who)
  3. Find root cause
  4. Surface ideas  (start with those that helps improving the existing situation)

For seeing situations like this, I try to keep the following "aha" reminders in the back of my head..

As an arguing manager, if I can’t concertize the problem it is a sign I need step back and put the right decisions into the right hands – the people closest to the problem.

As an arguing engineer, have I progressed towards engineering a solution, or even evolved into solving another problem (which I felt needed to be sorted first), before concretizing it’s nature with my counter part?

Continue reading
Continue reading: An exercise based on my PSL experience:The power of open-ended requirements

An exercise based on my PSL experience:The power of open-ended requirements

Today I held a class in Scrum and Lean.
I was able to test some of my learnings from the PSL class in a exercises I made up just the day before. 
The results were almost too good.

Continue reading
Continue reading: Debrief of Problem Solving Leadership class

Debrief of Problem Solving Leadership class

Last week I attended the Problem Solving Leadership class held by Jerry Weinberg, Johanna Rothman and Esther Derby.
It was a week full of exercises and simulations and I consumed more knowledge during one week than I usually do for months. 
And I am still digesting it.  This is a early debrief of what I think I have learnt.

Continue reading