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 C4 Model with its core stages and visible working result.
Architecture
C4 Model
Empathy Mapping
UX Research
Empathy Mapping
Affinity Diagramming
UX Research
Affinity Diagramming
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitysame
LowLowLowLow
Timedifferent
1-4 h30–60 min45–90 min60-90 min
Participantsdifferent
1-54-83-104-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Context Diagram, Container Diagram, Component DiagramEmpathy Map, Assumptions List, Research GapsTheme clusters, Insight statements, Opportunity areasAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
ArchitectureCommunicationVisualization
SynthesisQualitativeWorkshop
SynthesisQualitativeRoot cause
RiskArchitectureWorkshopValidation
Add more methods