SOLUTIONS ARE NOT THE ANSWER!!
Trainer and Conference Speaker FRANK NEWBERRY will be co-presenting the third part of Pitchcare's Essential Management Skills Programme for Groundsmen and Greenkeepers on 18th September 2008 at Leicester Tigers’ Welford Road Stadium. In this article Frank previews the highly practical, interactive problem solving process that he will be using on the workshop.
A very straightforward approach to solving work problems
A while back a trainee consultant I was coaching (to be able to help others to solve their work problems) was having difficulty with what I thought was a very straightforward approach to solving work problems.
Within moments of his ‘problem owner’ (another trainee consultant) identifying his work problem my lad was in his face barking solutions at him: “What you need to do is this” or “When we had a problem like that, we did this”. He, like many of us, found it hard to stop himself offering solutions immediately. This approach is often described in negative terms as ‘being prescriptive’.
At the time I was reminded of a doctor I went to years ago in London who, whilst I was walking into his consulting room, would already be writing my prescription. It made me smile as he would look up and ask me what the problem was - as he continued to write.
“Would you sign my passport photo please Doctor?” “Certainly” he would reply,
pausing to ask if there was anything at all wrong with me. As I turned to leave with what I needed I could hear the prescription being screwed up and tossed into the waste bin.
If we ‘write prescriptions’ for our friends and colleagues before investigating their problems thoroughly then the waste bin is probably the best place for them.
Everyone in the training room roared with laughter and applauded enthusiastically.
It was when my trainee became more familiar with a very sensible problem solving process that he came up with a response, which we incorporated into all the training programmes we offered to consultants who had a ‘working’ background as opposed to an ‘academic’ one.
“Frank” he announced, “I now realise that as far as problems are concerned - solutions are not the answer!”. Everyone in the training room roared with laughter and applauded him enthusiastically. What he meant was that ‘instant solutions’ and ‘quick fixes’ perhaps have less chance of
being successful than an answer that has been crafted as a result of some investigation and analysis.
Let us look now at a simple seven-step process that can be done by individuals, but really comes to life when done in teams, i.e. in your own work team.
Step One: Identify a problem we might be able to do something about
It may not be wise to spend too much time wondering how we can change the weather, but we might be able to tackle some new problems that are being caused by bad weather conditions. If we are working as a team we might need someone to take ‘ownership’ of the problem e.g. the team member most affected by the problem who has the time and the motivation to tackle the problem.
Step Two: Gather information about the problem
It helps the process if the problem can be expressed as a ‘How do I’ or ‘How do we’ statement, such as ‘How do we get the new apprentice to get to work on time every day?’ At this point the
problem solving team has a clear focus and can quickly get started on bombarding the problem owner(s) with questions in order to get the clarity they need. For example ‘How long has this been going on?’ ‘What have you tried already?’ ‘What worked with other people?’ and then the real detail on bus timetables, social habits, alarm clocks working or not, and so on.
Step Three: Identify potential causes
When we have the clarity we need on the problem itself we can start team members, or even people from other departments, generating a list of potential causes for the problem, e.g. ‘not used to the early hours’, ‘unreliable transport’, ‘up too late at night’ etc. On the 18th September workshop in Leicester we aim to get a page full of potential causes or combinations of causes for every problem identified.
Step Four: Identify most likely causes
With a long list of potential causes we can now invite the problem owner(s) to identify the most likely causes of their problem. Perhaps as many as half might be chosen or, at
It helps the process if the problem can be expressed as a ‘How do I’ or ‘How do we’
120
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140