Lead-user method: learn from people already solving tomorrow’s problems
The lead-user method looks for people who already face an emerging need strongly enough to develop unusual knowledge or their own solutions.
Method
Understand the situation before committing to a solution.
New to this subject? Start here
The lead-user method looks for people who already face an emerging need strongly enough to develop unusual knowledge or their own solutions.
Method
Map customer actions, frontstage encounters, backstage work and support processes. Use a fictional bicycle repair to find a fragile handoff and plan a useful service test.
Method
Use paired Kano questions to examine basic, performance and attractive requirements. Read category distributions carefully and avoid turning labels into priorities.
Framework
Plan contextual observation, record actions separately from interpretations and examine observer effects. Turn a task sequence into a careful, bounded research finding.
Method
Define your target population, select a suitable recruitment route and examine missing voices. Distinguish population estimates from purposeful qualitative research.
Foundation guide
Design clear questions, suitable answer scales and a workable questionnaire route. Pretest interpretation and avoid confusing agreement with actual behaviour.
Playbook
Build a repeatable search, examine source quality and transferability, and turn existing records into a clear evidence summary and focused follow-up questions.
Method
Plan research around a decision. Separate exploratory, descriptive and causal questions, choose suitable evidence and agree how findings will affect the next step.
Playbook
Distinguish customer requests, observed behaviour and underlying needs. Build an evidence record and a clear problem statement before committing to a solution.
Foundation guide
Build a journey map from evidence: choose one person and goal, mark what is known or assumed, add the work behind each step and turn pain points into owned questions.
Method
Tell McKinsey's growth horizons apart from the futures version, then sort a portfolio, give each horizon its own management and check which transitional moves lead anywhere.
Framework
Define useful search fields by connecting customer situations, company capabilities and external change, then decide what to explore and what to leave out.
Playbook
Go beyond six lists of trends: document signals, trace their business implications and decide which uncertainties deserve research or action.
Method
Explore plausible futures, stress-test one business decision and build a useful watchlist, with a worked parcel-shop example and clear limits.
Playbook
Build a focused scanning routine that distinguishes observations, patterns and explanations, checks counter-signals and feeds real innovation decisions.
Playbook
Plan and conduct useful discovery interviews, follow real experiences, and turn what people tell you into careful, actionable findings.
Playbook
Use Discover, Define, Develop and Deliver to connect problem exploration with practical testing.
Framework
Identify who is affected, who can influence a change, and which conversations must happen before the next decision.
Method
Try a different area, subtopic or format.
Problem framing connects what people experience with the choices a team makes. Use this area to examine evidence, widen the options and decide which uncertainty needs attention next. The aim is a defensible problem boundary, not a perfect workshop artifact.