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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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.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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.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
LowHighLowHigh
Timedifferent
30–45 min1-4 h1-5 Tage1-4 Wochen
Participantsdifferent
1-103-8Nutzertraffic1-6
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsChallenge Findings, Risk Register, Mitigation PlanInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
FramingOpportunityIdeationQuestions
RiskDecisionSensemaking
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods