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 for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
MediumHighLowLow
Timedifferent
1-3 h45-90 min1-2 h1-2 h
Participantsdifferent
3-123-103-103-8
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanRanked Backlog, Cost-of-Delay AssumptionsArchitecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
KnowledgeMappingRisk
LeanEconomicsSequencePrioritization
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
Add more methods