
Jon Hall from the OU gave a seminar entitled Problem Oriented Engineering? I'm Sorry I Haven't A Clue. Jon admitted that this was the first time he'd tried to give the presentation using "I'm sorry I haven't a clue" as a model, and I applaud him for trying. Not sure in an hour long session you can fit in a passion for Humphrey Littleton and an explanation of the work they're doing designing a problem solving framework though...
I won't try and summarise the framework - if you're interested, I'll just point you to their site, the delightfully named 'SolveMeHappy'.
Now the bit that I want to write about is the game Jon got us to play to demonstrate some of the issues surrounding correctly defining a problem.
The room was split into two teams - one holding Problem cards (the first part of a joke) and the other team holding Solutions (the punch lines). Someone from the first team had to draw/mime their Problem, while their team guessed what it was - I did the first one, and drew a stick man with a golf club wearing two pairs of trousers, my team correctly worked out the question was "Why was the golfer wearing two pairs of pants?".
Then we pass over to the Solutions team, who have to find the solution whch one of them has on a card, then that person has to come and draw/mime the answer. In this case we had a mime of "because he got a hole in one".
After a couple more rounds we did the same thing, but this time NO feedback was allowed from the mimer to the guessers to confirm or deny what they thought the problem was.

Despite the poor quality of the above photo, the problem I drew (yes, me again - there wasn't a lot of volunteering from the rest of the audience!) was "Waiter, why do you have your thumb on my steak?". Remember, no feedback. They didn't have the foggiest what I'd drawn and I had no way to guide them. As a result the Solutions team randomly picked an answer that had something to do with sprouts (the small plant drawing next to mine), and we were all completely baffled why!
The point of all this was to get us to think about the importance of properly understanding the problem being asked, so you don't end up solving the wrong problem, or failing to solve any problem at all.
A nice example occured on round 3 when once the question had been drawn (the one above about a hedgehog crossing a road) one of the solutions team shouted out "to see his flatmate!". Of course, if someone on your team knows the solution, life is very much easier.
I think all this links to my post yesterday about knowing who to turn to when you have a problem - it's not so important that I know the solution as that I know who to turn to to help me find the solution. Twitter always amazes me - I put out a problem and someone, who I may or may not know, always replies. Usually, very helpfully.
So the problem solving game is changing, I can exploit my network to solve problems more quickly and easily that I ever could before. In fact, as demonstrated by Ben's comment on my blog post yesterday, sometimes my network helps me solve problems (like vulnerable code) that I didn't even know I had.
So basically Jon, I think you should drop the Humprey Littleton jokes, but keep the charades - and maybe someone will buy you a funnier joke book for Christmas ;-}







