The Smart Solution Book 68 Tools For Brainstorming Problem Solving and Decision Making David Cotton
The Smart Solution Book 68 Tools For Brainstorming Problem Solving and Decision Making David Cotton
The Smart
Solution
Book
68 Tools for Brainstorming,
Problem Solving and
Decision Making
Edinburgh Gate
Harlow CM20 2JE
United Kingdom
Tel: +44 (0)1279 623623
Web: www.pearson.com/uk
The right of David Cotton to be identified as author of this work has been asserted by him in accordance
with the Copyright, Designs and Patents Act 1988.
The print publication is protected by copyright. Prior to any prohibited reproduction, storage in a retrieval
system, distribution or transmission in any form or by any means, electronic, mechanical, recording or
otherwise, permission should be obtained from the publisher or, where applicable, a licence permitting
restricted copying in the United Kingdom should be obtained from the Copyright Licensing Agency Ltd,
Barnard’s Inn, 86 Fetter Lane, London EC4A 1EN.
The ePublication is protected by copyright and must not be copied, reproduced, transferred,
distributed, leased, licensed or publicly performed or used in any way except as specifically permitted
in writing by the publishers, as allowed under the terms and conditions under which it was purchased,
or as strictly permitted by applicable copyright law. Any unauthorised distribution or use of this text
may be a direct infringement of the author’s and the publisher’s rights and those responsible may be
liable in law accordingly.
All trademarks used herein are the property of their respective owners. The use of any trademark in this
text does not vest in the author or publisher any trademark ownership rights in such trademarks, nor
does the use of such trademarks imply any affiliation with or endorsement of this book by such owners.
Pearson Education is not responsible for the content of third-party internet sites.
10 9 8 7 6 5 4 3 2 1
19 18 17 16
NOTE THAT ANY PAGE CROSS REFERENCES REFER TO THE PRINT EDITION
PART 3 P
ROBLEM-SOLVING TECHNIQUES
FOR INDIVIDUALS AND SMALL GROUPS 21
1 Force-field analysis and graphical force-field analysis 23
2 Tough questions 26
3 Ritual dissent (and ritual assent) 28
4 Brain-friendly brainstorming 30
5 Reverse brainstorming 32
6 Procrastination 34
7 Cartesian logic 36
8 Brainwriting 39
9 Individual and collective mind mapping 41
10 Structured walkthroughs 43
11 Life through a lens 45
12 Nominal group technique 47
13 GROW for problem solving 49
14 Head/heart-push/pull 51
15 Osborn-Parnes’ critical problem-solving process 53
16 Appreciative inquiry 55
17 Competitive ideas 57
18 Why not? 58
19 MUSE 60
20 Ishikawa fishbone diagrams 61
21 Deming’s PDSA Cycle (the Shewhart Cycle) 63
22 3D stakeholder mapping 65
23 The two words technique 67
24 The association grid 69
25 The Delphi technique 71
26 The Lotus Blossom technique 73
27 Photographic associations 77
28 The random word technique 78
29 Challenging assumptions 80
30 Metaphorical problem solving 82
31 Who else has solved this problem? 84
32 How-how? 86
33 The 5 Whys/question everything 88
34 The Jelly Baby Tree 90
35 Future shock 94
36 What if? 95
37 What if we didn’t? 96
38 Reframing 98
39 The ripple effect (systems thinking) 100
40 What I need from you 102
41 Concentration diagrams 104
42 The Pareto analysis – simplified version 106
43 The solution effect analysis 109
44 The work map 110
45 The competing values framework 115
46 Timelining 120
47 One question 122
48 Peer assist 124
49 Action learning 126
50 Story circles 128
51 Swim lane diagrams (Rummler-Brache diagrams) 129
Index 175
D
avid Cotton spent 21 years with Arthur Andersen and PricewaterhouseCoopers
(PwC) before becoming a freelance trainer in 2002. He has worked in 4
continents and more than 40 countries, delivering a wide range of training
in management, leadership, communication skills, business networking, confidence
building, dealing with difficult people, change management, business strategy,
coaching and mentoring.
David’s clients span local and national government and nearly every industry
sector and include the European Parliament, European Commission and many of its
agencies, the United Nations, BBC, Syrian Ministry for Foreign Affairs, Russian Federal
Commission, Croatian MOD, PwC, most of the major Middle Eastern oil and gas
companies, Manchester Business School and many others.
He is a Fellow of the British Institute for Learning and Development, a Member of
the Institute of Leadership and Management and also has Diplomas in Training and
Development, Hypnotherapy and NLP.
He has published scores of articles and more than a dozen books, including Key
Management Development Models published by FT Publishing in 2015.
In his spare time, David is a regular columnist for a specialist music magazine and
an avid collector of musical instruments. He has published more than 800 pieces of
music and performs regularly with his band. He plays Association Croquet for his local
club and, with his wife, appallingly bad golf.
I
rather like solving problems. The most brilliant boss I ever had schooled me in this
early in my career. ‘I don’t pay you to bring me problems,’ he said, ‘I pay you to find
solutions. Come back when you have.’ For a young professional, this was a great
message. Most of my subsequent bosses responded far better to a request to choose
the best solution than to solve a problem.
The Smart Solution Book is a collection of tools, techniques, ideas and ways of
thinking about problem solving and decision making that synthesises ideas from a
variety of sources – from traditional problem solving, through creativity to mass-scale
collaborative approaches.
Many of the techniques outlined in the book can be scaled up or down in terms of
the numbers involved in using them: from a one-person effort to a cast of thousands.
Some are subtle variants of each other and some of them include their own variants.
The trick for you, as a user, is to take a technique that looks relevant to your problem
and then adapt it to work for you. Nothing here is set in stone – there is no single way
of doing anything – and you can combine techniques to create something even more
powerful.
Some years ago, I had the good fortune to attend a training course run by the
European Commission entitled ‘The Art of Participatory Leadership’ (AOPL). It was
based in large part on ‘The Art of Hosting’, a new approach to harnessing collective
wisdom, regardless of the size of group involved in, say, problem solving or decision
making. The essence of it was that well-structured collaborative thinking can yield far
better results than a reliance on a small group of nominal leaders, that there is real
power in the collective. In many organisations, the most senior people attempt to
solve organisational problems almost independently of those who will be affected by
the outcome. AOPL opened my eyes to a number of techniques that can be used by
large groups of people working collaboratively to solve problems and make decisions
that really matter to them and to those they serve.
There is a deep satisfaction in solving a problem, and collaborative problem solving
creates an energy of its own. Many organisations list teamwork high on their list of
values and expected competencies. When people work together towards a common
goal, it creates a buzz – a real excitement – which brings people together and creates
a bond and team spirit that generates many other spin-off benefits for the organisation.
Personal agendas are set to one side and people start to realise that, collectively, they
can achieve far more than through their individual or corporate silos.
Most of the collaborative problems solving techniques detailed here deny the
dominant, aggressive or senior people a louder voice – everyone has an equal say
and the quieter people are given a voice that they may lack in day-to-day work. The
broader spread of ideas yields more creative and thoughtful solutions which work for
a greater number of people. It can take a certain courage, in a senior position, to
relinquish some of your assumed authority and allow more junior people a voice. Also,
it will vastly increase the respect that others have for you as a leader. The days of
command and control leadership are, largely, gone. Those who still embrace it will
find themselves increasingly isolated from their workforces. The new generation – the
Millennials – do not respect people simply because they have a title and a higher pay
grade, but expect to see their bosses do something to earn respect. They have grown
up in a society in which the gap between them and their parents, and them and their
teachers, has narrowed and the voice of authority is as likely to be laughed at as to be
entertained seriously. The new generation has seen more of the world and, often, has a
greater social conscience than its forebears had at the same age. The older generation
is often intent on cloning younger people in its own image. The younger people are
unlikely to stay in an organisation long enough to be cloned. Indeed, they are likely to
change professions regularly throughout their working life. Recently, I ran a workshop
for a large professional organisation. The participants were of mixed grades from newly
appointed assistants to senior partners. A partner declared that everyone in the room
had the single goal of becoming a partner in the organisation. I suggested that most
would not stay long enough to become partners, nor had any ambition of doing so.
The senior partner asked for a show of hands. Of the 30 or so people in the room, only
two declared their intention to reach partnership level.
The Millennials want to be a part of the decision-making process, regardless of their
level of experience, and many of the techniques described here allow them that voice.
It does not matter that they lack the experience of more senior people. Their fresh
perspective and optimism may bring a different texture to otherwise staid decision-
making and problem-solving processes. Old timers may find reasons why something
cannot be done. Younger people may bring sufficient enthusiasm to find ways of
making it happen.
This book offers ways of engaging people at all levels to solve problems, often in
fun, dynamic and unexpected ways. For good measure, I have thrown in some more
traditional problem-solving methods, too.
Throughout the book, I talk about, ‘business,’ problems, used as a blanket term
for any kind of organisational problem. Whether you work in the private sector, public
sector, charity, social enterprise or voluntary organisation, the methods described here
can work as they are or can be made to fit with very little tailoring. If an example of how
to use a technique appears to be based in a different sector than your own, you will
find you can adapt it very easily to fit your situation.
Throughout the book, too, I talk about brainstorming. At its simplest level,
brainstorming is just calling out and noting ideas without discussing them until no
more ideas are forthcoming. Standard, traditional brainstorming on its own is not
terribly effective, for reasons that become clear when you read about brain-friendly
brainstorming later, but the basic premise of brainstorming is a building block in many
of the techniques documented here.
I refer to those helping to solve a problem as participants. You will find guidance on
how to prepare them to be useful participants!
As you read about each tool, model or idea, you will find sufficient information to
know how you can use that tool in practice, where you can find more information about
it (where that exists) and, in many cases, start to apply it immediately in your own
working life. Some of the methods are my own inventions, and this is the only place in
which you will find them documented.
This book will help you to:
■ frame problems so that they can be solved (and so help in the decision-making
process);
■ find (often multiple) solutions to the most intractable problems;
■ enjoy the process of problem solving, whether alone or in collaboration with
others;
■ become more creative in your thinking so that, over time, solutions begin to
present themselves;
■ make decisions with more confidence, knowing that you have explored every
avenue before committing to those decisions.
To get the best out of the book:
1 Read the introductory sections on barriers to problem solving, framing a problem
and stages in problem solving.
2 Determine whether you will attempt to solve the problem alone, with a small
group of people or with a large group.
3 Use Part 1: Which tools to use and when. If your problem fits into a broad
category, use the first index:
a) Find the most appropriate category for your problem.
b) Look at the columns on the right to see which techniques work best for the size
of group involved in solving your problem.
c) Skim through the techniques listed to find the one that looks most appropriate.
If you have a very specific problem, use the second index, which will point
you towards techniques that you can use on your own (directly or with a little
adaption) or with others.
Remember that you can combine tools and techniques to create even more
powerful problem-solving tools.
I hope that you enjoy the book and find it rewarding. I would welcome feedback on
your successes, your creative adaptation of the methods, and on the ways in which
you have applied the tools in this book.
David Cotton
Email: [email protected]
Web: www.davidcotton.co.uk
Twitter: davidcottonuk
Which Tools to
Use and When
Y
ou can use many of the techniques on your own. Some also lend themselves
to small group work and some to large groups. For these purposes, let us say
that a small group comprises between 6 and 20 people. A large group can be
anything from 20 upwards. In 2011, a World Café session in Tel Aviv involved 10,000
people. You do not need to think on such a grand scale (just yet) . . .
Whilst many of the problem-solving and decision-making tools are multi-purpose,
applicable to a wide variety of issues, some are particularly good for specific purposes.
In the table below you will see the category of problem for which they may be useful, the
number of the tool or technique and an indication of the size of group that can use it:
One person = you
Two people = small group
Three people = large group
Perhaps unsurprisingly, there are more tools and techniques that can be applied
to a wide variety of problems and these are listed below as ‘Creative idea generation/
Generic problem solving’.
Many techniques are scalable in terms of the numbers who can use them, and you
will see that these are indicated by a mark in more than one column.
Whilst the first index looks at fairly generic types of problem, after it you will find a
key to the best methods for solving more specific problems.
(continued)
Category Tool/technique
Decision making 7 X
3, 9, 11, 12, 16, 19, 39, 50 X
55, 56, 57 X
Framing a problem 38, 54 X
2, 38, 47, 54 X
54 X
Learning/career 48, 49, 50 X
development
Planning 3, 4, 5, 9, 11, 16, 19, 22, 25, 35, 37, X
39, 46, 50, 52, 63, 67 X
46, 52, 55, 56, 58 X
Process/system/ 20 X
product design and 9, 10, 16, 20, 21, 29, 36, 51 X
improvement
57, 66 X
Project planning/ 9, 63 X
project
management
Root cause analysis 20 X
20, 32, 33, 41, 42 X
Stakeholder 22 X
management 22, 40 X
40 X
Strategy/ 3, 4, 5, 9, 16, 19, 34, 25, X
organisational 39, 52, 60, 63, 67 X
design/
52, 55, 56, 57 X
organisational
development
Testing a solution 37, 43, 39 X
10, 18, 37, 39, 43, 59, 65, 68, 50 X
39 X
Time management 6, 44 X
44 X
Problem-
Solving
Essentials
T
here is something rather magical about solving a problem. When you find a
solution, often you know instinctively that is the right one – it just feels right.
Problems may manifest themselves in many ways, including:
■ a discrepancy between expectations and reality;
■ failure to meet a standard;
■ the need for something to exceed the standard;
■ inconsistent results or performance.
There are many reasons why it is difficult to find a solution to a problem. Here are
some common causes and brief solutions and, after the table below, you will find more
detailed ways of dealing with each issue.
be convinced that continuing to do whatever they are doing will result in disaster before
they will contemplate changing.
The problem is too big to be solved as one: Break it into smaller, more manageable
sub-problems, ensuring that you do not lose sight along the way of the original problem.
Poor framing of the problem: You get what you focus on. If you are sloppy in the
wording or framing of a problem, you are unlikely to solve it. First, ensure that you are
stating the right problem. I have seen many organisations investing time and money
in finding brilliant solutions to the wrong problem. If someone asks you to design a
chair, the concept of chair as you understand it now becomes the anchor point for
your thinking. Everything you design will be linked somehow to your current concept
of a chair. But what is a chair for? Perhaps you decide that it suspends someone in a
comfortable state. Now you are released from the concept of chair so you can focus
on designing something that a chair is good at. At the simplest level, you may design
a hammock. At a more complex level, you may find some way of helping someone
to hover, supported by a cushion of warm air. In solving problems, you are designing
solutions, and you can do this only once you really understand the problem you are
trying to solve.
Instead of asking why not enough people buy our products, ask why some people
do buy our products and why other people buy our competitors’ products. What do
we do right? How can we capitalise on it? What do our competitors do right? Can we
introduce some of their thinking into the enhanced version of our own products and
thus take a bigger market share?
Before involving others in problem solving (and, indeed, solving a problem on your
own), look very carefully at the way you have framed it. Play around with the wording
of the problem statement, and then walk away from it. After some time, return and see
if it still feels right:
■ Does it capture the essence of the problem?
■ Is it too simple? Too complex?
■ What would happen if you did not solve the problem? Would anything change?
■ Would the problem go away if you ignored it?
■ Would a solution to this problem bring other problems in its wake?
(See the next section for more ideas of how to frame a problem.)
Solving the problem too quickly: Systems thinking theory suggests that the way out
of a problem may lead very quickly back in. If you try to solve a problem too quickly with
inadequate research or too little understanding of the ramifications of the solution (not
only within, but outside your own work area), you may do more harm than good. On the
flip side, do not leave an issue unresolved for so long that it escalates or grows bigger.
Politics: Sadly, an understanding of organisational politics is necessary in problem
solving. You may hit on the perfect solution only to find that you are not allowed to
implement it because it does not fit someone’s personal agenda. Involving the right
people and using methods that give them no greater voice than others and expose
them to wider, more popularly held views may help.
Dominant people: Many of the methods offered in this book prevent the more vocal,
senior or dominant people pushing others towards their solutions. You cannot avoid
the person who wants centre stage, but you can choose problem-solving methods
that allow them no greater say than anyone else involved in the process. Indeed, some
of the problem-solving techniques described here are conducted largely in silence.
Lack of understanding of the problem: We did our best to solve it, but did not really
understand it sufficiently well at the beginning. Here you need to ask good questions,
collect information and contextualise the problem for others helping you to solve it.
Pros Cons
Too little Fresh insight and ideas Too much preparatory work
unconstrained by standard needed to bring them to a
approaches and received level at which they can be
wisdom helpful
A lot They understand the context, They find it difficult to move
the language, the jargon and away from fixed ideas and
underlying assumptions or standard approaches. They
presuppositions ‘know’ the answer and
are reluctant to entertain
alternatives
Failure to consult the appropriate people: If you do not consult those affected by
the problem, you may not fully appreciate it. If you do not consult those who will be
affected by the solution, you may alienate people and cause bigger problems than the
one you set out to solve.
Failure to communicate the solution: Solving the problem is not enough – you need
to communicate the solution to those who will be affected by it and those who were
affected by the original problem. Think broadly here because often an apparently trivial
problem and an apparently small solution or decision can have far-reaching effects.
Trying to solve a problem by using the same thinking that created the problem:
We become institutionalised in our thinking very quickly after joining an organisation. If
you apply the same thinking, the same measures, the same assumptions to a problem
that its creators applied, then you will have little hope of solving the problem. This book
is full of methods that will allow you to escape assumptions and be free to explore
alternatives.
Fixing the symptoms without getting to the causes: Single loop learning patches
over the symptoms – we recognised a problem and we fixed it. Double loop learning
explores the root causes of a problem and then fixes the controls or processes that
allowed the problem to occur in the first place. If you face a nagging problem at work,
discover how it can happen and how you could recreate it, then you will understand
how to fix it so it does not happen again. For many years, I led an international team
of trainers. When someone made a mistake, I would thank them and ask them how
they did it. They were astonished to be thanked, but my thinking was that they had
found a way to do something that our procedures had allowed to happen and, far from
admonishing for an error, I was grateful that they had exposed a problem in the way
that we were working. We discovered the root causes of the problem, resolved them
and shared the results as best practice.
Framing a problem
Einstein is alleged to have said, ‘If I had an hour to solve a problem, I’d spend 55
minutes thinking about the problem and 5 minutes thinking about solutions.’
Here are some quick and dirty ways to frame a problem, so that you can solve it.
40-20-10-5: State your problem in 40 words, cut it to 20 words, then 10, then 5, to
get to the real root of the problem. Sometimes, you will find that concision in framing
the problem suggests the solution to the problem.
Collect information: Ensure that you have all the facts at your disposal before you begin
to solve a problem. Do this particularly if the problem is rather abstract or vague. Once
you have amassed information about the issue, be as specific as you can in framing it
as a problem question. Consider using this little framework when collecting information:
Tendency/
Problem Importance Urgency
Frequency
1
2
3
4
changing the manager, adjusting or revising a system or process. These are all
business issues rather than training issues. I will, happily, conduct a business needs
analysis and propose solutions based on business needs, but have not conducted a
TNA in more than a decade because I do not want to skew my thinking (nor that of my
clients) from the outset.
Broaden the view: In focusing on a small, finite problem, you may miss something
at a higher level that is causing the problem. By questioning the bigger purpose – the
reason for doing something – you may discover that the cause of the problem is not at
the level at which you had been looking. Equally, you may be viewing it from too high
a level and need to examine it in more granular detail.
Narrow the view: Now you have broadened the view and not found the cause of a
problem, you may have an inkling that the apparently wide-ranging problem has a tiny,
very specific cause. Narrow your focus and see what you can find.
Change the perspective: We tend to see issues from a single perspective. By looking
at a problem from another perspective – even someone else’s perspective – you may
gain fresh insights into the true nature of the problem. You may even see the solution
without further effort.
Frame a problem as a question, not a statement: ‘We’re not selling enough widgets’
is a statement. Asking, ‘How can we sell more widgets?’ or ‘How can we command a
bigger share of the widget market?’ opens up many more avenues of thought.
Don’t think of
a lemon OK
Turn it on its head: If you are struggling to resolve something, explore instead how
you could or indeed do create the problem. Rather than asking how to reduce road
traffic accidents, consider all the ways in which you and others can create them; then
use your answers to stimulate ideas about how you may reduce them. Creativity
comes from attacking a problem from a different angle. Throughout the world, town
centres are filled with traffic signs. In 2008, the German town of Bohmte received
an EU grant to remove its road signs. The only two rules that drivers must obey are
a speed limit and giving way to the right, whether to a car, a pedestrian or a cyclist.
The number of accidents has reduced dramatically since then. Similar experiments in
the UK, Denmark, Belgium and the Netherlands have resulted in a great reduction in
accidents. Sometimes, the act of removing rules means that people start to think again
for themselves and act more sensibly. If you set out to solve a problem by replacing
one control, process or system with another, consider whether you might get the
results you want by removal of the control instead.
SCAMPER it: SCAMPER is a simple checklist tool for thinking creatively about a
problem. It stands for substitute, combine, adapt, modify (magnify or minify), put to
other uses, eliminate, rearrange (reverse). You do not have to apply every element of it
to your problem, but select the more appropriate ones. Imagine I have a problematic
process, a system or a problem, which we will call X:
Substitute: Could I substitute something in place of an existing element of X?
Combine: Could I combine two or more elements of X to create something more
useful?
Adapt: Which parts of X could be adapted to resolve my problem?
Modify (magnify or minify): Could I modify some aspect of X? Would making part
of it bigger or smaller resolve my problem?
Put to other uses: Could I take something from somewhere else and use it here?
Could I use aspects of X usefully somewhere else?
Eliminate: Could I remove some part of X to make it work more effectively?
Rearrange (reverse): Could I do parts of X in a different sequence? If I reversed
elements of X, would it work better?
Applying SCAMPER to a problem, I may find that the problem simply goes away.
Focus: Faced with a series of related problems, be careful to focus on the central or
pivotal one. See if one element of the bigger problem is a tipping point. Often, by resolving
one small problem, the related series of problems is diminished or even removed. For
example, a team is not performing as well as it should, there is a higher than average level
of staff sickness and members are failing to fulfil their stated objectives. The organisation
determines that a teambuilding event will boost morale, help them to regroup and
improve their performance. The real problem is their manager who has been promoted
on the basis of technical excellence with little or no equipment to manage. Train or swap
the manager and the other problems disappear. Imagine a problem has a timeline: shift
your focus from the presenting problem to the time before the problem appeared and
look into the future to determine the longer-term effects of the problem.
off on
Many of the methods in this book follow these stages, sometimes repeating a stage to
drill further into a problem.
Problem framing
Frame the problem in a way that captures the real essence of the problem and is
understood by those seeking a solution.
Divergence
The divergent stage is, for many, the fun and creative stage in which a wide range of
possibilities is explored. There are no clear solutions at this stage. If you facilitate it
well, you will find that it raises lots of questions and questions keep the door open to
learning. Strong facilitation is needed to ensure that there is method in the apparent
madness of this stage – keeping people on track and ensuring that they still have the
original problem in mind – whilst allowing them the freedom to think around a subject
and make free and creative associations with the problem.
Emergence
The emergence stage sees some order begin to emerge out of chaos. The answers
that start to emerge are not, necessarily, clearly defined nor thought through in depth
but begin to shed light on the problem. It is important at this stage to ensure that
the problem solvers remember the initial purpose of their activities and do not pour
enormous energy into solving the wrong problem or a different problem. It can cause
frustration among those who want (quick) results.
Convergence
Testing
Check that the solution works. Sometimes, you may have to test it in a small, contained
area before applying it more broadly. Often, you will know simply that it works.
Implementation
off on
It is easier to manage each of these reactions if you can identify who falls into each
category. Do not simply expect that changes in approach, working methods, systems,
controls processes, ways of behaving, etc. naturally will be accepted readily by
everyone affected by them. We explore each of these reactions in more detail later in
the section on implementing solutions.
Equipment needed
For most of the methods in this book, you will need little more than paper and pens,
a flipchart (or whiteboard) and marker pens and the occasional sticky note or sticky
coloured dot.
In each section you will find a description of what you need. The emphasis throughout
is on methods of thinking through problems rather than on the use of technology to
resolve them.
Problem-
Solving
Techniques
For Individuals
and Small
Groups
When to Use It
■ One of the single biggest causes of failure when an organisation plans change is that
those affected by the change feel that they have no say in it. Use the force-field analysis
as early as possible in the change process, involving as many people as possible who
are likely to be affected directly by it. Use it, too, once a high-level change plan has
been prepared, to determine the order of priority in the planned steps.
How to Use It
Divide a flipchart into three columns – two wide columns on the left and right and one
narrow column between them. At the top of the left column write Helpers and at the
top of the right column write Barriers. In the narrow middle column write (vertically) a
brief description of the proposed change.
Brainstorm all the things that may help to make the change work, and list them
in the left column. This should include things that already exist on which you can
capitalise or things that, if implemented, would make a positive difference. You may
choose to distinguish between the two by asterisking existing helpers. At this point,
there should be no discussion, except where clarification is needed.
Brainstorm all the things that may make the implementation of the change difficult,
listing them in the right column. Again, you might like to distinguish between existing
and possible or anticipated barriers to change. Go back to the Helpers column and
add any new ideas, repeating the process for the Barriers column.
Imagine, for example, that you are brainstorming ways of improving staff motivation.
Note that there is no attempt here to counterbalance each barrier on the right with
a helper on the left: the two lists are, relatively speaking, independent of each other,
although, in reality, the points on one side will, sometimes, be the reverse of the points
on the other.
Using a green marker pen, ascribe weights (strengths) to each Helper by drawing
an arrow under each one, pointing towards the middle. The length of the arrow (short,
medium, long) indicates the strength of the idea. Alternatively, add scores to them to
show their relative strength.
Using a red marker pen, ascribe weights (strengths) to each Barrier by drawing an
arrow under each one, pointing towards the middle. Again, the length of arrow (short,
medium, long) denotes the strength of the idea. Alternatively, add scores to them to
show their relative strength.
For example, a group brainstorming helpers and barriers to staff motivation may
produce something like this:
Helpers Barriers
Now examine each of the Helpers in turn, discussing how you can capitalise on them
to make the change process easier. Start with the items that have long arrows, then see
if there are ways to increase the length of those with medium and short arrows, building
a picture of everything positive that either exists now or could be done relatively easily.
Then focus on the Barriers, exploring how you can reduce or remove them
completely, to make the change process more effective. As before, start with the long
arrows, then medium, then short.
Variants
1 Two-team version: Two teams produce the force-field analysis. Using two different
flipcharts, team 1 lists Helpers; team 2, Barriers. Teams swap. Team 1 finds
solutions to the Barriers and team 2 finds ways of capitalising on the Helpers and
each shares their ideas with the other.
2 Graphical force-field analysis: Two teams produce the force-field analysis, drawing
pictures instead of writing words. Often, this engagement of the creative side of
the brain results in more imaginative ideas. One person from each team stays
with their team’s flipchart and the others swap over. The Helpers team first must
interpret the other team’s pictures (aided by the team member who has remained
with the flipchart) and then find ways to reduce or remove the barriers that the
pictures represent. The Barriers team must interpret the other team’s pictures
(aided by the team member who has remained with the flipchart) and then find
ways to capitalise on them. Ideas are shared in a plenary discussion.
Reference
Lewin, K. (2013) The Conceptual Representation and the Measurement of
Psychological Forces. Eastford, Connecticut: Martino Fine Books. Reprint of a
book first published in 1938.
Questions open doors to exploration and creativity. Answers close those doors:
often, the moment we believe we have solved a problem, we stop exploring it. Tough
questions is a powerful tool that helps an individual or team to explore a problem in
depth before attempting to find a solution. Indeed, when used well, the technique
may throw up questions that have not been considered and change the nature of the
problem being explored.
When to Use It
■ In the early stages of planning change, exploring an issue or attempting to solve a
difficult problem.
■ When a colleague has a difficult problem and requires fresh thinking to resolve it.
How to Use It
The technique works best with one or more teams of around five people.
1 One person (the originator) writes down on a sheet of paper a question to which
they have found no satisfactory answers.
2 The originator puts the sheet on the floor, sits down on one of the chairs, reads
out the question once or twice and focuses on the question, staring down at it on
the floor.
3 Others stand around the chairs and consider the question.
4 If the original question prompts a new question in one of the others, they may
sit in the vacant chair and ask that question out loud. Nobody must make any
attempt to answer any of the questions raised – their job simply is to ask more
and more questions. Nobody needs justify their question nor explain why that
question should occur to them based on the previous question – participants
must accept that the question seemed relevant to the questioner.
5 Anyone can tap one of the seated participants on the shoulder at any time and
take their place. When a person is tapped on the shoulder, they must stand up
and give their place to the person who tapped them.
6 Once seated, a participant must ask one or more further questions.
7 Continue until nobody has any more questions.
8 At this point, the originator should write down the last question asked, read out
the original question again and the final question.
It can be incredibly powerful to see how the original question mutates through a series of
other questions into something that may, at first hearing, seem unrelated to the original
question. Often, the final question has more depth and power than the original and
opens up new thinking about the original subject. Sometimes, a transitional question may
generate a new stream of thinking and bring insights to the original problem. The person
posing the original question may choose to note some of the transitional questions.
Variants
Use this as a breakout activity in a bigger event. A number of people declare in plenary
the questions that they want to explore, each related to the broader theme of the
event. Interested parties join them in smaller breakout groups and each group uses this
technique to explore the individual questions. In plenary, the owners of the questions
read out just the starting and final question from their breakout session. It is interesting
to see the reactions of the larger group as the questions are read out.
When the activity is working at its best, the final questions can be quite startling to
the larger group and can be the basis of further discussions using other techniques in
this book.
References
Adams, M. (2009) Change Your Questions, Change Your Life. Oakland, California:
Berrett-Koehler Publishers.
Pope, G. (2103) Questioning Technique Pocketbook. Alresford: Teachers’ Pocketbooks.
When to Use It
■ To test proposals or ideas.
How to Use It
Variants
If appropriate, you may repeat the cycle, for example:
■ asking the speakers to join a different table to present and listen to the discussion;
■ asking groups to further explore their ideas, informed by feedback from the
speaker in the last round, then getting each group to appoint a different speaker
to present their refined ideas to a different table group.
When to Use It
■ To generate ideas to be used in problem solving or decision making.
How to Use It
1 State the problem to be resolved or decision to be made. Ensure that everyone
understands it.
2 Brainstorm ideas for just two minutes. You may ask someone to keep time for the
group. As each idea is called out, it is noted on the flipchart, with no discussion.
3 Stop and discuss something completely unrelated to the problem for a minute
or two.
4 Restate the original problem or pending decision.
5 Resume the brainstorming, noting each item on the flipchart as it is called out.
You will find that the most creative and useful ideas will emerge after the short break.
The participants’ unconscious minds continue to work on the issue, trawling through
past experiences to produce better answers.
To resolve the dominance/seniority issue and to arrive quickly at a list of ideas worth
further discussion:
1 When the brainstorming session is finished, ask for a show of hands from the
whole group for each idea in turn. If the majority believes an idea worthy of further
discussion, mark it with a green + (plus).
2 If the majority believes it is not worth pursuing, mark it with a red − (minus). Do
not allow any discussion or defence of an idea; if it is outvoted, it is not
discussed.
Variants
If you struggle to write the ideas as quickly as they are called out, the group loses
energy. When you are working with a large group of people – say more than 12 – it
can be difficult to keep up with the group. Use more than one flipchart, appoint one or
more additional scribes to note ideas, and take turns to write the ideas down. On one
occasion, we worked with around 30 people, using four scribes and four flipcharts.
Each scribe, in turn, would write the next idea as it was called out. This allowed us to
keep up with the flow of ideas and maintain the energy in the group.
Reference
de Bono, E. (1985) de Bono’s Thinking Course. London: Ariel Books.
When to Use It
■ When discussion of possible solutions to a problem yields pedestrian answers.
■ When you are trying to resolve a problem related to something that people
constantly do badly or wrong.
■ When you are working with a group of people who have done something the
same way for a long time, not considering that it could be done differently or
better.
How to Use It
The technique works best with a group of between 6 and 12 people.
1 State the problem to be solved.
2 Ask the group to call out every possible way of creating the problem.
3 Write each suggestion on the flipchart.
4 When no further ideas are forthcoming, ask the group to use the suggestions to
stimulate real solutions to the original problem.
For example:
The problem: How can we improve the service offered by our call centre?
Now use the PMI technique (see Tool 4) to determine which of the answers are worth
further discussion. Consider using a voting or ranking technique to prioritise them.
Reference
de Bono, E. (1985) de Bono’s Thinking Course. London: Ariel Books.
Tool 6 Procrastination
Leonardo da Vinci took years to paint the Mona Lisa, perhaps as long as a decade. Its
slow progress frustrated him, but, in the years in which he carried the idea of the picture
around with him and continued to improve it, he studied optics and his understanding
of light may have informed his painting – arguably, he became a better artist as he
failed to finish his masterpiece.
Psychologist Bluma Zeigarnik noted that people are better able to remember tasks
that they have not completed than those that they have. A waiter will tend to remember
what diners ordered up to the point at which the bill is presented, and then the order
will disappear from the waiter’s short-term memory. Zeigarnik said that people were
twice as good at remembering interrupted tasks as they were at remembering
completed work – the fact that it preys on your mind suggests that your subconscious
has continued to work on it in the background.
The cliff-hanger ending to an episodic drama has precisely the same effect as the
unfinished task – it gnaws away at us until we see some resolution.
When to Use It
■ When you have spent some time staring at a problem, unable to find a solution.
How to Use It
1 Start by writing concisely the problem to be solved.
2 Recite the problem statement to yourself a number of times.
3 Sketch a few ideas that may contribute to the solution.
4 Walk away.
5 Return to it occasionally, and attempt to solve it only when you are under
pressure to do so.
References
Grant, A.M. (2016) Originals: How Non-Conformists Move the World. Viking.
Zeigarnik, B. (1938) On Finished and Unfinished Tasks: A Source Book of Gestalt
Psychology (pp. 300–314). New York: Harcourt.
When to Use It
■ hen you need to ensure that you have looked at the problem from every possible
W
angle.
■ When you are torn between two possible solutions.
■ When avoidance of the issue could be as useful as tackling it.
■ When you want to test a possible solution to a problem.
How to Use It
Consider your problem and a possible solution. Let us call the solution X. Ask yourself:
■ What would happen if I do X?
■ What would not happen if I do X?
■ What would happen if I do not do X?
■ What would not happen if I do not do X?
Write down the answer to each question.
Do Do not
Would happen
Would not happen
For the logically minded, the questions are based on the statements:
■ If A then B.
■ If A not B.
■ If not A then B.
■ If not A not B.
You will discover quickly that the questions lead to similar answers and, usually, the answer
to your problem becomes obvious as you work through the questions. Sometimes, the
answers raise further questions about your values – what is really most important to you?
You may choose to ascribe weights or scores to each element of your moral dilemma,
according to its importance to you and use the weighting to select the best answer.
For example:
Do Do not
Would happen He may lose his enthusiasm He will continue to be rude
The team will be happier with He may alienate the rest of
his behaviour the team
He will continue to be
enthusiastic about his work
Would not happen His continued enthusiasm He will change his ways
The team’s continued upset at He will be alienated
his behaviour
His continued input to the
project
The subtle differences in wording in each box take some thinking through. Very often,
the method confirms what you already knew, but it is good to have that confirmation.
Often, too, the result is not quite clear-cut: the reality in this example is that I should
tackle the rudeness issue because it is inappropriate and affecting the whole team. The
more basic question seems to be about my management ability! I have avoided talking
to someone about inappropriate behaviour because it makes me uncomfortable, and
it seems I have decided that the only way my team member can be motivated is by
allowing him to be rude to others. The problem of his enthusiasm may need to be
tackled as a separate issue. Asking all the right questions helps to clarify the way
forward, at least partially, even if the results are uncomfortable.
Do Do not
Would happen I will be eligible to apply for a I would be frustrated that
director’s post in my firm (all I haven’t advanced either my
the directors have MBAs) learning or my career
I continue to see as much of I could never fulfil my ambition
my family of becoming a director
What comes out of this is the moral dilemma: what is more important – career or
family? Perhaps the real solution is to consider studying for an MBA over a longer
period, so that I can fulfil both ambitions, taking more time with my family and still
getting the qualification that makes me eligible for directorship.
Variants
You can use Cartesian Logic with a group of people who will tend to expand the range
of ideas beyond those that you could think of for yourself.
Tool 8 Brainwriting
When to Use It
■ It is particularly useful for collecting ideas from people who are reluctant to offer
ideas in a group session or when you need to solve several problems in parallel.
■ Use it, too, to prevent senior or loud participants dominating a session – this way
everyone gets a say, and in silence.
Problem:
Owner:
How to Use It
Small Group, Multiple Problems
Variants
The same technique can be adapted to large groups with multiple problems and small
groups with a single problem.
When to Use It
■ hen you need to think on a large scale, resolving problems whose solutions may
W
have far-reaching effects.
■ As a planning tool, to ensure that you have covered all possibilities.
■ As a design tool, working in collaboration with others.
How to Use It
1 Draw a circle in the middle of a sheet of paper, turned landscape, and write a brief
description of the problem inside it.
2 Allow yourself to think freely about the problem.
3 As each major solution occurs to you, draw a branch leading from the central
circle, and label it with a brief description of the solution.
4 As you think in more detail about each possible solution, draw sub-branches
leading from the appropriate branches and label those, too, with a brief
description.
5 If you see links between sub-branches, connect them with lines or arrows.
6 Now look at the overall picture you have created and allow it to inspire new ideas,
new connections not yet made, new branches and sub-branches. Add them in to
the mind map.
If you are working with a group of people, ensure that you have large sheets of paper
(flipchart pages attached to a wall are ideal) and lots of space to manoeuvre. Encourage
people to take lots of time out to stand back and look at the map as it begins to
emerge, so that each person’s thinking stimulates ideas in others. Use colourful arrows
to connect ideas.
Brain-friendly Reverse
Pro
b Brainstorming
fra lem
OFF min Argument
g Divergence
ImpON Discussion
leme
ntatio Problem Debate
do n
st solving Eme Dissent
Ju it! rgen
ce
Revelation
Aha!
Co Lightbulb
g nv
stin erg moments
t Te en Agreement
Pilo ce
all Comin
Sm ale toget
g
sc her
ll
Fu cale
s
A simple mind map relating to problem solving shows five main branches, each related
to the five primary stages, and sub-branches illustrating more detail about each area.
Drawings can be useful to trigger key thoughts, memories or ideas.
Reference
Buzan, T. (2009) The Mind Map Book: Unlock Your Creativity, Boost Your Memory,
Change Your Life. London: BBC Active.
When to Use It
■ When you have a partly developed solution to a problem.
■ When you need constructive criticism to take an idea further.
■ When you feel you can benefit from the collective wisdom of others.
How to Use It
One person is the presenter. Appoint a leader and recorder; other participants are
reviewers. Roles are as follows:
Presenter: Presents the ideas and listens to participant feedback.
Leader: Chairs the meeting and ensures an egoless approach, an even pace,
concentration on the key issues and dictates what will be recorded.
Recorder: A non-participant in the discussion, there to record only what the leader
asks to be recorded.
Reviewers: There to listen intently to the presenter, question areas that they do
not understand fully and ask for clarification in difficult areas. Reviewers should
be both interested parties and people with no vested interested in the finished
solution. They should have sufficient background to understand the subject of the
presentation.
1 The leader introduces the topic and, where necessary, the participants.
2 The leader explains each person’s role, how the session will work and sets strict
time limits.
3 The presenter is there to present an idea, a design, a possible solution but not
him/herself.
Reference
Yourdon, E. (1978) Structured Walkthroughs. New York: Yourdon Press.
When to Use It
■ When no obvious solution presents itself.
■ When your possible solution seems too obvious and you want to see it from new
perspectives.
How to Use It
State your problem. Ask yourself or others, if working collaboratively, how would a(n) X
begin to solve it? X may be, for example, an/a:
■ doctor;
■ lawyer;
■ engineer;
■ artist;
■ statistician;
■ politician;
■ office cleaner;
■ IT technician;
■ chef.
Add as many professions as you like to this list, selecting those professions that are
sufficiently unlike your own to give you a broader perspective. Stress that you do not
expect anyone to understand the detailed work of the chosen professions, instead
consider how that person would think about a problem.
For example:
A doctor might diagnose the root causes of a problem before suggesting a cure;
a lawyer might explore opposing sides of an argument before presenting a case;
an engineer might explore the detailed workings of an issue; an artist might make
preliminary sketches before starting the real picture; a chef might ensure that all
ingredients are in place before beginning to create something.
Discuss which combination of these approaches will guide you towards a better
solution and implement the most appropriate.
If you are working with a large group, delegate the appropriate approaches to sub-
groups and have them work in parallel on them, presenting to all in a plenary session.
For example, one group may compile the balanced arguments for and against an
approach, one may sketch a number of approaches and one may analyse the current
situation and its likely effects in more depth.
When to Use It
■ When a group includes very vocal or highly dominant individuals.
■ When you believe that quieter members of the group are reluctant to speak in
front of the more dominant ones.
■ When the group has, traditionally, not generated a large volume of creative ideas.
■ When the issue is controversial.
How to Use It
1 State the problem and check that everyone understands it. The problem is best
voiced as an open question, for example: ‘What are some of the ways in which we
could encourage employees to come to work on time?’
2 Individuals silently generate ideas, writing as many possible solutions as they can
in a fixed time period (5 to 10 minutes is usually adequate). The facilitator may
also write down ideas.
3 In plenary, each participant declares one idea in turn and the facilitator records
them on a flipchart:
a) No discussion of the ideas is allowed.
b) In some versions of NGT, clarification may be sought at this stage. In others,
clarification is sought after all ideas are recorded.
c) A participant may call out an idea that is not on his or her list, but is inspired by
other ideas.
d) A participant may decide to pass in a given round and then offer an idea in a
subsequent round.
4 Discuss each idea in the sequence in which they are written on the flipchart:
a) Members may ask questions and state whether they agree or disagree.
b) The facilitator must ensure that each contributor has equal space to talk about
their ideas and is not subject to verbal attack.
c) The group may combine ideas into categories and offer new ideas stimulated
by what they have heard. The group ranks ideas in relation to the original
problem and votes on them. (See ranking and voting.)
Variants
After ideas have been generated and recorded, the facilitator questions whether the
ideas are relevant to the stated problem. If they are not, the problem is declared ‘ill-
structured’ because it allowed for responses that were not strictly related to it. The ideas
that participants have generated are then clustered into groups – for example, one
group would relate directly to the stated problem, another to a different interpretation of
that problem. The ill-structured ideas are then regarded as problems in their own right
and another round of NGT may be applied to them.
References
Delbecq, A.L. and VandeVen, A.H. ‘A Group Process Model for Problem Identification
and Program Planning’, Journal Of Applied Behavioral Science VII (July/August
1971), 466–91.
Delbecq, A.L., VandeVen, A.H. and Gustafson, D.H. (1975) Group Techniques for
Program Planners. Glenview, Illinois: Scott Foresman and Company.
When to Use It
■ When you need a range of possible solutions to a problem.
■ When you need to explore a problem in depth and bring something concrete to a
partly formed idea.
How to Use It
Perhaps the world’s most popular coaching tool is GROW, which provides a sequence
for questioning the coachee. GROW stands for goal, reality, options, will/way forward.
Typically, the coach asks the coachee a number of questions to help the coachee explore
a goal, further questions to establish the reality of the coachee’s current situation and the
possible options available to the coachee based on that goal and reality. Finally, the coach
tests the coachee’s willingness to continue to work towards the goal and asks which
option or options the coachee will undertake first.
The same tool offers a useful framework for problem-solving. You can use it on your
own or with others.
Goal: Explore in as much depth as you can the problem you are attempting to solve.
For example:
■ What would happen if you did solve it?
■ What would happen if you did not?
■ What would it look like, feel like (even sound like) if you had solved the problem?
Engage as many senses as possible to make the end goal seem as realistic as
possible.
■ How would you know that you had solved it?
Reality: Explore, again in as much depth as possible, the reality of your current
situation and the environment in which you are trying to solve your problem:
■ Who or what might help you?
■ What are the potential barriers or constraints?
■ What might be the indirect consequences of finding a solution?
Options: Explore the choices available to you that might resolve the problem.
Be as creative as you like at this stage, constantly checking that your possible
solutions will actually resolve the original problem and testing the feasibility of your
proposed solutions against the reality of your situation.
Will/way forward: Given the reality and possible options, do you still have the will
to resolve this problem? Which option or combination of the options will you select
to start resolving the problem and what will be your first step?
Reference
The GROW model has been attributed variously to John Whitmore, Alan Fine and
Graham Alexander. There are few references to it as a method for pure problem solving.
As a coaching tool, there is an abundance of literature. Perhaps the best known is:
Whitmore, J. (2009) Coaching for Performance: GROWing Human Potential and
Purpose – the Principles and Practice of Coaching and Leadership. London:
Nicholas Brealey Publishing.
Tool 14 Head/Heart-Push/Pull
Head
Pull Push
Heart
The head argument is a rational one, dealing with facts, figures and information
coolly and objectively.
The heart argument works at the emotional, subjective level, tugging at the heart
strings and offering opinions rather than facts.
The push approach argues a case so that the listener feels that they have no
choice but to comply.
The pull approach attracts the listener towards an argument, making it seem
irresistible.
By combining head-push, head-pull, heart-push, heart-pull, you can create a set of
arguments to convince people from varying standpoints that what you are doing is
right for them and for the organisation.
When to Use It
■ To ensure that you communicate the solutions to a problem in the best way for
different audiences.
■ Typically, you would use this at the end of a problem-solving session. You have
found a solution to a problem and now you and those who participated in
the problem-solving exercise need to consider how to communicate the
solution to others.
How to Use It
Either work as a single group or divide the group into four smaller teams, each of which
focuses on one facet of communication and then reports back in plenary. The facets
are head-push, head-pull, heart-push and heart-pull.
For example: You are a travel agent and you want to entice a couple to buy an
expensive holiday from you:
Heart-pull – ‘Imagine the scene: you are standing on a beautiful beach, the
gentle waves lapping at your feet in the soft white sand. Above you, in the azure
sky, there is barely a wisp of cloud and a warm breeze strokes your cheeks.
In your hand, a cocktail. You haven’t a care in the world. And all this could be
yours for just £2,550 per person, half board!’ The aim is to make an expensive
holiday so attractive that the couple cannot resist it, by taking them with you at
an emotional level.
Head-push – ‘On the limited budget available to you, there are only two holidays
that you can afford – pony trekking in the Welsh mountains or a city break in
Edinburgh. So, if you are restricted to the first week of May, those are your
options.’ The aim is to push the couple into accepting a holiday at the top of their
budget by stripping out any emotional appeal and being absolutely rational.
In reality, you may have to communicate your solutions to a broad range of people,
and the trick here is to have considered your communication from all four viewpoints,
so that you have your arguments ready and can deal with objections or resistance at a
personal level with those to whom you communicate your ideas.
When to Use It
■ hen you are faced with a problem that affects a large number of people or a
W
decision whose effects could be wide-ranging.
How to Use It
1 Mess finding (objective finding)
Challenge yourself at this stage so that you identify clearly the problem to be
explored.
For example:
■ What is the challenge or goal that you wish to explore?
■ What would you like to do or to have?
■ What would you like to improve?
■ In what ways do you work inefficiently?
■ Which relationship(s) would you like to improve?
■ What is currently making you angry or frustrated?
2 Fact finding
Use the six question words here: Who? What? Where? Why? When? How?
For example:
■ Who is currently involved? Who should be involved? Who might expect to be
involved? Who will we deliberately not involve?
■ What is happening? What is not happening? What would happen if . . .? What
would happen if not . . .?
■ Where does X happen? Where does X not happen? Where could I make X
happen?
■ Why does X happen? Why does X not happen? Why do we face this problem?
■ When does X happen? When does X not happen?
■ How does X happen? How can I make X happen? How can I stop X from
happening? How is X a problem?
3 Problem finding
You get what you focus on, and the way you define a problem will have a distinct
impact on the solutions you find. At this stage, you should list a number of
alternative definitions of the problem. Try prefacing the problem statements with,
‘In what ways might I/we . . . ?’ Then ask, for example:
■ What is the real underlying problem?
■ What is the primary objective?
■ Why do I want to do X?
■ What is my goal in accomplishing this?
4 Idea finding
Use any brainstorming or creative thinking techniques you like here to generate
ideas. Avoid criticising or evaluating the ideas at this stage. Your aim is to create
the broadest list of possible ideas.
When to Use It
■ For organisational change.
■ For strategic planning.
■ For community development.
■ For building networks.
■ For resolving conflict.
■ For helping teams to see how to work better together.
How to Use It
For some years, the most widely applied version of AI was a four-step approach to
problem solving, which focuses on:
Discovery: Appreciating the best of ‘what is’ now. The idea is to hold on to the
aspects of the object of inquiry that are really worth preserving. What is working well
that we should preserve?
Dream: Envisaging what might be. What would the organisation, team, etc.
look like at its very best? This is often created as a graphical representation of a
possible future rather than a carefully wordsmithed vision.
Design: Discussing what should be. What concrete proposals can those involved
suggest? These are sometimes referred to as possibility statements or design
statements.
Delivery/destiny: Innovating what will be. Cooperrider changed the name of the
fourth stage from delivery to destiny because of a concern that the term ‘delivery’
had connotations of traditional change management. At this stage, participants
in the process take actions to make the dream and design a reality. The process
avoids the establishment of committees and project teams, encouraging
participants to do what they believe is right based around some agreement of the
design statements.
It is interesting to note that Jan Carlzon, president of the airline SAS in the early 1980s,
decentralised power to allow his employees to make decisions and solve problems in
the interests of the passengers without first asking for permission. If each of the airline’s
10 million passengers came into contact with 5 airline employees for an average of 15
seconds for each encounter, the airline was ‘created’ 50 million times a year. By taking
authorisation away from management and giving it to the employees, he created new
possibility statements that took a failing airline to ‘Airline of the Year’ in just three years.
Reference
Cooperrider, D. and Whitney, D.D. (2005) Appreciative Inquiry: A Positive Revolution in
Change. San Francisco: Berrett-Koehler Publishers.
When to Use It
■ Best used with groups of people who are naturally competitive.
How to Use It
1 Present a business problem to a large group and then break the group into smaller
groups.
2 Tell them that they have a set time (as appropriate) to create the best solution(s)
to the problem and must present their ideas to the other groups. The solutions
must be worked through and feasible. State that this is a competition between
the groups to find the best solution(s).
3 After each small group has presented their solutions, groups will vote on the best
solution. Groups may not vote for themselves.
4 When the best solution is selected, other techniques may be used to explore in
more depth how it can be put into practice.
As a further incentive, you may choose to offer small prizes to the team with the winning
ideas.
When to Use It
■ To test a possible solution to a problem.
■ To refine a partly developed solution.
How to Use It
1 Present the context of the problem for which you have a notional solution. Explain
your proposed solution.
Variants
1 Participants read out their written objections, then hand them to the problem owner
for consideration, without further discussion.
2 Participants read out their written objections and the problem owner may
question them but not justify the original solution – this way the problem owner
may learn from the participants without becoming proprietorial about the original
solution.
3 In a slightly reworked version of Ritual dissent, (Tool 3) participants read out and
discuss their objections in front of the problem owner, who may listen and take
notes but not take part in the discussion.
Tool 19 Muse
When to Use It
■ To draw out quiet people who may have something useful to contribute.
■ To ensure that those with the loudest voices do not dominate the process.
How to Use It
1 State the problem and invite questions and discussion to ensure that everyone
understands it.
2 Individuals (me) silently write possible solutions to a problem.
3 Pairs (us) discuss their ideas and challenge each others’ thinking to refine the
ideas.
4 Pairs now select the best of their ideas and post them on a flipchart or poster,
visible to all.
5 Pairs explain their ideas in plenary.
6 The larger group ranks the solutions and votes on them.
7 The larger group agrees who will implement the solution(s) and by when.
When to Use It
■ When a team has fallen into a rut in its thinking about a problem.
■ To uncover new connections not immediately obvious through more linear
problem-solving methods.
How to Use It
You can use this technique on your own or with others. The group method is described
below. Working alone, substitute ‘you’ for ‘the group’:
1 Write down the problem to be solved (the Effect) to the centre right of your flipchart
or whiteboard.
2 Draw a box around it.
3 Draw a horizontal line from the right of the paper, connecting to the middle of the
box.
4 Brainstorm the major categories of possible cause of the problem and write them
as branches from the horizontal line.
5 Brainstorm all the possible causes of the problem and for each one, ask ’Why
does this happen?’
6 Write each answer as a sub-branch attached to the appropriate category,
duplicating the ideas if they logically fit in more than one category.
7 For each cause, ask ’Why does that happen?’ and write the answers as sub-
causes attached to the appropriate causes.
8 Keep asking why and adding more layers of branches until the group has no
more ideas.
Ba
Bl
re
gh tm
un
d
pr
co en
de
es
st t
rs
s
of
Poorly itemised
Ba arke
Po ills
m
sk
dly ted
or
pe
Competition Pricing Expertise
o
ple
Points to Watch Out For
The biggest issue in using a fishbone diagram is to ensure that you have sufficient
space on the paper for all the sub-branches. It is frustrating having to start again!
Reference
Ishikawa, K. (2012) Introduction to Quality Control. London: Chapman & Hall.
Plan Do
Act Study
When to Use It
■ In planning for change and continual improvement.
(Note that I have used ‘continual’ here in place of ‘continuous’. Continual implies
stopping and starting, whereas continuous means there is no break in the process.
Realistically, there is!)
How to Use It
Work in sequence through the loop:
Plan: Define your objective, and make predictions about the outcome of your plan.
Be prepared to answer questions about the plan: Who? What? Where? When?
Create or revise a business process to improve results. Determine the data that you
will need to collect to measure the success of the plan.
Do: Implement the plan and collect data to measure the success of its
performance. Ideally, you should test the change on a small scale at first.
Study (also known as check): Analyse the data and report your results to
the appropriate decision makers. Compare your data to the predictions and
summarise what you have learned from the experience and what went wrong.
Act: Decide which changes are needed to further improve the process. Plan the
next cycle and decide whether the change can be implemented or abandon it if
it cannot be made to work.
Reference
Deming, W.E. (2000) Out of the Crisis. Cambridge, Massachusetts: MIT Press.
When to Use It
■ At the start of any project involving multiple stakeholders.
■ At the start of any major change programme.
■ When there are complex relationships between stakeholders.
■ When you need to understand the best ways to influence stakeholders.
How to Use It
1 Bring together a team that has a role in implementing the project or major change.
2 Use duct tape to create the grid shown. Mark the axes and scales using paper
labels. Squares/cells must be big enough to accommodate several people.
3 Brainstorm the names of each individual or group with a vested interest in the
project or change.
4 Write each name in big, bold letters on a separate sheet of paper and distribute
the sheets to participants.
5 Each participant must, with the group’s agreement, move into the appropriate
square/cell in the grid for the stakeholder they represent and hold up the piece of
paper showing the name of the stakeholder they represent.
6 They should stand, kneel or sit according to the expected level of impact of the
project or change on the stakeholder they represent (stand=high, kneel=medium,
sit=low).
7 If a stakeholder is where we would want them to be (e.g. in terms of support or
influence), then leave them as they are.
8 If the project or change would be easier to manage if a stakeholder occupied a
different square, ask the participant representing that stakeholder to point to the
ideal square for that stakeholder – the square in which that person would offer
the most help or cause the least damage to the change or project.
9 If any of the participants believe that they are in a position to influence the
stakeholder to change his/her mind and move to a different square, leave them
as they are. If not, identify someone else in the grid, known to the participants,
who could influence them to move. Attach the influencer and errant stakeholder
to each other with a piece of string.
10 When everyone is in place, hands are pointing and string is attached, either take
photographs of the 3D grid from every possible angle or sketch the map on a
piece of flipchart paper.
Now there are two possibilities:
1 Disband the group and send the photos to each participant. Use prints of the
photos at each project meeting to manage stakeholder relationships.
2 Use the flipchart map immediately in planning how the group will manage
stakeholder relationships.
High
Level of influence
When to Use It
■ To create fresh insights into a problem or to inform a decision.
How to Use It
1 Create a two-word phrase to summarise a problem.
2 Write each word at the head of a column in a table and then freely associate
ideas with each word, listing them in the table columns.
3 Randomly match pairs of words across the columns to gain new insights into the
problem and its possible resolution.
For example:
I manage a team of 20 people whose motivation levels fluctuate and vary from
highly motivated all the time to hardly motivated any of the time (and all possibilities
in between). I want to know how I can create higher levels of motivation for more of
the time. I create a table, headed with the words ‘Staff’ and ‘Motivation’ and make
free associations with those words, writing my thoughts in the appropriate columns.
I then create random pairings of words to see what new ideas emerge:
Staff Motivation
Diverse Happiness
Teams Reward
Individuals Recognition
Clever Gifts
Difficult Parties
Busy Challenge
Lazy Recognition
People Achievement
Let us say I randomly pair the words ‘individuals’ and ‘recognition’. Am I showing
individuals the recognition they deserve, commensurate with effort? Am I showing
favouritism (too much recognition) to some at the expense of others?
Now I pair ‘lazy’ and ‘challenge’. Am I giving people sufficiently stretching work to
stimulate them? Are the ones I deem to be lazy actually efficient workers who complete
their workload more quickly than others? Am I considering some to be lazy who would
work better if they understood more of the context of their work and its importance to
others?
I pair the words ‘diverse’ and ‘achievement’. Am I too focused on one specific
aspect of the team’s work, favouring those who excel in that area and neglecting other
areas of excellence and achievement simply because it has not been on my radar?
I pair the words ‘busy’ and ‘happiness’. Have I been too busy doing my own work
for purposes of self-fulfilment (happiness) to pay sufficient attention to members of my
team?
As you make these random pairings, so they stimulate questions and those
questions open the doors to new learning.
When to Use It
■ As for the two words technique, to create fresh insights into a problem or inform a
decision.
How to Use It
Create a table of five or six columns and rows. Think about the problem to be solved
and, as you begin to associate words or ideas with the problem, write them in the table
cells, one per cell, in any sequence. Now combine ideas randomly from the table, and
new and creative solutions to the problem will begin to emerge.
For example:
You are overwhelmed with work at the moment. Your boss assures that you that
the situation is temporary and that, as soon as a new team member is hired, your
workload will be reduced again to more normal levels.
Not important 3. 4.
Anything deemed to be urgent and important goes into box 1; anything important
and not urgent goes into box 2, etc. I know that I should execute the work in sequence –
box 1, then 2, then 3 then 4 and that the bulk of my work should be in box 2, where I
can plan it properly. What tells me that something is urgent? Whose sense of urgency
is it? If someone tells me something is urgent, a good question to ask is, ‘Which part of
this is urgent?’ Often, a small part is important and urgent (box 1) and the rest belongs
in box 2, where I can take a little more time over it. Many things stop being urgent the
moment that they are delegated to someone else. Perhaps I have more time to do
them than I thought?
Now let us look at the word ‘delegate’ and combine it with ‘overloaded’ and
‘nightmare’. Which team members can I trust? What would happen if I approached
them and said, ‘I’m having a nightmare at the moment. I am covering for X who has
left and I’m overloaded with work.’ Ask them if they can help, even with small things,
which would allow you to concentrate on the bigger issues.
Combine ‘unsupported’ and ‘logjam’. Think about your standard working hours and
how much overtime work you can feasibly do. Prioritise your work, using the Covey
matrix or another favourite method and discover where the real logjams are. Is there
anything that, if it could be completed, would free up a significant amount of time to
tick a number of other items off your list? Consider how you could approach your boss
a second time and explain that you are feeling unsupported at the moment. (It may be
more useful to reframe it in terms of needing support rather than the more accusatory-
sounding ‘unsupported’.) Show your prioritised list and ask your boss to take some
time to work through it with you, asking if there are others who could take on some of
your excessive workload.
You will notice that, in this example, the solutions that begin to present themselves
are largely commonsense. When you are overwhelmed, it can be difficult to see a
situation rationally, and the association grid may help to clear the fog and bring some
objectivity to the problem.
Reference
Covey, S., Merrill, A.R. and Merrill, R.R. (1994) First Things First: To Live, to Love, to
Learn, to Leave a Legacy. New York: Simon and Schuster.
When to Use It
■ hen you want to know with some certainty the likelihood and outcome of future
W
events. For example, as a project manager, what future events may have an impact
on your projects?
How to Use It
1 Appoint a facilitator. Ideally, this should be someone with a background in research
and data collection.
2 Identify a team of experts – people with relevant knowledge and experience of the
topic you are going to discuss.
3 Define the problem to be solved. Create a clear, comprehensive definition of the
problem in language that the chosen experts will understand.
4 Round one: Distribute an open-ended questionnaire to begin the process of
collecting information about a specific area of content. Collate the responses
and summarise them, removing irrelevant material and checking for common
viewpoints.
5 Round two: Create a new questionnaire based on the responses to the first,
designed to explore the topic in more depth. Once more, collate the responses
and summarise them, removing irrelevant material and checking for shared
viewpoints and common ground.
6 Round three: Create and distribute a third and final questionnaire, designed to
support decision making. What have the experts agreed on in their responses to
the first two questionnaires? (You may choose to create further questionnaires if it
is necessary to achieve consensus.)
7 Analyse the findings from the final questionnaire, and plan actions based on the
consensus views.
References
Dalkey, N.C. (1969) ‘An Experimental Study of Group Opinion’, Futures, 1 (5), 408–26.
Dalkey, N.C. (1972) ‘The Delphi Method: An Experimental Study of Group Opinion’ in
Dalkey, N.C., Rourke, D.L., Lewis, R. and Snyder, D. (Eds.) Studies in the Quality
of Life: Delphi and Decision-making (pp. 13–54). Lexington, MA: Lexington Books.
Dalkey, N.C. and Helmer, O. (1963) ‘An Experimental Application of the Delphi Method
to the Use of Experts’, Management Science, 9 (3), 458–67.
When to Use It
■ When standard brainstorming techniques would not give depth of solution.
■ When you want to explore relationships between components of a problem.
How to Use It
1 Draw a 3x3 grid in the centre of the page. This is grid 1, which represents the
central problem to be solved or the issue to be explored. In the centre of the grid,
write a word or phrase that summarises the problem to be explored:
Core idea
Each of the cells around the centre will represent a sub-topic of the main idea.
2 Brainstorm solutions, related concepts or ideas, and write a keyword description
of each in the boxes surrounding the problem in the central grid. You may
struggle at first to suggest eight related ideas, but persevere – the greater the
detail, the richer the solution and the greater the number of associations you will
see between ideas. For our purposes, we have simply lettered the subtopics
A–H:
A B C
H Core idea D
G F E
3 Around the central grid, draw 8 more 3x3 grids – grids A to H (3 above, 3 below,
1 to each side). Each of these grids will be used to further break down the
subtopics, A–H.
1 2 3 1 2 3 1 2 3
8 A 4 8 B 4 8 C 4
7 6 5 7 6 5 7 6 5
1 2 3 A B C 1 2 3
Core
8 H 4 H D 8 D 4
idea
7 6 5 G F E 7 6 5
1 2 3 1 2 3 1 2 3
8 G 4 8 F 4 8 E 4
7 6 5 7 6 5 7 6 5
4 Take each of the words that you wrote in the central grid (in our case, A–H) and
put those words in the centres of the surrounding grids. The diagram will show
you how this would look.
5 For each of the eight grids, brainstorm ideas related to its central theme and write
them in the boxes surrounding the central idea. In our diagram, we have simply
numbered them 1–8 for each grid. In reality, you would have eight sub-sub topics
per grid.
6 When you have finished, you will have 64 ideas to help solve the original problem.
They will vary in usefulness and importance and you may find that just one or
two suggest the best solution. However, by looking at the problem broadly, you
may start to identify the ripple effects of a solution across other aspects of your
operations or organisation.
The problem – We want to improve our customer service at a call centre which is
central to our operations.
In the central grid, we write Call centre and then brainstorm ideas related to the call
centre:
Proactive not reactive Call centre customer service Faster response times
Each of these ideas now becomes the central idea in boxes A–H. Now we need to
brainstorm ideas in each of the grids.
Let us look at box C. In the centre, we write Sharing information. The concept here
is that the better the information sharing among call centre staff, the less duplication of
effort and the better they can offer a quick and consistent service to callers.
Brainstorming Sharing information yields the following ideas . . .
Email tips to super-users Create customer web forum Create staff manual
Repeat the process for each major idea in the central grid. Now you have a wealth
of ideas to help focus your management effort in call centre improvement.
Variants
To complete the 8 grids requires you to think of 64 ideas, which may, at first, seem
daunting. In reality, it is not unusual to generate 64 ideas in a brainstorming session, and
the Lotus Blossom technique gives a structure to the thinking that is lacking in more
traditional brainstorming – you are finding only eight new ideas under eight headings!
■ If you are working with a group of people, break it into smaller groups, with everyone
involved in the plenary discussion about the eight main areas, then each group working
on one or two of the subtopics. You might consider printing nine separate blank grids –
one for the core topic and one each for the subtopics. Distribute the blank grids to
smaller groups. Working on a 9x9 grid may seem less daunting than working on
the full nine-grid model. When each subgroup has finished, put the pieces together
and fix them to a wall so everyone can see the completed picture. One word of
warning here: when everyone works on the grid together, they start to see and
make connections whilst constructing the overall set of grids. If the smaller groups
work in isolation from each other, it may reduce the number of creative connections
and the end result may not be as effective.
But:
■ Consider using something other than squares in your grids. In line with the name
Lotus Blossom, some people create a flower, writing the topic at the centre and the
subtopics on the surrounding petals.
Subtopic
Subtopic Subtopic
Subtopic Subtopic
Subtopic
When to Use It
■ With creative, imaginative groups.
■ With groups who are bored with more conventional brainstorming techniques.
How to Use It
1 State the problem to be solved/the issue to be explored.
2 Distribute a number of photographs among participants. Ensure that there is a
diverse range of subject matter in the photos.
3 Ask participants to make free associations between the images in the photos and
the problem and to document those associations.
4 In plenary, ask participants to call out their ideas and use others’ solutions to
stimulate further ideas.
5 When all solutions have been suggested, use PMI (see Tool 4) to sort them, or a
voting/ranking technique to prioritise them.
Reference
Tanner, K. and Cotton, D. (2006) Picture This. Altrincham: Wize-Up Ltd.
When to Use It
■ When you need to look beyond the obvious for a solution.
How to Use It
State the problem to be solved. Select a random book, random page and random
line number. Find the first noun on the chosen line and write it on a flipchart. Ask the
group to call out anything they associate with the chosen word – it does not matter
how outlandish their suggestions are – in fact, the more creative, the better. Write each
word or phrase on the flipchart as it is called out. There should be no discussion at
this point.
When no further ideas are forthcoming, restate the original problem and ask the
group to freely associate the brainstormed ideas with the original problem. They can
combine the ideas to form new associations with the original problem.
For example:
A restaurant owner is concerned that, because of the location of her restaurant, she
is not attracting the volume of trade she needs. Although the restaurant is in the
centre of a major city, it is on a side-street off a main shopping street from which it
is not visible. She wants as many ideas as possible of how to attract more people
to the restaurant.
After selecting a random book, page and line, the first noun on the line is hammer.
The group’s suggestions include:
heavy
nails
construction
repeated action
metal
wood
destruction
The group now starts to associate the ideas freely with the original problem. Ideas
include:
■ Heavy metal and other themed music nights to attract different audiences (heavy
and metal).
■ Children are given pizza bases and a variety of toppings and encouraged to
decorate the pizzas themselves, which are then cooked and served (construction).
■ Greek-themed evenings with Greek food, music and plate smashing (destruction).
■ Loyalty cards offering a free meal after each six purchased (repeated action).
■ Beautician offering manicures/pedicures before lunch (nails).
Reference
de Bono, E. (2009) Lateral Thinking: A Textbook of Creativity. London: Penguin.
When to Use It
■ When you feel constrained by a system or process.
■ When you feel that a design is becoming old and tired.
How to Use It
1 Ask the group to call out everything that they know about the current object of the
discussion. What are the attributes of the current version? List each answer on a
flipchart.
2 Now ask them to consider that none of these attributes is real nor cast in stone –
each is simply assumed to be real.
3 For each attribute listed, ask them to suggest one or more alternatives.
4 Draw together the alternatives and see what you could create.
For example:
Imagine going back in time to the days of desktop telephones. What were the
standard attributes of the early telephone?
They might include these:
Wires
Dial
Heavy Static
When to Use It
■ hen more conventional ‘head-on’ problem-solving techniques have yielded
W
pedestrian solutions.
How to Use It
1 State the problem.
2 Invite participants to suggest a different problem that is analogous to the
presenting problem.
3 Find solutions to the metaphorical problem.
4 Map these solutions freely back to the original problem.
5 Select from the ‘back-mapped’ ideas, those that have merit.
For example:
1 Attracting more customers/clients – catching fish.
2 Developing our business – growing plants and flowers.
3 Reducing the bureaucracy at work – weeding the garden.
Step 3 Now we have to brainstorm ways of clearing the weeds from the garden.
Ideas might be:
■ Turn over the soil to expose the roots of the weeds, to make them easier
to clear.
■ Use weedkiller.
■ Dig out the offensive weeds.
■ Ensure that, as we dig out the weeds, we retain the flowers that we want
to keep, etc.
Step 4 Now we need to ‘back-map’ the new solutions to the original problem. The
trick here is to do it fairly freely, not trying to find an exact match. For example:
■ Turn over the soil to expose the roots – do a thorough review of existing
policies and procedures and sift out those that are neither valid nor
workable.
■ Use weedkiller – be ruthless in removing useless administrative procedures,
retaining nothing simply because it is the way we have always done things.
■ Dig out the offensive weeds – this really repeats earlier ideas. That does
not matter at all in this process because, often, a repeated ideas suggests
a certain strength of feeling behind the idea. If it feels like the right thing to
do, then it most probably is.
■ Retain the flowers we want to keep – be careful not to be so ruthless that
we throw away useful policies and procedures.
The example is a relatively straightforward one. Somehow, by taking a metaphorical
view of a problem, the discussion can become less emotive because it is held,
effectively, at arm’s length. Then the decisions that fall out of the discussion will seem
easier to execute.
When to Use It
■ When we need a solution in a hurry.
How to Use It
1 State the problem.
2 Setting aside the specific context in which the problem occurs in our organisation,
list those who, at a more generic level, have had to face this or a very similar
problem. You may consider direct competitors, similar organisations or even
organisations or individuals unrelated to your area of work who faced something
similar.
3 What did they do to solve the problem?
4 How can we, either directly or with some tailoring, adopt the same solution(s)?
For example:
An IT repair company asks how it can respond more quickly to its customers in
order to offer better and quicker service.
List what the doctors do to solve their own problem and, against each solution, write
tailored solutions for the IT repair company:
Tool 32 How-How?
When to Use It
■ When trying to analyse the root causes of a problem.
■ When generating new processes or working methods.
How to Use It
In the examples below, we are concentrating on generating new ideas. The same
principles apply in analysing how something has gone wrong. Instead of asking, ‘How
could we do this?’, ask, ‘How did this happen?’
1 State the problem clearly and ensure that everyone understands it. Express the
problem as a need, e.g. ’We need to increase our widget sales by 50 per cent in
the next three months’ or ’We need to attract more people to our library services to
avoid library closures’.
2 Write the problem on a card.
3 Place the card to the left centre of the table.
4 Ask the group (or yourself if working alone) ’How can this be done?’
5 Write each possible answer on a separate card and place the answer cards in a
column to the right of the problem card.
6 For each answer, ask again, ’How can this be done?’ and write the new answers,
one per card. Place each answer to the right of the card that prompted the
question, so building up a hierarchy or tree.
7 Continue the process until you have solutions and no further questions.
Increase
widget sales
Variants
Use sticky notes on a wall/flipchart instead of cards on a table.
When to Use It
■ When a process is not working.
■ When something has gone wrong despite the process in place.
■ For quality improvement.
■ To determine the relationship between different causes of a problem.
How to Use It
1 State what has gone wrong and ask why it has gone wrong.
2 Write down the answer. Answer in terms of what actually happened rather than a
supposition about what might have happened. Does this get to the root cause of
the problem? If so, suggest a counter-measure to prevent the recurrence of the
problem.
3 If not, ask ‘Why?’ again and repeat step 2.
Because!
Why, mummy?
4 Continue, repeating steps 1 and 2, until you have an answer and can go no further
with the questioning.
The 5 Whys suggests counter-measures rather than solutions, because a counter-
measure prevents the problem recurring, where a solution may fix the presenting
problem and recur when the same situation occurs again. It does not matter whether
you ask ‘Why?’ once or 50 times – the number 5 is notional. In practice, you need to
keeping ask it until you have reached the root cause.
For example:
Solution: Ensure that everyone is trained on the new system before using it to plan real
shipments.
When to Use It
The Jelly Baby Tree has multiple uses, limited only by your imagination! They include:
■ resolving a dispute between two colleagues.
■ helping to plan an individual’s career progression.
■ helping to plan organisational career paths.
■ organisational design.
How to Use It
Resolving a dispute between two colleagues
1 Bring together the two people in conflict and explain how important it is that they
work together harmoniously.
2 Tell them that you want to try to experiment – that it may look odd at first, but you
believe that it will help them to resolve their dispute.
3 Give each a copy of the Jelly Baby Tree and some coloured pencils.
4 Ask each of them to colour in the jelly baby that represents them and, in a
different colour, the jelly baby that represents the other person.
5 Ask them to show each other their pictures and invite each, in turn, to explain
why they have coloured in their chosen jelly babies.
6 Because they spend much of their time focusing on the picture and describing,
almost dispassionately, why they have chosen certain jelly babies, they tend to
have a calmer, more rational discussion about the reason for their conflict. Each
will interpret the same character in the tree in different ways and you will hear
them say, ‘I chose this one because it is doing X’ and the other may reply: ‘Oh,
I hadn’t looked at it that way – I saw this character doing Y’. The Jelly Baby Tree
helps them to discuss their issues as though they relate to a third party and, as
the raw emotion is taken out of the discussion, so they begin to realise that they
can talk reasonably to each other, that perhaps they have simply seen things
from a different perspective and that there may be some room for agreement or
settlement of their dispute.
There are many possible uses of the Jelly Baby Tree – be creative!
When to Use It
■ For strategic or operational planning.
How to Use It
1 Determine the area of your organisation that you will focus on.
2 Brainstorm the current processes and systems in use in this area.
3 Outline the results that you currently achieve in this area.
4 Now ask, for each process and system: If we continue to do this, what will the
results be at some pre-specified time in the future?
5 List the suggestions as quickly as they are made, without evaluation at first.
6 Then discuss each in turn, with emphasis on what we can/will/must do to sustain
or improve our current position.
7 Take care to explore the ripple effects of proposed changes on other areas of
operation or likely results.
When to Use It
■ This is particularly useful in a dynamic, enterprising organisation or team that wants
to explore possibilities for improvement.
How to Use It
1 State your business issue. It may be in the form of a business problem, an explanation
of a current process or a way of doing something within the organisation.
2 Participants play ‘What if?’ – calling out ideas of what might be possible. It does
not matter how outlandish or far-fetched the ideas seem to be at first sight.
3 Record the ideas without debate, judgement or discussion.
4 You may ask the participants to rank the raw ideas before developing them
further. Use other techniques, such as PMI (see Tool 4), to develop the ideas.
When to Use It
■ hen you have a potential solution to a problem but are unsure that it will reap the
W
desired benefits.
How to Use It
1 State the problem and your proposed solution.
2 Brainstorm (and write down) each potential benefit of implementing the solution.
3 For each benefit, ask ‘What if we didn’t do/didn’t need this?’ and ask, for
example, ‘What is the cost of solving this?’ and ‘What is the likely cost of not
solving this?’
4 Score the total ‘package’ of benefits (1=low and 10=high) and then score the
counter-arguments on the same scale. Which carries the higher score? If the
score given to benefits that would result from solving the problem is lower than
that for the counter-arguments, do not proceed to solve the problem, instead
accepting that it is a given and that you can live with it.
For example:
Should we increase our staff salaries by 5 per cent to match those of our biggest
competitor?
not a motivator.
■ We have actually recruited from our
Whilst the potential benefits here look appealing (score of 7), each is counterbalanced
with an argument (total score of 9) which suggests that, overall, the solution is not
worth implementing.
Tool 38 Reframing
When to Use It
■ To gain new insights into a problem.
■ To inform decision making.
■ To lift the morale after something has gone wrong at work.
How to Use It
1 Brainstorm the most pressing concerns for your team, department or organisation.
2 State each one as a question.
3 For each in turn, invite participants to frame the question so that it becomes an
avenue for exploration or a statement of opportunity.
For example:
Problem Reframe
Why aren’t sufficient people buying from us? Why do people buy from us?
Who does buy from us, and can we expand that
market?
Why is client X so difficult? What can we do differently to work more effectively
with client X?
How are we being difficult with client X?
How can we offer the same services, faced Which services can we offer, faced
with budget cuts? with budget cuts?
Which services can be made cheaper?
Which services do people really need?
Who else is offering a similar service?
Who wants our current services?
Now use other tools to explore the best of the reframed statements in more detail.
A problem solved in one part of an organisation may have ripple effects in other
areas of the organisation, again sometimes appearing only some time after the solution
is effected. The ripple effect is a technique designed to tease out the effects that a
change made in one specific area of the organisation has on all the other areas of the
organisation.
When to Use It
■ hen you plan a major change in your operational area and need to know if/how it
W
affects others and, as such, whether your plan is workable in its current form.
■ You may want to use the solution effect analysis method (see Tool 43) first, to
satisfy yourself that you have looked at all the possible side-effects that you could
predict before looking at the wider organisation.
How to Use It
You will need a group of people representing as many areas of the organisation as
possible.
1 State the problem for which you have a possible solution.
2 Ensure that all participants understand the nature of the problem – state it as
factually as possible, avoiding any emotional hooks and remembering that the
participants may not understand the jargon you use in your own operational area.
3 State your proposed solution, again ensuring understanding.
4 Now ask the participants to reflect silently for five minutes on the possible
ramifications for their area of work, noting down questions and concerns.
5 After five minutes, ask participants to raise their questions and concerns.
6 Do not worry if you do not have immediate answers to each concern, but thank
them and note it.
7 Invite participants to suggest modifications to your ideas that could reduce
or remove the effect on their operational area without rendering your solution
unworkable.
8 When all suggestions have been discussed, thank the participants and agree a
time by which you will report back to them.
9 After the meeting, assimilate their ideas and rework your solution.
10 Distribute the revised solution to the participants, inviting final comments by a
specified date.
Reference
Senge, P.M. (2006) The Fifth Discipline: The Art and Practice of the Learning
Organization. London: Random House Business.
When to Use It
■ hen you have reached a solution to a problem and want to ensure that everyone
W
knows what may be expected of them as the solution is implemented. Ideally, use
this after collaborative, cross-departmental or cross-functional problem solving.
How to Use It
1 Invite representatives of each area of the organisation who will be affected if you
implement a proposed solution to a problem.
2 Write the name of each department represented on a separate flipchart sheet and
fix the sheets to the walls.
3 State the original problem and your proposed solution. Invite participants to ask
questions to ensure their understanding of both the problem and the solution.
4 Ask each one to reflect, in silence, on what they would need from your department/
business area and others’ departments/business areas if the solution is to be
viable. Each request should be written on a separate sticky note and signed by its
author, then posted on the flipchart page representing the department or business
area of whom the request is being made. For example, if someone representing
HR needs something from IT, then they write the request and post it on the IT
flipchart page. If requests are time-critical, then the time for fulfilment of the request
should be added to the sticky note. If the requests can be fulfilled only by specific
individuals, their names should be added to the sticky note.
5 After posting their requests, participants should walk around the room and read
the requests on each flipchart page to get a broad picture of others’ thoughts.
6 Finally, participants should stop at the flipchart relating to their own area of work,
then in turn, in plenary, ask requestors clarifying questions to ensure that they
truly understand what is being asked of them. If necessary, the written requests
should be modified by those who wrote them.
7 If appropriate, additional specific requests should be added to the flipchart pages
to balance any modifications made in the plenary session.
8 Photograph each flipchart page and either send the appropriate photo to each
participant or type and send the appropriate requests to each participant.
There is a nice spin-off effect from this method – almost by stealth it achieves buy-
in from other departments as you involve them in the process. It can be even more
powerful if you involve the same participants first in the problem-solving process using
one of the methods in this book, and then facilitate this process so that everyone
knows exactly what is expected of them.
When to Use It
■ To discover exactly where a problem is occurring, which may, in turn, reveal patterns
of occurrence of the problem.
How to Use It
1 Draw a map of the building, the room, the area or the system.
2 Determine whether you already have data about the location in which a problem
occurs. If you do, then go to step 4.
3 If you do not have that data, list the events that you need to record to connect
them to locations.
4 If recording more than one event, assign symbols to each event.
5 Map the events on the diagram.
6 Analyse patterns or trends in the diagram.
For example:
Our office cleaners have been complaining that there are coffee stains on the
carpets and that they are struggling to keep pace with the number of people who
appear to throw more coffee on the carpets than they ingest. We want to know
where the worst stains are and whether we can detect a pattern that suggests why
this is happening.
First we map out the areas that the cleaners tell us are worst affected – the areas
around the reception desk, guest seating area, kitchenette and photocopier room.
Then we mark the worst areas of staining on the map.
From the map, it seems that there is a trail of stains between the reception desk,
kitchenette and guest seating area and another cluster to the side of the photocopier.
We can guess that the receptionists, eager to welcome our guests, slop coffee as they
carry it from the kitchenette to the guest seating area, and that people photocopying
rest their coffee cups on the side of the copier.
Although this is a trivial example, it illustrates how the concentration diagram can be
used to detect patterns, useful in analysing root causes of a problem.
Reception desk
X
X
X Kitchenette
X
X
X X
X
X XX
Reference
Andersen, B., Fagerhaug, T. and Belz, M. (2010) Root Cause Analysis and Improvement
in the Healthcare Sector: A Step-by-Step Guide. Milwaukee, Wisconsin: ASQ
Quality Press.
When to Use It
■ To determine where to focus management effort in solving a problem.
How to Use It
There are many variants on the Pareto diagram, and some require detailed statistical
analysis. Here is a simplified version, which can be adapted to many situations to
discover the primary causes of major problems and thus show you where to focus your
main management efforts.
1 Identify and list your problems.
2 Identify the root cause of each problem.
3 Score the problems.
4 Cluster the problems by root cause.
5 Add the scores for each cluster.
6 Take action to resolve the problems.
For example:
I have assumed responsibility for a team that manufactures widgets. The level of
customer complaints and accompanying returned products is rising sharply. I need
to understand where to focus my management effort for greatest impact.
I list the problems I have observed in the team, the likely causes and the number of
complaints. I have clustered the problems by root cause:
It is immediately obvious that the greatest source of problems comes from operator
error. In a more complex scenario, it is worth charting the causes and scores to see a
graphical distribution. For this example:
60
50
40
30
20
10
0
Operator Machine Dist. dept.
error error error
From the distribution of errors, I know that I should focus my first efforts on training
the staff. After this, I may wish to have a quiet word with the maintenance department
and distribution department.
Reference
50minutes.com (2015) Pareto’s Principle: Expand your Business! 50Minutes.com.
When to Use It
■ Consider using in conjunction with the Ripple effect (see Tool 39). This method will
help you to identify possible ramifications of your solution in your own area. The
Ripple effect will help you to identify possible effects of your solution across the
wider organisation.
How to Use It
1 Use other methods outlined in this book to create the solution to a problem.
2 Use a fishbone diagram to identify the major effects of the solution.
3 Brainstorm possible further effects of those major effects.
4 Analyse those effects and look for solutions.
5 Amend the original solution or re-evaluate to create a new, more effective solution.
Major Major
effect effect
Solution
Major Major
effect effect
When to Use It
■ The work map is very useful in analysing where your own time goes and discovering
ways of recouping lost time.
■ It can also be a powerful tool to use with a small team working together.
How to Use It
1 On a piece of paper (at least A4 in size) and turned to landscape, draw a small circle
in the centre and put your name in the circle.
2 Consider all the people or groups of people both inside and outside work who
require something from you or have expectations of something at work – it may
be that you deliver goods, services, reports, information to them – it does not
matter what you offer, as long as they have some expectation that you will deliver
something to them. These groups and individuals might include, for example,
your boss, your direct reports, key customers or clients and others. Ranged
around the central circle, draw another circle for each person or group who
requires something from you and put their name inside the circle that represents
them. Note that if several people or groups require exactly the same thing from
you, their names can be entered in the same circle. If there are differences in their
expectations of you, no matter how subtle, draw a separate circle for each one.
Client Client
X Y
Supplier Client
3 Z
Supplier
2 Me Boss
Supplier Boss’s
1 boss
Team
3 Connect each circle to the centre circle with lines like spokes of a bicycle wheel.
Above each connecting line, write a very brief description of what you believe
each of these ‘stakeholders’ requires from you.
Client Client
X Y
Supplier Client
Time
ce
3 Z
ervi
ly su
Oc
at s
ca o
ord sion inf
pply
ate
Gre
ers al r
£ cu
Ac
Supplier Large Keep clients
2 Me Boss
orders $ € Ra happy
ise
rev
lar en
gu $ ue
Re rs £
Direction/
e
delay
o r d
Supplier Boss’s
1 boss
Team
4 Consider how each stakeholder would evaluate your offerings to them. Do they
measure it in terms of quantity, quality, cost or time, or a combination of these?
By each circle, indicate how they evaluate it using Qn (quantity), Ql (quality), C
(cost), T (time).
Ql,T
Ql,T
Client Client
X Y
Ql,T
Supplier Client
Time
ice
3 Z
serv
l
Oc
y su
C,T
ca o
inf
at
ord sion
pply
te
Gre
ers al ra
£ cu
Ac
Supplier Large Keep clients
2 Me Boss
orders $ € Ra happy
Qn,C,T ise
rev Ql
lar en
e gu £ $ ue
Direction/
R rs
e
delay
Qn,C,T
Team
Q,T
5 From each stakeholder circle, draw a line and write on this line what each
stakeholder does with whatever you offer them. For example, if you send
stakeholder X a monthly report, what do they do with the information in that
report? (See completed work map overleaf.)
6 Now go back to the lines connecting each stakeholder to the central circle. If
you believe that what you wrote above the line represents what the stakeholder
expects from you, now write below the line what you need or expect from the
stakeholder in order to provide this. (See completed work map overleaf.)
7 Finally, consider where you spend the bulk of your working time. Shade in the
circles representing the stakeholders who, whether rightly or wrongly, take up
most of your working time. (See completed work map below.)
ion
Ql,T licat
Pub Ql,T !
sure
Not f
Client Client staf
Not
sure X Y re with
! Sha
Ql,T
Supplier Client
Time re!
Pub service
Not
-
Oc
ly su
su
C,T
No ers onal
ion
o
inf
at
ts £
pply
te ular
Gre
Dev ure o
elo ! r a
cu Reg enu
e ort t
EME p in Rep ss
A Ac re
v bo
Supplier Large orders $ € Keep clients happy
2 Me Boss
Timely supply Regular feedback
Ra
Qn,C,T £$ i
Oc se re
e rs me c Ql
or d ti rec as ven
lar lity & Direction/delay og iona ue
Motivation &
productivity
u nit
g
Re h qu
a ion l
i g C,T
Supplier H Boss’s
1 boss Board report
inv est
Re-
Qn,C,T
Team
Q,T
Now you have a picture of your working life, which may prompt a series of questions:
1 How do you know what each stakeholder wants from you? When did you last
discuss it with them?
2 How do you know how they evaluate what you do for them? When did you last
discuss it with them?
3 Do they know exactly what you expect/need from them in order to meet their
expectations? When did you last discuss it with them?
4 How do you know how they use whatever you deliver to them? When did you last
discuss it with them?
5 If you are spending a disproportionate amount of working time with certain
stakeholders, are you neglecting others who would value spending more time
with you?
Notice in the example diagram, some of the expectations are marked as ‘Not sure’ as
the end results of whatever I am providing to the stakeholders. If I am not sure what
they do with whatever I provide, then I must go and speak to those stakeholders and
re-establish what we need from each other and why we are doing what we are doing.
The idea is to question everything. You may discover, for example, that you produce
a detailed report for one stakeholder who needs only a high-level, bulleted summary.
You may discover that you are taking too much time to produce something of quality
when the stakeholder requires something basic, or perhaps requires nothing at all and
simply has not told you (because you did not ask).
Go back and talk to the people you have included in your diagram and discuss
mutual expectations. You will be surprised at how much extra time you can gain from
reducing some of the work you do for them and, in some cases, stopping it altogether.
When to Use It
■ hen you are looking for a new job and choosing the organisations for which you
W
could work comfortably or (if seeking a challenge) change!
How to Use It
Cameron and Quinn’s extensive research into organisational culture suggested that
every organisation, regardless of whether it is in the public, private or third sector
(voluntary, social enterprise, charity), displays a combination of characteristics in four
particular areas, which they named as:
Clan Adhocracy
Hierarchy Market
Clan Adhocracy
(Collaborate) (Create)
Hierarchy Market
(Control) (Compete)
Any two boxes that are diagonally opposite each other are considered to be
diametrically opposed. For example, the greater the clan characteristics displayed by
an organisation, the fewer market characteristics it will display and vice versa.
Cameron and Quinn described the cultural characteristics typical in each area and,
as you begin to understand them, so you can start to choose the type of organisation in
which you would feel comfortable working. Broadly, the characteristics are as follows:
Clan Adhocracy
(Collaborate) (Create)
Friendly and sharing family Dynamic and entrepreneurial
Leaders are ‘parents’ or mentors Leaders are innovative and risk takers
Loyalty and tradition Experimental and inventive
High commitment Leading edge
Emphasis on personal development Emphasis on growth and new resources
Sensitivity to internal and external clients Success is new services or products
Participation and consensus Individual initiative and freedom
Hierarchy Market
(Control) (Compete)
Formal, structured and procedural Results-oriented, getting the job done
Leaders are efficient organisers Competitive and goal-driven
Smooth running is essential Leaders are tough and demanding
Formal rules and policies Emphasis on winning
Stable and dependable service Achievement of measurable goals
Secure employment Success is in market share and penetration
Now imagine a scale of 0 to 50 for each quadrant, starting at the centre of the box and
radiating out towards the corners. Score each quadrant based on its appeal to you
and join the dots.
60 Clan Adhocracy 60
50 50
40
40
30 30
20 20
10 10
10 10
20
20
30
30
40 40
50 Market 50
Hierarchy
60 60
In this hypothetical example, I want a medium high clan score and a high adhocracy
score. I want a low hierarchy score and a medium market score. At a personal level, it
suggests that I do not much like being constrained by rules but enjoy the freedom to
think and act for myself; I am a reasonable, but not strong, team player; I am moderately
driven by targets but do not like too much pressure.
Now try to discover as much as you can about the company that you are thinking
of joining and overlay on top of your diagram a picture of how you see that company
using a different style or different coloured pen. You might like to add a key to indicate
which is your score and which relates to the company. How would you score them
in each area? How close is your ideal to what you perceive as the actuality of the
company? Where are the gaps? Can you tolerate them? Would you be applying for a
sufficiently senior position to be able to change anything?
60 Clan Adhocracy 60
50 50
40
40
30 30
20 20
10 10
Hierarchy 10 10 Market
20
20
30
30
40 40
50 50
60 60
Me
Company
If there is a close match, then the company looks like a good choice for you. If there
are discrepancies, then you need to think carefully about whether it is for you. Look at
the following points for guidance.
Reference
Cameron, K.S. and Quinn, R.E. (2011) Diagnosing and Changing Organizational Culture
Using the Competing Values Framework. San Francisco: John Wiley & Sons.
Tool 46 Timelining
When to Use It
■ When a group needs to plan and prioritise its actions.
How to Use It
Round 1 – major achievements
1 Around a room, post flipchart sheets, each headed with a date – the first shows the
date six months from now, the second a year from now, the third eighteen months
from now, the fourth two years from now – as far ahead as you believe you can
look or need to plan.
2 Ask participants to walk around the flipchart sheets, in complete silence, staring
at each date and imagining what they could achieve/must achieve/would like to
achieve (as appropriate) by then, then walk to the next and the next in sequence
until they cannot imagine their work any further into the future.
3 When they reach the latest date at which they can visualise something being
achieved, they should write on the flipchart sheet a brief description of the
milestone they intend to reach by this stage.
4 Participants then walk back in the opposite direction, writing on each flipchart
sheet the major achievement(s) they expect by each date in turn. Remember that
this is all done in silence.
Round 2 – milestones
1 Participants walk to the flipchart displaying the furthest date (in the future) at which
they had marked a milestone achievement.
2 Then they consider what has to happen at earlier dates to make the end date
feasible.
3 They walk back and write on each flipchart in turn the major phases that must be
finished at each specific date in order to achieve their end goal. Again, this is done
in silence.
Round 3 – actions
Round 4 – people
1 Finally, the participants are allowed to speak! Participants should consider who
must undertake each of the actions in round 3.
2 They should seek out the appropriate people (if they are in the room and participating)
and take them to the appropriate flipchart sheets, ask them to undertake the work
in question and, with their agreement, assign the actions to them by putting their
names or initials on the appropriate sticky notes.
Round 5 – assimilation
1 Everyone now walks through the flipchart sheets from earliest to latest date, reading
the milestones, actions, assigned names and ultimate achievements and double-
checks the feasibilities and dependencies, asking permission from others to make
changes, as appropriate.
2 Take photographs of each flipchart sheets in sequence and have them typed up as
a high-level action plan, to be discussed (if necessary) in more detail at a later team
meeting.
Reference
The provenance of this method is unknown. I am indebted to Angela Peacock and
Jeremy Lewis of the People Development Team (www.pdtglobal.com) for showing
me the technique and demonstrating it so powerfully with clients.
When to Use It
■ When attempts to solve a problem have failed or solutions have not been
forthcoming, it is often because the wrong question is being asked, or the problem
is badly framed. One question can help the participants to reframe a problem as a
question so that it is easier to find a viable solution.
How to Use It
1 Outline the problem in the broadest terms, answering participants’ questions to
ensure that everyone understands it fully.
2 Each participant then frames the single question that they believe needs to be
answered first to start to create a solution. Participants write their questions on
sticky notes and post them on a wall or a flipchart.
3 Read out each question in turn and ask participants to vote for the question that
best encapsulates the problem to be solved. You may choose to vote by a show
of hands or by placement of sticky coloured dots. Participants may vote for any
question except their own.
4 When everyone has voted, read out the question that gained the majority of the
votes.
5 Ask the group whether it needs to be refined in light of the other questions – is
there anything missing that would make solution finding easier?
6 Now you have the final question, use other methods outlined in this book to
resolve it.
7 It may be that reading out all the questions suggests that there are sub-questions
or sub-topics to be explored. Discuss with the group which other questions are
worth exploring, or use the voting system to pick up, say, the second and third
most popular questions as voted by the participants and explore those, too.
When to Use It
■ hen you are starting a new project and could benefit from the advice of more
W
experienced people.
■ When you are facing a problem that others have faced in the past.
■ When you are planning a project similar to one that another group has been
involved in or even completed.
How to Use It
Before the peer assist session:
1 Determine who has experience of the topic to be discussed.
2 Email them to present your purpose and plan for the session.
3 Set a date for the session.
Variants
If a number of people are involved in a new project and seek assistance, you may
choose to divide the large group into smaller, more manageable groups and have
parallel discussions with one presenter and one facilitator per smaller group. Follow the
format above but add in a plenary session between steps 4 and 5 in which the whole
group convenes for a plenary sharing of information and ideas.
Reference
There are many articles online about peer-assisted learning, but most of the books
focus on classroom methods in school.
When to Use It
■ This is useful after more formal training to keep a peer group together so that they
continue to learn and assist each other in problem solving, decision making and
learning.
How to Use It
1 Establish a relatively small, mutually supportive group of four to eight people, ideally
peers from a number of departments.
2 State clearly the organisational problem (or opportunity to be developed).
3 Group members ask clarifying questions.
4 Group members now focus on asking the right questions to help the presenter to
learn, rather than on finding solutions, exploring both what is known and what is
not yet known and using questions to break away from received wisdom about
the past and ‘how we do things around here’. Good open-ended questions,
asked one at a time, rather than ‘stacked’ work best.
5 Members are encouraged to be challenging in their questioning to help the
presenter to see an issue from other perspectives whilst remaining supportive
and attentive to the presenter’s feelings. They must not give personal solutions or
work from their own, personal agendas. Examples of good questions are:
■ ‘Could you say a little more about that?’
■ ‘Are you saying that . . . ?’
■ ‘What happened after that?’
■ ‘Have you considered exploring X?’
References
Butler, L. and Leach, N. (2011) Action Learning for Change: A Practical Guide for
Managers. Oxford: Management Books 2000 Ltd.
Pedler, M. (2013) Facilitating Action Learning: A Practitioner’s Guide. Maidenhead:
Open University Press.
When to Use It
■ To elicit the experiences of a group of people who have already done something in
an area in which you are just becoming involved.
■ To test the viability of an idea before implementing it.
■ To understand better how to implement a particular change at work.
How to Use It
1 The presenter discusses an idea, a challenge, a topic in which he/she is seeking
help.
2 The facilitator asks a number of open questions, designed to elicit experience
in the area of discussion and allows sufficient time for participants to tell their
stories, which illustrate their personal experiences of the issue.
3 The presenter may also question participants to get them to delve deeper into
their stories.
When to Use It
■ Use it to test the efficiency of a process that involves a number of participants in
different functional areas.
How to Use It
1 Select the business process to be analysed.
2 State the specific process that you are working on.
3 Identify each participant in the process that you are analysing.
4 List each participant in the left column of the diagram. Each participant is given a
horizontal row (swim lane).
5 List the steps in the process as it is currently executed.
6 Map each step to the participant who executes it.
7 Analyse the diagram and assess whether any part of the process can be
improved. For example:
■ Are there any missing steps?
■ Is there any duplication of effort?
■ Is there any step that adds no value?
Issue
Controller
ticket
In our example, you can see that both picker/packer and driver load the truck,
which reduces the number of people in the warehouse picking and packing. The driver
and the store manager unload the truck together. This may be a useful way of double-
checking the inventory, but it may be inefficient.
Having analysed the diagram, you may choose to draw another swim lane diagram
to show how the process could/should work. This may result in, for example, the
removal or addition of steps, removal or addition of participants in the process or
combination of steps.
Variants
You may want to start by creating a swim lane diagram for the highest-level processes
and then create new diagrams to explore one or more sub-processes in additional
detail.
Reference
Damelio, R. (2011) The Basics of Process Mapping. New York: Productivity Press.
Large Group
Problem-
Solving
Techniques
When to Use It
■ When time is limited and you need a lot of ideas but have little time for discussion.
■ When people are reluctant to speak out in front of the group.
The method works particularly well in cultures or organisations where people are
reserved and prefer to contribute anonymously.
How to Use It
1 Distribute slips of paper or sticky notes to each participant.
2 Ask them to write ideas on the topic being discussed, one idea per slip.
Contributions are made anonymously.
3 You may offer to summarise the responses after the event (which encourages
participation).
4 Collect the slips when you see that participants are running out of ideas.
5 Outside the event, collate and sort the answers by subtopic or theme.
6 After the event, send a summary of ideas with a thank you email to participants.
Reference
Dettmer, H.W. (2003) Brainpower Networking Using the Crawford Slip Method.
Bloomington: Trafford.
When to Use It
■ For strategic planning.
■ For organisational design.
■ For discussion of issues/problems/decisions that cut across departmental
boundaries.
How to Use It
1 Agree on the issue(s) to be discussed – these should be subtopics of a bigger idea.
2 Divide the group into smaller groups, maximum seven per group, plus a recorder
(who is also the small group facilitator).
3 Assign an issue to each group.
4 Each group brainstorms its issue.
5 The recorder facilitates and records all ideas.
6 At a given time/signal, the recorder moves to the next group.
7 The recorder reviews the issues/responses of the new group.
8 The groups begin brainstorming again around a new idea, building on the thinking
from the last idea.
9 Repeat steps 5 to 8 until each group has discussed all the issues.
10 Allow the recorders/groups time to draw all the ideas together into key themes or
strands.
11 In plenary, ask recorders to present the key ideas coming from their groups. You
may need to rank the ideas.
Tool 54 Starbursting
When to Use It
■ Before attempting to find a solution to a complex issue with many sub-strands.
How to Use It
You can use this technique on your own, but it is more fun and more productive with
one or more small groups of, say, four people per group.
1 Create a six-pointed star on a piece of paper – you may choose to use ordinary
office paper or, for larger groups, flipchart paper. Label the points of the star with
question words: Who? What? Where? Why? When? How?
Who?
How? What?
When? Where?
Why?
2 Brainstorm questions about the topic, starting with each of the question words
around the star. Generate as many relevant questions as you can.
3 Do not attempt to answer the questions. At this stage, you are only generating
questions.
4 Write the questions so that they radiate from the points of the star.
5 If several groups are taking part, ask one group to read all its questions,
prompted by a particular question word, and then ask other groups to add any
questions not posed by the first group. Now move to another group and let them
lead with their questions, prompted by another question word, with other groups
adding to it. Repeat for each question word.
6 Collect the Starbursting diagrams and, after the session, collate the questions
and distribute them to participants.
Variants
■ ou can either generate one set of questions or use each set of questions to
Y
stimulate the creation of a new set.
■ Break a large group into smaller groups. Either let each group explore the same
issue or give different issues (or different aspects of the same issue) to each smaller
group and ask them to share their questions in plenary.
How may people do we want to attend? What are the current topics of interest?
How long do we have to plan it? What’s our budget?
Who?
How? What?
Attract more
conference
delegates
When? Where?
Why?
When are the school holidays? Where does our target audience work?
When are the public holidays? Where would be a good, central location?
When to Use It
■ For strategic planning.
■ For organisational design.
■ For any decision making that will affect people cross-functionally.
How to Use It
1 Bring the group together in a circle.
2 Distribute paper to each participant.
3 Welcome the participants and explain the process.
4 Invite anyone with a concern or an issue to be resolved to write it on a piece of
paper, come into the centre of the circle and announce the concern to the group.
5 Those who express concerns are described as ’conveners’ and, having
announced their concerns, each places their paper on an ‘agenda’ wall with a
place to meet and a time slot. Ideally, this should be prepared in advance of the
session, with small placards on the wall listing each breakout room/area, so that
the conveners can place their written concerns under a location name and add
their start time.
6 Participants note the times and locations of the sessions that interest them.
7 The conveners start their sessions and interested parties come and join them.
8 Each group appoints a recorder to capture the important points and post their
reports on a ’news wall’. Reports will be collated and fed back in a plenary
session.
9 After a break, groups might move to a convergence stage in which they attach
actions plans to the points raised.
10 The group comes back together in a circle in which participants are invited to
share comments, insights and agreed actions arising from the process.
If you find yourself in a breakout meeting to which you can contribute nothing or in
which you are learning nothing, then exercise the Law of Two Feet and move to another
session to which you believe you can contribute something.
The principles of open space
The originators of Open space believe that:
■ Whoever comes are the right people.
■ Whenever it starts is the right time.
■ Whatever happens is the only thing that could have happened.
■ When it is over, it is over.
There are some flaws in these basic principles. In reality, there may be too little time for
the right people to take part in each small group discussion and the timing may not be
appropriate for everyone. The other two ideas suggest some kind of inevitability about
the process and outcomes that somewhat fly in the face of common sense.
Reference
Owen, H. (2008) Open Space Technology: A User’s Guide. San Francisco: Berrett-
Koehler Publishers.
When to Use It
■ For strategic planning.
■ For organisational design.
■ For any decision making that will affect people cross-functionally.
How to Use It
1 Setting: Setup is usually café style, with small tables for four or five people. Provide
paper, pens and, possibly, a ‘talking object’ (only the person who is holding it may
speak). Each table has a host, who usually stays at the same table throughout the
process.
2 Welcome and introduction: The event host welcomes everyone, sets the scene
for the discussion and describes the process.
3 Question: A question is posed, related to the main topic of the discussion.
Reference
Brown, J. and Isaacs, D. (2005) The World Café: Shaping Our Futures Through
Conversations That Matter. San Francisco: Berrett-Koehler Publishers.
When to Use It
■ When you need to move relatively quickly from problem solving to action.
■ For strategic planning.
■ For organisational design.
■ For any decision making that will affect people cross-functionally.
How to Use It
1 Everyone meets in a circle to understand the purpose of the session.
2 Participants consider in silence if there is a question they would like to explore.
3 They are asked to share it and invite others to work with them on it. Those who
do not raise questions are asked to work with those who do.
4 Each person with an issue to explore stands up, states their issue and writes it on
an agenda, then chooses the number of the table at which they will meet. Ideally,
each table should have a host and three or four other people.
5 Three rounds of conversation for 20 to 30 minutes each, each focusing on a
specific question to broaden and deepen the process before converging. A five-
minute break between rounds.
Round 1: What is the quest behind the question? Dig under the surface of what
we already know to understand the initial question better.
Round 2: What is missing? What do we need to know to make the picture more
complete?
Round 3: Next steps and key learnings. In the final round, the convener remains
at the table and the groups rotate to the next table to hear the thoughts so far
and offer fine-tuning and help. The hosts and participants assimilate what they
have learnt and take away actions.
6 Feedback in a circle. Everyone gathers in a seated circle in which the hosts
describe what happened at their tables and what they will take away from the
discussions. If time permits, others may wish to share their experience of the
activity. To control the flow of conversation in the feedback session, some groups
use a ‘talking object’ – the object can be anything at all, and only the person
holding it may speak. For some, this may be taking things a little too far: it has
the advantage of ensuring that people do not interrupt each other, but can make
discussion a little stilted and over-formalised.
Problem-
Solving
Business
Games
S
ome people believe that ‘games’ have no place in serious organisations.
Meetings are serious events with a serious purpose. I could not disagree more
strongly! Children learn through play and so do adults. Our problem is that we
do not necessarily allow adults to learn the same way as children. Children learn by
play, by activity and by making mistakes. Rather than give up at the first sign of failure,
they persevere. How many of us would pursue the art of walking if it were something
we learnt to do only as adults? At the first fall, most of us would think, ‘Well, I’m not
trying that again!’
The art of using business games is to ensure that a game has a serious purpose,
and that the purpose either becomes apparent during play, or is brought to the surface
in the debrief that follows the game.
The trick of introducing games into ‘serious’ organisations is not to call them
games, but ‘activities’ and do them anyway. I have been designing and using games in
training and meetings for years and, only very occasionally, have I encountered people
unwilling to join in.
If you can use a game to stimulate thinking and create solutions to problems, then
it is as viable as any other problem-solving technique. (Just do not mention the word
‘game’!)
When to Use It
■ hen a group is struggling to see how it can improve its working methods, this role-
W
playing game can be enormously helpful.
How to Use It
Ask small groups to project themselves into the future, imagining that it is their
retirement day and they have, throughout their working lives, created a great place to
work, a highly dynamic team, a place with seamless and efficient tools and processes
(or whatever is pertinent to the group).
They now have to imagine that they are going to make a presentation to a group of
new joiners to the team/department, explaining what they did to make it so good. They
actually present to the larger group.
In presenting the ideal future, effectively by looking backwards, they free themselves
from the constraints they would see if simply asked to look forward. Small groups
prepare, present to others in plenary and, after each small group has presented, ideas
are ranked, voted on and explored in more depth to turn them from abstract concepts
into practical reality.
gap between the present and future will seem unbridgeable. However, in imagining a
future without known constraints, they start to believe that real change is possible and
from the often bizarre ideas suggested comes an imaginably better future.
Try using the PMI technique (see Tool 4) to explore in more detail some of the seeds
of possibility sown here.
Tool 59 Convince Me
When to Use It
■ hen there are opposing forces in an organisation and simple discussion or debate
W
has not yielded a solution.
How to Use It
1 Two teams are asked to adopt opposing ideas of how to solve a problem. Whether
or not the stance they take reflects their own thinking does not matter for these
purposes. Their job is to produce a well-reasoned argument from the perspective
allocated to their team.
2 They stand in lines facing each other, at opposite sides of a room.
3 Anyone can present an argument to persuade the other team to come over to
their point of view.
4 As individuals hear a compelling argument, they take a step towards the other
team.
5 When the majority of members of one team have stepped over the halfway point
between the two teams, the first round is over.
6 Now small, mixed groups work together to discuss how the winning solution may
be implemented.
Tool 60 Evolution
When to Use It
This is a tool for senior decision makers working in conjunction with functional leaders
at a time when there is concern about the direction an organisation is taking; for
example, when there has been:
■ a downturn in profits;
■ a decrease in take-up of services;
■ a fall in the level of charitable contributions received;
■ some reputational damage to the organisation;
■ anything that signals that the organisation is not working as well as it should.
How to Use It
Teams work to establish the aspects of their business that are strongest and so most
likely to survive:
■ What can they do to ensure that survival?
■ How can they develop the strongest areas to be stronger?
■ Is there a danger in focusing too much on a limited range of areas of the
organisation and so missing something important elsewhere?
■ What happens to the weaker areas?
■ Can they be strengthened or should they be removed?
■ What would be the effect (in cost, time, materials, etc.) of shoring up the weaker
areas?
When to Use It
■ To resolve complex problems involving many stakeholders.
How to Use It
1 A large group of people from a mixed range of grades is broken into smaller groups.
2 Each small group imagines itself to be a team of investigative journalists.
When to Use It
■ When you need a variety of views on a critical or complex organisational issue. The
preparation for this technique can be time-consuming and it is a non-trivial method
of examining an important issue in depth before reaching one or more decisions on
how to proceed.
How to Use It
1 All interested parties are brought together to discuss an organisational problem.
2 Brainstorm solutions to the problem and use a ranking method to assess the
favourite solution.
3 Appoint a recorder and judge.
4 Divide the remaining group into two smaller teams – one for the prosecution and
one for the defence.
5 Each team must appoint a leader who will, ultimately, represent it in the trial.
6 The prosecution team must amass as much evidence as it can to find flaws in the
solution, and appoint key witnesses from within the team to speak on their behalf.
7 The defending team must amass as much evidence as it can to support the
solution, and appoint key witnesses from within the group to speak on its behalf.
8 The trial is convened.
9 The judge asks the lead prosecutor to present the team’s case against the
solution (the aim being to expose its flaws). The prosecutor may call witnesses to
support the team’s case.
10 At the judge’s behest, the recorder will note key arguments in favour of the
solution on a flipchart headed ‘For’, visible to all participants.
11 The lead defender presents the case in support of the solution (the aim being
to highlight its benefits). The defender may call witnesses to support the team’s
case.
12 At the judge’s behest, the recorder will note key arguments against the solution
on a flipchart headed ‘Against’, visible to all participants.
13 When each side has presented its case, the lead prosecutor and lead defender
may summarise their arguments.
14 At this point, the official trial is over and the evidence is assessed using the force
field analysis method (see Tool 1).
When to Use It
■ For planning – whether strategic or operational.
■ For organisational design.
How to Use It
1 Divide a group into two teams. One team is the hares, the other the tortoises. Each
team works independently of the other to discuss solutions to the same business
problem.
2 Hares must find quick wins, easy solutions and rapid approaches to solving the
problem. Tortoises must find medium- and longer-term solutions to the same
problem.
3 Each presents to the other in plenary and, after a facilitated discussion on the
merits and demerits of each suggestion, ideas are ranked/voted on and, where
possible, combined.
When to Use It
■ When standard approaches to a problem are not yielding any new insights.
■ With creative groups who have rare opportunities to demonstrate that creativity.
■ With non-creative groups who need a way of breaking away from logical,
structured thinking.
How to Use It
1 State the problem to be resolved.
2 Participants sketch whatever comes into their heads as they think about the
problem. They can focus on any aspect of the problem and illustrate it however
they wish.
3 Display their artworks in a ‘gallery’ and, as participants view each other’s
pictures, they use them to stimulate their thinking about solutions to the problem.
4 Facilitate a discussion to allow participants to air the ideas and solutions that have
come out of their tour of the ’gallery’.
Variants
Whilst participants are discussing a problem and possible solutions, ask someone with
artistic ability to sit back from the main discussion and sketch anything that occurs to
him/her, then display the artist’s pictures. Participants study the pictures and see and
discuss the new ideas they stimulate.
When to Use It
■ hen a team is struggling to find insight into organisational issues using more
W
conventional methods.
How to Use It
1 Compile and print a list of proverbs. You might like to include, for example:
■ ‘Too many cooks spoil the broth.’
■ ‘A little bit of knowledge is a dangerous thing.’
■ ‘Better safe than sorry.’
■ ‘A rolling stone gathers no moss.’
2 Distribute the list to participants, who may work alone, in pairs or threes.
3 Present the problem to them and ask them to use the proverbs to stimulate
thinking about it, whether to create solutions or simply to ensure that they are
asking the right questions.
For example:
■ ‘Too many cooks spoil the broth.’ Where do we have too many people involved
in a process that requires fewer people’s involvement?
■ ‘A little bit of knowledge is a dangerous thing.’ Where do our people lack
information, knowledge or skills necessary to do their jobs better?
■ ‘Better safe than sorry.’ Are we managing risk appropriately? Are our health
and safety measures appropriate? Are we being too risk-averse/over cautious
in some areas?
■ ‘A rolling stone gathers no moss.’ Are there ways in which we can act quickly
and effectively, with low risk, to get ahead of our competitors?
When to Use It
■ When bureaucracy seems to be overshadowing common sense.
■ When ’the way we do things here’ has not been re-evaluated for a long time.
■ When the organisation is in danger of becoming a tick-box culture, driven by
process instead of using minimal processes to avoid chaos and using the
processes as a stepping stone to higher performance.
How to Use It
1 Small groups are each allocated a process, procedure or a set of house rules.
2 They must decide on its original purpose, then effectively tear it up and start
again with a simplified set of rules or governing principles that address the original
purpose or problem.
3 Each group presents in plenary and the larger group determines whether:
■ the new rules/principles are an effective replacement for the original;
■ some of the ideas the activity generates can be incorporated into the original
rules to simplify or refine them;
■ in fact, no rules would be the best option, leaving an issue to the integrity of
those involved rather than dictating how it should be done.
Tool 67 Documentary
When to Use It
■ To explore a business problem creatively and in depth.
How to Use It
1 Split a larger group into smaller teams.
2 Allocate a business problem to each team (either distinctly different problems or
subsets of the same problem).
3 Give teams a time limit in which they have to create a radio- or TV-style
’documentary’ that explores the issue and possible solutions to it
4 Each team enacts its documentary in front of the larger group combining
presentation and interviews.
5 You may then choose to use other methods to assess or further explore the solutions
presented and, if appropriate, vote on the best one or best combination of solutions.
When to Use It
■ hen a number of smaller groups has worked on the same problem and believe
W
their solution is the best.
How to Use It
1 Appoint a panel of experienced people and allocate large amounts of notional
money to each one of them – say, 100,000 of your local currency.
2 Small groups each prepare a solution to a different, pressing business problem,
then one or two from each group pitch their solution to the panel of experts.
3 Give each group a time limit (of, say, five minutes) for their pitch.
4 Experts question the presenters about their solutions and can then allocate their
notional money to ideas based on their merit, or choose to opt out if they believe
a solution has no real merit (is not worth pursuing). An expert refusing to invest
explains the reasons not to invest and declares, ‘I’m out!’
5 The solutions with the highest ‘investment’ of points are then taken back to the
wider group and other techniques used to explore how they can be implemented
in practice.
Variants
Each group works on the same business problem and presents its suggested solution
to the experts. Experts allocate notional money (points) to each solution. The one with
the highest investment is then developed in practice.
Offer a small prize to the ’winning’ team.
Sharing and
Implementing
Solutions
Sharing Solutions
I
t is all very well involving groups of people in creative processes to generate ideas,
solutions to problems and new ways of working. But what happens when you have
those ideas? How do you determine which are worth pursuing?
In this section, you will find:
■ a wealth of methods of collecting (sometimes described as ‘harvesting’) ideas
generated in a collaborative problem-solving session;
■ ways of ranking those ideas and voting on them so that the best of them can be
implemented.
■ Teams present their three/five top tips. Again, this may lead to repetition or side
discussions.
■ Teams present how to do something entirely wrong, so that the rest of the group
can learn how to do it right.
■ ‘The most important thing is . . .’ and ‘The least important thing is . . .’
■ Groups present opposite viewpoints as a precursor to discussion. This is useful in
ensuring a well-rounded, informed debate.
■ ‘Taboo’ – describe a subject without mentioning certain key words (determined in
advance by the facilitator). The rest of group must guess the words being described.
■ Create an aide memoir or mnemonic to help others to remember key points.
You may choose to photograph flipcharts and distribute the photos after the event, so
that everyone feels that they made a valid contribution and ideas of merit that did not
make the ‘cut’ are not lost.
Graphical ’harvesting’
In some circles, capturing ideas from a group is described as ’harvesting’. Drawings,
diagrams and cartoons can be a wonderful way to capture ideas and often stimulate
further thinking: our left brains handle the rational side of our discussions and pictures
tap into the creative, right side of the brain to help us to make more connections.
You do not have to be a great artist to capture ideas. Take a look at these videos
for ideas:
http://bit.ly/1Ak6lVL
http://bit.ly/1bdspN9
Tips
■ Put flipchart sheets on tables or use paper tablecloths during problem-solving
meetings. Encourage people to scribble and sketch as they discuss an issue. Often,
new ideas are stimulated by the pictures.
■ Put two or three flipchart stands in a row, so participants can capture big ideas
across several charts in parallel.
■ Ask if participants can think of a metaphor for the subject they are discussing and
use it as a visual representation or backdrop for the harvested ideas.
■ Ask one or two participants with reasonable artistic flair to capture ideas during a
conversation or discussion.
■ Treat the visual harvest as a giant doodle, focusing more on capturing ideas than
on the beauty of the artwork, and you will find it starts to flow.
■ Look online for symbols and have those to hand when you create the graphical
harvest.
■ Make your pictures colourful so they are attractive to participants.
Implementing Solutions
You have framed a problem beautifully, gathered together a team of interested parties
to help you resolve it, chosen and executed the ideal problem-solving method and
your solution creates a need for change – change to a system, a process, a method
of doing something, a way of thinking, the structure of a team or even an organisation.
Having the ideal solution is not enough – now you have to sell the idea to others.
Whilst this book is about problem solving rather than change management, the act
of implementing a solution can be a major problem in its own right, so let us explore
some ways of implementing solutions and making them work.
Let us start by dismissing a major myth about change management. This is the
change curve, espoused by change managers and management consultants many
years ago to describe the stages that people go through when they encounter change
at work. The curve was described originally by Elisabeth Kübler-Ross1, an expert in
‘near-death studies’, who worked extensively with people told that they had a terminal
illness. She talked about the five emotional stages (denial, anger, bargaining, depression,
acceptance) that those who knew they had little time to live might go through.
Significantly, she said that not everyone would go through all the stages, nor necessarily
in a prescribed order. Management consultants seized upon this and determined
that, if dying people go through these stages (after all, dying is a big change . . .),
then people facing change at work must go through the same stages. In my many
years working with two of the world’s biggest consultancies and training people who
faced change, I rarely saw anyone conform to this curve, unless their livelihood was
threatened. The truth is, if an organisation has good managers and leaders, rarely
should any change be a surprise: good managers and leaders communicate constantly
with their staff who, as a result, know what is happening in their organisation.
In reality, there probably are five reactions to change, which we outlined briefly
earlier in reference to preparing the ground for problem solving – but they are not those
outlined by Kübler-Ross! Now let us look at them in more detail:
Indifference: A remarkably high number of people are indifferent to change. They have
seen it all before! Change is not new, not remarkable and often not terribly interesting.
The most emotional statements you are likely to hear from them are ‘Whatever!’ or
‘Here we go again’.
1
On Death and Dying (1969)
Active acceptance: There are many reasons why someone might actively (and vocally)
accept a change, some perhaps surprising. These include:
■ They see that it is a good idea.
■ They do not know any better.
■ They see benefits for themselves in the new regime.
■ They trust their manager who has got things right before and has probably got it
right this time.
■ They are sycophants who will agree with their manager for purely self-serving
reasons.
■ They are swayed by one of their trusted colleagues who agrees with the change.
■ Most of their friends believe the change is ok, and they are swayed by peer
pressure.
In a sense, it does not matter what motivates the active acceptor to agree with the
change – they make all the right noises and are prepared to vocalise their support for
the new idea.
Active resistance: There are many reasons why someone might actively (and vocally)
resist a change. These include:
■ They see that it is a bad idea.
■ They know that it will not work. They have a long corporate memory and have
seen similar schemes fail in the past. They are not negative in their outlook, but
realistic in their appraisal of your solution. Enlist them as change agents – they will
help you to make it work.
■ They see no benefits for themselves in the new regime.
■ They do not trust their manager because of past failures, predicting that this will
work no better than the last hare-brained scheme.
■ They are swayed by one of their trusted colleagues who disagrees with the
change.
■ Most of their friends believe the change is flawed and they are swayed by peer
pressure.
You need to understand at an individual level why these people resist the change and
are prepared to vocalise their resistance, then deal with them individually.
Passive acceptance: Passive acceptors accept the change and simply get on and
implement it. They do not talk about it but you will find them quietly doing what you
have asked them to do. It can be useful to get them to vocalise their support of the
change to sway some of the indifferent ones towards some level of acceptance.
Passive resistance: Passive resistors are the most dangerous people in times of change.
Publicly, they may appear to agree to the change but, privately, will either do nothing to
implement it or subtly sabotage it. You need to discover what drives this behaviour in
them individually and manage them one at a time through the change process.
Once you are aware of individuals’ reactions to change, you can plan your approach
to talking to them. The key here is to understand individual reactions rather than
expecting that a whole team will react the same way.
Here are some simple ideas to help you to implement your solutions:
■ Involvement: Involve those who will be affected by the change or have a political
interest in it from the outset. Many of the problem-solving techniques described
here can involve people at all levels without giving a bigger voice to the more senior/
vocal/political. Their involvement brings them in to the process and, effectively,
denies them the right to change the outcomes because they were part of the group
that agreed on how something should be done (and there will be many witnesses
who saw them agreeing!)
■ Consultation: Gather together at the outset anyone who may be affected by your
proposed changes/solutions and use the force-field analysis to explore what may
help/hinder the implementation of your solution. This way, those affected forfeit
the right to say that they were not consulted. Of course, if you involve them in
creating the solution at the outset, they have already forfeited this right!
■ Leadership buy-in: Get leadership buy-in from the outset, either by involving
them in the problem-solving process or working with them between crafting and
implementing your solution.
■ Timing: Pay attention to timing. People are tired of constant change. Wait until the
time is right for your idea rather than being carried away on a tide of enthusiasm
because it is high on your agenda.
■ Context: Contextualise everything. When people understand why something is
necessary, they are more likely, if not to support it, then at least to step out of the
way to allow it to happen.
■ Talk to them as adults: Do not patronise people. Often, in times of change,
managers and leaders adopt a parental stance and treat their staff like stupid
children. If you are having grown-up conversations all the time with your staff,
change will not come as a surprise and, even when the results of the change may
be difficult to accept, it is far easier to explain them if you have (and maintain) an
adult relationship with your staff.
■ Translate strategy into practice: Remember that strategic change has to be
translated into practice. If you are relatively senior, you may be privy to strategic
conversations in which your staff members take no part. Your staff suffer the
fallout of your strategic deliberations without being part of the process and may
not understand the reasons why certain decisions have been made. Explain them
in purely practical terms. Pre-empt questions like, ‘Can you help me to understand
this?’ and ‘What does this mean in practice?’
■ Plan it: Plan the implementation of your solution as rigorously as you can to avoid
false starts and the resultant loss of credibility.
■ Play it down: Remember that most of your staff will not be frightened of change,
but indifferent to it. Do not make a big issue out of something that does not have
a huge effect on your staff or colleagues. It is important to you, but may be of little
consequence to them. Making a fuss of something is more likely to arouse strong
emotions than being low key.