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
Paper illustration of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper illustration of a six-field PESTLE grid
Business Strategy
PESTLE Analysis
Purposedifferent
When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions.When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 Tage1-3 h1-3 h1-3 h
Participantsdifferent
Internes Team2-82-82-10
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesContext Map, Integration Patterns, Boundary NotesGap Matrix, Action Plan, Risk NotesPESTLE Map, External Risks, Strategic Questions
Tagsno overlap
ResearchCustomerSynthesis
Domain-Driven DesignBoundariesStrategy
StrategyAnalysisPlanning
StrategyMarketAnalysis
Add more methods