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 PARA Method |  Decision Making Assumption Surfacing |  Architecture Software Architecture Canvas |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work. | 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 Setup, laufend | 45-90 min | 1-2 h | 60-90 min |
Participantsdifferent | 1 | 2-8 | 3-10 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Assumption List, Critical Assumptions, Learning Plan | Architecture Canvas, Goals, Constraints, Quality Attributes | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | KnowledgeProductivityOrganization | AssumptionsRiskDecisionDiscovery | CanvasArchitectureAlignmentWorkshop | RiskArchitectureWorkshopValidation |