The tools inside every innovation process

View method →

Affinity Mapping

Clustering raw research, one observation per card, until patterns emerge that no single data point could reveal — then naming each cluster as an insight.

Time required

2–4 hours for a typical research corpus; larger bodies of work may take a full day

Group size

Best with 3–8 people — the full team that did the research and will act on its findings

Format

View method →

Ambition Matrix

A portfolio tool that maps innovation bets across how new the offering is and how new the market is, so you can deliberately balance safe and bold.

Time required

Half-day workshop

Group size

Leadership team (budget owners essential)

Format

View method →

Analogs & Precursors

Borrowing solutions that already exist — looking sideways across other industries and backward through your own industry's past — to spark genuinely new ideas.

Time required

2–4 hours for a full session; research and library-building is ongoing

Group size

2–8, can split to cover both axes in parallel

Format

View method →

Assumption Mapping

Surfacing the beliefs a concept secretly depends on and sorting them by importance and uncertainty, so you test the one that could kill the idea first, before building.

Time required

1–2 hours for the mapping session

Group size

3–8, cross-functional

Format

View method →

Avatars

The single specialized target you commit to first: the narrow beachhead you choose to dominate before you try to serve anyone else.

Time required

Half-day strategic session

Group size

Leadership team (product, marketing, sales)

Format

View method →

Balanced Breakthrough

An idea that is desirable, feasible, and viable simultaneously — checked against all three lenses before investing in it, because an idea that passes only two is not a breakthrough, it is a trap.

Time required

30–90 minutes for an initial DFV mapping; repeated throughout a project as each assumption is tested

Group size

Cross-functional team of 3–8; must include people who can speak to all three lenses

Format

View method →

Business Model Canvas

Nine boxes anyone can fill in. The method is not the filling in. It is discovering that block three contradicts block seven, on paper, before it does so in the market.

Time required

A focused session of 2–3 hours to map and stress-test the model; revisited whenever a significant block changes

Group size

Cross-functional team of 4–8; must include people who understand the customer, the offer, the delivery, and the economics

Format

View method →

Capability Mapping

Laying the capabilities a delivery requires against the capabilities you actually have, layer by layer, so the gaps that will stop you shipping are visible before they stop you.

Time required

1–2 facilitated sessions to build the initial map; revisited when delivery plans change

Group size

Core team plus practitioners who do the actual work; senior leadership for gap-closure decisions

Format

View method →

Co-Creation Workshops

Inviting the people a solution is meant to serve into the creation process itself, as active contributors who build and shape concepts alongside the team, not just react to them.

Time required

Half-day to full-day workshop

Group size

6–16 (participants + team)

Format

View method →

Competitive Landscape Analysis

Mapping who is playing in a market and how they are positioned, so you can find the space nobody occupies rather than crowd into where everyone already is.

Time required

2–4 hours for the initial mapping session; ongoing as the field shifts

Group size

2–6 for the analysis session; input gathered before

Format

View method →

Concept Testing

Everyone says your idea sounds great. The only question that matters is what they do when you ask them to commit, and whether you decided in advance what 'yes' looks like.

Time required

1–3 days for a structured concept test with real target users, including design, recruit, and synthesis; shorter for a fake-door or landing-page test, longer when qualitative probing is required

Group size

2–4 team members to design and run the test; the participants are real target users, typically 5–20 depending on whether you need qualitative signal or a quantitative commitment rate

Format

View method →

Contextual Observation (Ethnography)

Watching people in their natural environment to see what they actually do, rather than what they say they do.

Time required

1–3 hours per session in the field, across 5–10 participants

Group size

1–2 per observation (observer + optional note-taker)

Format

In person

View method →

Crazy 8s

Eight ideas, one per panel, one per minute, eight minutes — a brutal time constraint that forces you past your obvious ideas to the ones you did not know you had.

Time required

8 minutes for the sketching session; 20–30 minutes with briefing, sharing, and selection

Group size

Any; works individually or in groups of any size

Format

View method →

Delivery Roadmap

A sequence of bets ordered by uncertainty and dependency, firm in the near term and deliberately loose further out, that shapes what you build and learn in what order.

Time required

Ongoing — initial sequence in 1–2 weeks; revisited on a cadence as evidence arrives

Group size

Team lead(s) plus stakeholders for gate decisions

Format

View method →

Design Principles

Pre-committed tradeoffs that decide, in advance, how a team will choose when a hard choice arrives, and what it has agreed to say no to.

Time required

A focused session of 2–3 hours to derive and pressure-test from real recurring arguments; revisited when strategy or product stage changes

Group size

The team that actually faces the recurring choices — not leadership representatives, the decision-makers themselves

Format

View method →

Diary Studies

Asking participants to log their own experiences in the moment, over days or weeks, to reveal the longitudinal patterns and private moments no single interview or observation could catch.

Time required

2–4 weeks for the study period; analysis 1–3 days depending on volume

Group size

5–15 participants; n=6–8 is common for focused studies

Format

View method →

Ecosystem Mapping

A map of all the actors in a system and the value that flows between them, used to understand the wider web a problem actually lives in.

Time required

Half-day to full-day workshop

Group size

Cross-functional team with diverse domain knowledge (4–8 people)

Format

View method →

Empathy Mapping

A four-quadrant canvas — Says, Thinks, Does, Feels — that organizes what a team knows about one person, where the insight lives in the gaps between the quadrants.

Time required

45–90 minutes for a focused workshop; less with good research preparation

Group size

Works alone; most powerful with 3–6 people who were in the research

Format

View method →

Flow Mapping

Mapping the actual branching structure of how a product or process works today, every path, fork, dead end, and loop, so you can see the complexity that has quietly accumulated.

Time required

Half-day to full-day session

Group size

Small team with direct access to people who use and operate the thing (2–6)

Format

View method →

How Might We

A reframing question that converts a research insight into an open design challenge — the hinge between what you learned and what you build.

Time required

45–90 minutes per cluster of insights; full synthesis-to-HMW sessions run 2–3 hours

Group size

Effective solo; most powerful in a cross-functional group of 3–8 with access to the raw research

Format

View method →

In-Depth Interviews

Structured one-on-one conversations designed to understand not just what people do, but why they do it.

Time required

45–60 min per session

Group size

2–3 (facilitator, note-taker, participant)

Format

View method →

Jobs To Be Done

People do not buy products. They hire them to do a job, and they fire them when something does it better. Understand the job and you understand the demand.

Time required

3–8 hours for initial framing; the underlying research to fill it honestly is the larger commitment

Group size

Works well solo for initial framing; most powerful in a cross-functional team workshop with 3–8 people

Format

View method →

Journey Mapping

The whole experience on one picture, including the silent gaps between touchpoints where the real problems usually hide.

Time required

Half-day to full day (plus research time)

Group size

Cross-functional team of 4–12

Format

View method →

delivery

MVP & MLP (Minimum Viable and Minimum Lovable Product)

The smallest real product you put in front of real users — built either to learn as cheaply as possible (viable) or to be genuinely loved rather than merely tolerated (lovable).

Time required

Weeks to months (a real product release)

Group size

Full product team

Format

View method →

Orthodoxies

Surfacing the unquestioned beliefs that invisibly constrain what a team thinks is possible, so they can be deliberately challenged.

Time required

2–3 hours for a full orthodoxies session

Group size

4–10, with deliberate mix of insiders and outsiders

Format

View method →

Personas & Archetypes

Research-grounded portraits of the range of people you are designing for, so the team designs for real users instead of for itself.

Time required

Half-day synthesis session (after primary research)

Group size

Core design/research team

Format

View method →

Pilot Launches

Running your full, real solution with a bounded exposure — a defined segment, a defined geography, a fixed time window — to learn from real conditions before scaling.

Time required

4–12 weeks (the pilot window) plus 2–4 weeks of analysis

Group size

Core team of 4–8 plus operational capacity to run the bounded launch

Format

In person

View method →

Post-Launch Feedback Loops

Building a system that listens to a live product and actually acts on what it hears, closing the loop from signal to sense to decision to shipped change, and back again.

Time required

Ongoing — establish the loop in 2–4 weeks; the loop then runs continuously

Group size

2–4 people owning the loop; decision forum size depends on organisation

Format

View method →

delivery

Proof of Concept

A deliberately bare, internal experiment built to answer the one critical question a concept depends on — before committing to build it.

Time required

Days to weeks (for a single, well-scoped question)

Group size

1–4 (usually a small technical team)

Format

View method →

Rapid Prototyping

Making an idea tangible quickly and cheaply, at whatever rough fidelity is just enough to learn from it, rather than describing or debating it.

Time required

15 minutes for a paper sketch; an afternoon for a clickable mockup; the right answer is the least that answers your question

Group size

Individual or small team; test with 3–5 real users

Format

View method →

Service Blueprinting

A map of the whole machine behind an experience: not just what the customer sees, but the frontstage, backstage, and systems that produce it.

Time required

Full-day workshop (plus research prep)

Group size

Cross-functional team including frontline staff

Format

View method →

Stakeholder Mapping

Identifying everyone who has a stake in a problem, and characterizing each by their power, interest, and attitude, so you research the right range of people and engage each one well.

Time required

1–2 hours for the initial mapping session; updated throughout the effort

Group size

2–6; collaborative building surfaces stakeholders any one person would miss

Format

View method →

Storyboarding

A deck lets you write 'and then it intelligently surfaces the right answer.' A storyboard makes you draw it. The frame you cannot draw is the idea you do not have.

Time required

One to two hours for a first-pass sequence; an afternoon to walk it with the team and find the gap

Group size

3–8; small enough that everyone draws, large enough that the frame nobody can draw is felt by all

Format

View method →

Strategic Choice Cascade

A five-question framework that treats strategy as a set of linked, reinforcing choices — an aspiration, where to play, how to win, what capabilities, what systems — rather than a plan or a vision.

Time required

Half day to full day for the leadership team to work the cascade together; ongoing as conditions and choices evolve

Group size

Leadership team (4–10); must include people accountable across all five choices

Format

View method →

SWOT Analysis

A four-quadrant view of strengths, weaknesses, opportunities, and threats — whose actual value is not the four lists but the strategic moves you find by crossing them.

Time required

2–3 hours for the full audit and cross-pairing session

Group size

Cross-functional team of 4–8; mix of internal perspective holders and someone with outside-in market knowledge

Format

View method →

Systems Mapping

Modelling the feedback loops, delays, and leverage points that explain why a system keeps producing the same outcome, no matter how many times you fix it.

Time required

Requires several sessions with the people inside the system; building and testing the model honestly takes days to weeks, not hours

Group size

The team inside the system — people who actually know what happens, not what is written down

Format

View method →

The 5Es Framework

A fixed five-phase lens — Entice, Enter, Engage, Exit, Extend — for evaluating an experience and making sure the neglected bookends get designed, not just the core.

Time required

Half-day structured workshop

Group size

Cross-functional team (3–8 people)

Format

View method →

Usability Testing

Watching a real person attempt a real task with the thing you built, without helping them, to find out whether they can actually use it.

Time required

2–4 hours per round of five participants, plus analysis

Group size

1 facilitator, 1 observer, 5 participants per round

Format

View method →

Value Proposition Canvas

A two-part canvas that forces an honest match between what customers actually need and what a product actually offers, and exposes every gap between them.

Time required

2–4 hours for an initial canvas; the underlying customer research to fill it honestly is the larger commitment

Group size

Works well with 3–8 people — the product, design, and research team members who know both the offering and the customer

Format