Design Thinking
Design thinking is a human-centered approach to innovation that draws from the designer's toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.
Design Thinking is IDEO's five-phase human-centered innovation framework — Empathize, Define, Ideate, Prototype, Test — that transforms fuzzy challenges into testable solutions. Developed by Tim Brown and codified with Stanford's d.school, it gives product teams, entrepreneurs, and innovators a repeatable process for generating ideas grounded in actual user research rather than guesswork. What makes it distinct is its insistence on desirability first: solutions must be wanted by real people before asking whether they're feasible or viable.
“We're trying to improve onboarding for our B2B software. Customers sign up, get a product tour, and then we see huge drop-off in the first two weeks.…”
Solve the right problem by starting with real human needs, not assumptions
Design Thinking operates through five phases, each with defined activities and outputs. Empathize uses ethnographic tools — interviews, observation, shadowing — to surface unmet needs. Define synthesizes those observations into a crisp Point-of-View (POV) statement structured as 'User / Need / Insight,' then reframes the problem as a bank of How Might We (HMW) questions that open up solution space. Ideate applies structured divergent-thinking techniques — brainstorming rules, SCAMPER, analogies — to generate a wide range of candidate solutions without premature judgment. Prototype builds the lowest-fidelity representation needed to make an idea testable — the 'build to think' principle. Test collects real user feedback against the prototype, producing iteration triggers that send the team back into any earlier phase. Underlying the whole process is Brown's evaluation triangle: every solution is ultimately assessed against desirability (do people want it?), feasibility (can we build it?), and viability (should we?). In practice the phases are non-linear — test findings often reframe the original POV — but each phase has clear entry criteria and named deliverables that make the process encodable and repeatable.
Most innovation projects fail not because teams lack ideas but because they're solving the wrong problem — one defined by internal assumptions rather than real user needs. Teams jump from a fuzzy brief to solution-mode, skipping the hard work of understanding who they're designing for and what those people actually need. The result is well-executed solutions to the wrong problem, or prototypes that never make it past a first user test.
Work through the five Design Thinking phases with a guided co-facilitator: surface real user insights, reframe your problem with precision, generate ideas against the right criteria, and produce a prototype brief ready to build and test — all grounded in Tim Brown's IDEO framework rather than generic brainstorming.
- Your problem space or design challenge (rough or refined)
- Raw observations, interview notes, or user research you've collected
- Constraints you're aware of (time, budget, technology, organization)
- Any ideas or directions you've already considered
- A crisp Point-of-View statement pinning the real user need your solution must address
- A bank of How Might We questions that reframe your problem as opportunity space
- An empathy map or user persona synthesized from your research notes
- A prioritized idea shortlist evaluated against desirability, feasibility, and viability
- A prototype brief specifying what to build, what question it must answer, and how to test it
Watch the methodology work.
Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.
“You have 47 sticky notes from three customer interviews, a feature drop-off chart showing 60% churn in week two, and a team arguing between 'redesign the tour' and 'add a checklist.' The next sprint starts Monday and nobody agrees on what the actual problem is.”
“You have a single, crisp Point-of-View statement your whole team signed off on, a bank of eight How Might We questions ranked by opportunity size, a shortlist of six ideas scored against desirability / feasibility / viability, and a prototype brief for the top candidate — specifying exactly what to build, what question it must answer, and how to run a five-user test by end of week.”
The same skill, where the work happens.
No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.
What it does, specifically.
Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.
POV Statement Synthesis
Transforms messy empathy notes, interview transcripts, or observations into a single, actionable Point-of-View statement. The POV anchors the entire project by naming the specific user, their unmet need, and the underlying insight that makes this need surprising or important. A sharp POV prevents the team from chasing the wrong solution space.
How Might We Question Bank
Reframes the POV statement as a set of How Might We (HMW) questions that open possibility rather than close it. The skill generates multiple framings at different levels of abstraction — some narrow, some broad — so teams can choose an ideation aperture that suits their constraints.
Empathy Map Builder
Takes raw field notes, interview quotes, or user observations and organizes them into a structured empathy map — what the user Says, Thinks, Does, and Feels. This reveals gaps between stated preferences and actual behavior, which is where the best design opportunities live.
Structured Ideation Facilitator
Runs a text-based divergent ideation session using Design Thinking's brainstorming rules (defer judgment, build on ideas, go for quantity) combined with structured stimulus techniques including SCAMPER and analogical thinking. The skill generates idea prompts calibrated to the HMW question, then helps the team converge on a prioritized shortlist.
Prototype Brief Generator
Produces a structured brief specifying what prototype artifact to build, what specific question it must answer, what fidelity is needed, and how to recruit and run a test session. This prevents over-building and keeps prototypes focused on the single most important uncertainty.
Desirability / Feasibility / Viability Evaluator
Assesses a set of candidate ideas or a proposed solution against Brown's three-lens evaluation framework. The skill surfaces the tension points — ideas that score high on desirability but low on feasibility, or viable but not desirable — and guides prioritization decisions accordingly.
Graded before it shipped.
Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.
Point-of-View Statement
A single precision-written sentence in 'User / Need / Insight' format that anchors your project to a real human need. Functions as a filter for every subsequent decision: does this idea serve this POV?
How Might We Question Bank
A ranked list of reframed problem questions, from narrow to expansive, ready to use as Ideate phase prompts in a team workshop or solo brainstorm.
Empathy Map
A structured four-quadrant synthesis of user Says / Thinks / Does / Feels, with key tensions and latent needs called out — the primary Define-phase input for POV writing.
Prioritized Idea Shortlist
A scored matrix of candidate ideas evaluated against desirability, feasibility, and viability, with a recommended prototype candidate and rationale.
Prototype Brief
A one-page specification: what to build, what single question it must answer, what fidelity is appropriate, and a test plan with suggested participant profile and feedback prompts.
Grounded in the original work.
Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.
Tim Brown
Tim Brown is the CEO and president of IDEO, the global design and innovation firm credited with pioneering human-centered design. He is the author of 'Change by Design' (2009) and wrote the landmark 2008 Harvard Business Review article 'Design Thinking' that brought the methodology to mainstream business audiences worldwide. His TED talks on design thinking have been viewed millions of times, and he co-founded the Stanford d.school (Hasso Plattner Institute of Design) curriculum that now trains engineers, MBAs, and designers in the framework.
Change by Design (2009) and 'Design Thinking' Harvard Business Review (2008)
CEO of IDEO; author of 'Change by Design'; landmark 2008 HBR article; co-founder of Stanford d.school curriculum; TED speaker with millions of views.
Be first to run it.
Design Thinking is being built right now. Leave your email and we’ll tell you the moment it goes live.