View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Knowledge Mapping |  Decision Making Assumption Surfacing |  Architecture Software Architecture Canvas |  Architecture Risk Storming |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 45-90 min | 1-2 h | 60-90 min |
Participantsdifferent | 3-12 | 2-8 | 3-10 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Assumption List, Critical Assumptions, Learning Plan | Architecture Canvas, Goals, Constraints, Quality Attributes | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | KnowledgeMappingRisk | AssumptionsRiskDecisionDiscovery | CanvasArchitectureAlignmentWorkshop | RiskArchitectureWorkshopValidation |