The 10 tools every innovation team should know

An innovation team does not need a hundred tools. It needs about ten that between them cover the whole arc: understanding a problem, framing it, generating options, choosing, testing and learning. The ten below do that. For each one: what it is really for, and the trap that makes it fail.

If you are just starting out, begin with the five methods every team should learn first. This list is the next step: the working kit a team grows into over its first year.

Understanding the problem

1. Stakeholder interviews: the fastest way to stop guessing.

Talking to the people who live with a problem replaces opinion with stories. A good interview asks about specific past events, not hypothetical futures, and listens more than it explains. The trap is interviewing whoever is easiest to reach and asking whether they like your idea. Recruit by behaviour, ask about the last real time, and read our piece on the research mistakes that waste interviews before you book anyone. Guide: stakeholder interviews.

2. Experience mapping: one picture of what people actually go through.

A journey or experience map lays out the stages someone passes through, what they do, think and feel, and where it goes wrong. It is the tool that lets five departments see one experience at the same time. The trap is drawing it from memory in a workshop and printing it. Build it from evidence, limit it to one person and one goal, and finish with owned fixes. Our article on journey maps that lead to change walks through it. Guide: experience mapping.

3. Five whys: the cheapest root-cause tool there is.

Asking "why" repeatedly, usually credited to Sakichi Toyoda and made widely known through the Toyota Production System, moves a team from symptom to cause in a few minutes. The trap is stopping at a person ("the officer made a mistake") or following only one chain when there are several causes. Stop when you reach something you can change, and switch to a fishbone diagram when the causes clearly branch. Guide: five whys.

Framing the challenge

4. "How might we" questions: turning a complaint into a brief.

A "how might we" question reframes a problem as an open invitation to solve it. The phrasing is generally traced to Min Basadur's work at Procter & Gamble in the 1970s and later spread through design firms. The trap is writing it too wide ("how might we improve customer experience") or too narrow, with the solution already inside it. Aim for a question that rules some things out and still allows many answers. Guide: how might we. Examples, good and bad, are in 10 "how might we" questions.

Generating options

5. Brainwriting: ideas from everyone, not only the loudest.

In brainwriting, people write ideas silently and pass them on for others to build on. The best-known version, 6-3-5, was published by Bernd Rohrbach in 1968: six people, three ideas each, five minutes per round. It works because quiet and junior people contribute on equal terms and nobody anchors the room early. The trap is skipping it because the group "prefers discussion". Discuss after, not before. Guide: brainwriting.

Choosing

6. Impact-effort matrix: a first cut, honestly made.

Plotting options on two axes, value against effort, helps a group sort a long list quickly and spot the obvious quick wins and money pits. The trap is treating its output as a decision. Positions on the matrix are guesses unless someone has evidence, and enthusiasm tends to push favourite ideas to "high impact". Use it to shortlist, then apply a more careful method to the shortlist. How to prioritise ideas compares the options. Guide: impact-effort matrix.

7. Assumption mapping: knowing what you are betting on.

Every idea rests on assumptions about what people want, what is feasible and what the organisation will support. Assumption mapping lists them and places them by how important they are and how much evidence you have. The few that are important and unproven are what you test first. The trap is listing only comfortable assumptions. Ask, "What would have to be true for this to fail?" Guide: assumption mapping.

Testing

8. Paper prototype: the cheapest way to watch an idea meet a person.

A sketch on paper of a form, screen, letter or counter layout, put in front of a real user, shows you in an afternoon what months of debate would not. Carolyn Snyder's book Paper Prototyping (2003) remains a practical reference. The trap is polishing it. The rougher it looks, the more freely people criticise it. Test what people do with it, not what they say about it. See the cheapest prototype you can make this week. Guide: paper prototype.

9. Premortem: failure, imagined in advance.

Before committing, the team imagines that the project has failed and writes down why. Gary Klein described the technique in the Harvard Business Review in 2007. It works because it gives people permission to voice doubts they would otherwise keep to themselves, especially in hierarchical settings. The trap is running it and then filing the list. Turn the top risks into actions or tests with owners. Guide: premortem.

Learning

10. Retrospective: the habit that makes every other tool better.

A short, regular look back at what worked, what didn't and what to change next time. It is the tool that turns a team's experience into capability. The trap is making it a complaints session or skipping it when the team is busy, which is exactly when it is needed. Keep it short, end with one or two specific changes, and check next time whether they happened. Guide: retrospective.

Do's and don'ts

Do

• Learn each tool by using it on a real problem, not a training exercise.
• Pair tools: interviews feed the map, the map feeds "how might we", ideas feed the matrix.
• Write down what each session decided, not only what it produced.
• Revisit a tool after using it: what would you change next time?

Don't

• Collect tools for their own sake. Ten used well beat fifty used once.
• Run a tool because it is in the plan when the situation calls for another.
• Let the canvas become the output. The output is a decision or a test.
• Skip the understanding stage because "we already know the problem".

Illustrative example

Illustrative. A national library service in a Northern European country set up a small innovation team to rethink how people borrow e-books. In the first quarter the team used most of these ten tools on one challenge. Interviews with lapsed members and an experience map showed that the drop-off came at sign-in, not at search. Five whys traced it to a library card number most people no longer had to hand. The team wrote "How might we let a lapsed member borrow a book within two minutes, without their card?" Brainwriting with front-desk staff produced 40 options; the impact-effort matrix cut them to six; assumption mapping showed that the riskiest belief was that members would accept identity checks by phone. A paper prototype of the new sign-in, tested at two branches, confirmed most of it and exposed one confusing step. A premortem before the pilot flagged staff training as the likeliest failure, so it was added to the plan. The team closed the quarter with a retrospective and dropped one tool it had overused.

Questions people ask

What are the most common innovation tools? Across most practitioner toolkits you will find interviews, journey or experience maps, root-cause tools such as five whys, "how might we" framing, silent ideation such as brainwriting, prioritisation matrices, prototypes and retrospectives. The names vary; the stages they cover are fairly stable.

Do we need design thinking training before using these tools? No. Each tool can be learned in an hour and improved by using it. Training helps most after a team has tried the tools on real work and knows where it struggles.

How do I choose the right tool for my situation? Start from the question you need answered, not the tool. If you don't understand the problem, use understanding tools; if you have too many options, use choosing tools. Our pillar guide, which innovation tool should I use, is organised by situation for exactly this.

Where to go next

All ten tools have their own free guides, from stakeholder interviews to the retrospective. Browse the full set in the guides index.