A framework for teams who want to think better, not just work faster
Where this came from
Over decades of running innovation sprints and design programmes inside large enterprises — building products and services that reached global markets across healthcare, finance, consumer goods, and technology — certain patterns kept appearing.
It wasn’t the methods that determined whether a team would produce something genuinely new. Teams could follow any process and still arrive at mediocre, safe, obvious answers. What separated the teams that broke through was something harder to name: a set of mental orientations, ways of looking at a problem, habits of perception that they had either developed or hadn’t.
The Five Mindsets emerged from that observation. They are not a process. They don’t tell a team what to do in what order. They are five distinct lenses — five ways of directing your attention — that together give a team the range they need to move from a real problem to a meaningful solution without losing what matters along the way.
Each mindset requires training. Each one asks you to shut off something you would naturally default to, and open something you would naturally suppress. Together, they form a complete system for thinking about innovation — not as a series of steps, but as a practice.
Mindset One: Empathy
Stop thinking about the solution. Start feeling the problem.
The first and most fundamental shift the Five Mindsets asks of any team is this: stop thinking about what you can build, and start understanding the world of the people you are building for.
This sounds straightforward. In practice it is one of the hardest things a team of builders, engineers, and product managers will ever be asked to do. Because the moment a capable team sits down together, the solution space opens up immediately. Someone mentions a technology. Someone else sketches a feature. Within minutes the conversation has migrated from the user’s problem to the team’s solution — and it rarely comes back.
The empathy mindset is a deliberate act of closing that door.
“The voice of the solution is loud. The voice of the user is quiet. Empathy is the discipline of learning to hear the quieter voice.”
This is a mental exercise in shutting off a core part of the product-making brain — the part that thinks in materials, technologies, feasibility, and revenue. Not because those things don’t matter, but because when they dominate too early, the team stops seeing the problem clearly and starts seeing only the solutions they already know how to make.
Empathy has to be felt, not just reported. This is the key distinction. A researcher can deliver findings. A product manager can brief a team on user pain points. But the empathy mindset is not transferred until every person on the team has genuinely felt the frustration, confusion, or unmet need that the people they are solving for live with. Data transfers information. Empathy transfers experience.
This is why the methods here tend toward the experiential. Mystery shopping — moving through a customer journey with no insider knowledge, acquiring the solution and navigating the distribution channel as a first-time user would, stripped of the branded experience. Participatory observation — going into the spaces and processes where users operate, not to solve anything, but to listen and feel. Job shadowing with a trust bond built over time, where a user learns to articulate their emotions as they experience them, and a curious team member follows, watching and absorbing.
Other methods bring the evidence directly into the working environment: photographs taken at emotional peaks and valleys, statements written in users’ own words, pinned to the walls where the team works. When a designer or engineer looks up from their screen and sees the face of the person they are building for, something shifts.
Quantified and desk research has its place too — tracking where people express strong emotions publicly, identifying patterns in what frustrates or delights, even occasionally revealing how users feel about a particular brand or industry when they don’t know a company representative is listening.
And then there is one particularly generative category of empathy source: the lead users. The people who have already started solving the problem themselves — taping, cutting, improvising, hacking together their own solutions and sharing about it. These people don’t just tell you about their problem. They show you where the conventional solution has failed badly enough that they went ahead and built something better. That is empathy at its most instructive.
Mindset Two: Ideation
Every idea is valid. Some ideas need the impossible to get there.
The second mindset is a complete change of register. Where empathy asks you to slow down, receive, and feel, ideation asks you to accelerate, combine, and generate. The shift is total — and it requires its own discipline.
Ideation is not brainstorming in the casual sense. It is a trained capacity to think in multiple directions simultaneously, to hold an idea as a living thing with variants and strains and components, to shape and reshape it, and above all to resist the instinct to judge too early.
Think of an idea as a living organism with DNA — origins, compartments, variants. The skilled ideator can mould and cast and combine and rotate ideas, find variants they wouldn’t have found otherwise, follow a direction systematically to see where it leads. This is a mindset of divergence, but systematic divergence: think of all the ways to do X, then all the ways to do Y, then apply variations to proportion, sequence, amount, boundaries.
“The trick is not just to have ideas. It is to know how to shape them consciously — to understand that ideation is a skill that gets better with practice, not a talent distributed at birth.”
One of the most useful mental models here comes from mathematics: the concept of imaginary numbers. In rational mathematics, certain problems are unsolvable. But when mathematicians introduced the imaginary axis — defined as the square root of negative one, which is impossible in the rational number system — they created a two-dimensional space in which those same problems became solvable. The solution exists on the imaginary axis. You take it there, resolve it, and bring it back to the rational line with an answer that was previously unreachable.
Ideation works the same way. The impossible idea, the absurd idea, the idea that would never be built — these are not wastes of time. They are vehicles for accessing parts of the solution space that rational, feasible thinking cannot reach. You go there, you find something, and you bring it back.
The thinking of Edward de Bono fits naturally here. His model of parallel thinking — the idea that a group of people can be trained to think in the same mode simultaneously, rather than each defending their own position — is the actual foundation of effective co-creation. His six thinking hats are one practical expression of this: structured modes (analytical, emotional, critical, creative, optimistic, process-oriented) that a team moves through together, in rhythm. Like a choir that first sings in unison before finding harmony, a team that has practised parallel thinking can start to move strong ideas between minds with very little friction.
Statistically, good ideas come from anywhere. Trained ideators will produce strong ideas more consistently. But anyone in the room can produce the best idea in the session. The only way to find out is to create the conditions where all ideas are genuinely welcome — and where judgment is held in abeyance until the field is full.
Mindset Three: Filtering
Not all ideas are equal right now. Some are right for this problem, this moment.
After the expansive work of empathy and ideation, the filtering mindset asks for something different again: clarity, judgment, reduction. This is where a team moves from a field of possibilities to a set of directions worth pursuing — and where the quality of that judgment determines everything that follows.
Filtering is not about finding the one right answer. It is about intelligently reducing the space. From a hundred ideas to fifty. From fifty to five. And doing so in a way that preserves what was valuable in what gets set aside, so it can be recombined later.
The filtering mindset works through three lenses applied simultaneously:
Viability asks whether value can be created from this idea in the market. Not just revenue — but whether the current brand can contain this type of solution, whether governance and compliance structures support it, what portion of the market is realistically addressable given regulation, culture, and distribution norms.
Feasibility asks whether the idea can be made. Does it use the team’s production capabilities well? Is the risk profile acceptable? Can materials be sourced, operations sustained, the concept maintained on future roadmaps?
Desirability looks at the full chain of people the solution must work for — not just the end user, but everyone from manufacturing through distribution through sale through adoption through end of life. Usability, desirability, the degree to which this solution resolves the problem better than whatever currently fills that need. Sometimes the real competitor is not what you expect. A milkshake is a competitor to a burger for the driver eating on a motorway — not because they’re in the same category, but because they’re solving the same problem, and the milkshake wins on the criteria that actually matter in that context.
“Filtering is the art of reduction. But the ideas you remove are not dead — they are in circulation, waiting for the problem that fits them.”
What makes filtering a mindset rather than just a decision-making process is the awareness of resolution. Like a fractal, the space between two ideas contains infinite variations — zoom in and an entirely new field opens up. Filtering is always a question of grain size: what lens, what resolution, what level of detail are we looking at the solution space through? We need enough breadth to see the whole field, and enough detail to make real distinctions. We balance those constantly.
Filters are also temporary. Time-limited decisions — this is our direction until Friday — allow a team to move, learn, and return. The filtered-out idea is not rejected. It is sent back into the pool. All ideas are potentially good; they are just good for different occasions. Some never find their moment. Others find broad universal use across many different problems, years later.
Mindset Four: Iteration
Move without complete knowledge. Learn your way to the right answer.
The iteration mindset is the discipline of building, testing, learning, and adjusting in cycles — and doing it with the minimum expenditure of effort that still generates real learning.
This is not about perfectionism before release. It is the opposite: the explicit acceptance that you don’t have enough information to be right yet, combined with the understanding that the fastest way to get that information is to make something and see what happens.
The rhythm is everything. Like a band that has found its pulse, the iterative team returns again and again to the same territory, each time with slightly more understanding, adding and adjusting and sometimes removing elements. The goal is not to finish a single great version. It is to keep moving through cycles until the evidence tells you you’re close enough.
Lean principle governs the speed of this: what is the least we can do to test this hypothesis? Not the minimum viable product in the marketing sense — the minimum valid test in the learning sense. Every additional element added to a test is weight that slows the cycle. The question is always whether this level of fidelity is actually necessary to learn what we need to learn. If it isn’t, strip it out.
“Iterative teams don’t fall in love with their solutions. They use their solutions as instruments for generating truth.”
Access to real users is non-negotiable — and it is where many teams hesitate. Exposing a half-formed idea to customers feels risky. What if the brand looks unprofessional? What if users form a negative impression? The iteration mindset reframes this entirely: you are not showing customers what you built. You are using their reactions to understand something. The prototype is a learning instrument, not a product preview.
The full solution does not need to be prototyped. A solution with fifty subsystems can have one tested in isolation. But the team needs to hold awareness of interdependencies — some systems cannot be truly validated in fragments, and some assumptions can only be tested at the system level.
Early in the cycle, lightweight stands-ins do the work: paper prototypes, narrative scenarios, role-plays. Later, as the concept matures and the choices narrow, the prototypes become more rigorous and cycle time increases. What determines when iteration stops is not a fixed rule — it is the criteria set during filtering, the hypotheses defined at the outset, and the evidence accumulated in the tests. Iterative teams would never stop if left to themselves. The discipline is in knowing when the learning curve has flattened enough to act.
Mindset Five: Storytelling
The idea isn’t finished until it can travel without you.
Of the five mindsets, storytelling is the one that feels most optional — and it is the one most often left undone. Teams invest deeply in understanding users, generating ideas, filtering ruthlessly, and iterating toward something real. Then they present their work in a meeting, move on, and wonder later why the idea got watered down, misunderstood, or quietly dropped.
The problem was never the idea. The problem was that the story didn’t travel with it.
The storytelling mindset is about one precise and important capacity: the ability to knit together the logic of an entire design journey into a coherent, transferable narrative — one that another person can understand, repeat, and defend without you in the room.
A strong innovation story holds three threads simultaneously:
- From empathy: What did we learn about the user, and why did that specific pain become the one we decided to solve for?
- From ideation and filtering: What did we choose to pursue, and what made us select it — what were the criteria, and how did we weigh them?
- From iteration: What did we learn from testing, and what does the evidence now say?
Most teams can answer each question in isolation. The storytelling mindset is the discipline of holding all three together as a single argument.
“The most powerful innovation stories are not about the solution. They are about the marriage between the solution and the problem it was made to solve.”
This connection — when made with clarity and conviction — transforms how an idea is received. It stops feeling like someone’s creative output and starts feeling like the obvious, necessary response to a real human need.
Stories preserve what rationalisations destroy. By the time a design team’s work reaches engineering, product management, marketing, or the executive layer, it has typically passed through multiple rounds of simplification and cost-cutting. Each round is rational. Each round removes something. And without a story that explicitly names what matters and why, the most important elements — the ones that made the idea distinctive — are exactly what gets trimmed first.
The storytelling mindset is an act of preservation. When you document the emotional core of an empathy finding — not just the data, but the specific moment that made the team care — you give that feeling a form that others can hold. When you articulate the selection logic behind an idea — not just the output, but the reasoning — you protect it from being second-guessed by people who weren’t in the room.
The mindset also runs across the entire process, not just at the end. In empathy work, stories transfer the feeling of what users experience to team members who weren’t in the field. In iteration, a narrative prototype can test whether an idea resonates before anything is built. In filtering, a well-told story makes criteria legible in ways a scoring matrix never can.
For product makers, the storytelling mindset flows naturally into product marketing, brand, and advertising. When you have captured, with honesty and precision, what problem you solve, for whom, and why this solution is the right one — you have given the rest of the organisation the raw material for everything that follows. Marketing, sales, customer success, investors — all of them can build from a story that is clear and true.
“A strong innovation story doesn’t just explain the product. It equips every part of the organisation to make meaningful decisions about it.”
And finally: in storytelling, you are not trying to change anything. The story does not invent. It faithfully and compellingly reflects what the team learned, chose, and built — and why. This is what separates storytelling from spin. Spin changes the facts to fit the audience. Storytelling finds the honest thread running through all of the facts and makes it visible.
When that story is in place, the best ideas survive. Not because they were protected politically, but because everyone who encountered them understood exactly what they were — and why they mattered.
Callout — The thread through everything:
The Five Mindsets are not sequential steps. They are five ways of paying attention — each one a discipline in its own right, each one requiring the others to be complete. Empathy without ideation produces insight with nowhere to go. Ideation without filtering produces noise. Filtering without iteration produces untested bets. Iteration without storytelling produces learning that disappears. And storytelling without empathy produces a story no one believes.
コメントを残す