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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture 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.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h1-2 h45-90 min1-2 h
Participantsdifferent
3-123-82-83-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanInception Canvas, Risks, Goal List, Open QuestionsAssumption List, Critical Assumptions, Learning PlanArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
KnowledgeMappingRisk
AlignmentArchitectureCanvas
AssumptionsRiskDecisionDiscovery
CanvasArchitectureAlignmentWorkshop
Add more methods