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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Empathy Mapping
UX Research
Empathy Mapping
Affinity Diagramming
UX Research
Affinity Diagramming
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.
Complexitydifferent
MediumMediumLowLow
Timedifferent
2-6 h1-3 Wochen vom Draft bis zur Entscheidung30–60 min45–90 min
Participantsdifferent
2-83-20 Reviewer4-83-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsEmpathy Map, Assumptions List, Research GapsTheme clusters, Insight statements, Opportunity areas
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ArchitectureDecisionAsyncGovernance
SynthesisQualitativeWorkshop
SynthesisQualitativeRoot cause
Add more methods