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 WSJF with its core stages and visible working result.
Agile
WSJF
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Purposedifferent
When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.
Complexitydifferent
HighMediumLowLow
Timedifferent
45-90 min1-2 h1-2 Tage1-4 h
Participantsdifferent
3-101-81-41-5
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsConcept Map, Relationship Labels, Knowledge GapsArchitecture Document, Context View, Runtime View, Deployment ViewContext Diagram, Container Diagram, Component Diagram
Tagsno overlap
LeanEconomicsSequencePrioritization
KnowledgeConceptsMappingSensemaking
ArchitectureDocumentationCommunication
ArchitectureCommunicationVisualization
Add more methods