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 |  Architecture Request for Comments |  Architecture Risk Storming |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min | 45-90 min |
Participantsdifferent | 1 | 3-20 Reviewer | 4-12 | 2-8 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | KnowledgeProductivityOrganization | ArchitectureDecisionAsyncGovernance | RiskArchitectureWorkshopValidation | AssumptionsRiskDecisionDiscovery |