methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
How Might We
Innovation
How Might We
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.
Complexitydifferent
LowMediumHighHigh
Timedifferent
30–45 min45-60 min1-4 h1-4 Wochen
Participantsdifferent
1-102-83-81-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsAssumption map, Test backlog, Risk rankingChallenge Findings, Risk Register, Mitigation PlanExperiment results, Decision log, Learning summary
Tagsno overlap
FramingOpportunityIdeationQuestions
AssumptionsRiskExperimentsValidation
RiskDecisionSensemaking
ExperimentsGrowthAnalyticsValidation
Add more methods