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 | ![]() Agile ROAM Board | ![]() Decision Making Force Field Analysis | ![]() 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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | Low | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 20-40 min initial, dann laufend | 45-90 min | 45-90 min |
Participantsdifferent | 1 | 3-15 | 3-12 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | ROAM Board, Owner List | Force Field Map, Change Levers, Risk Notes | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | KnowledgeProductivityOrganization | RiskAgileTrackingAlignment | ChangeDecisionStrategy | AssumptionsRiskDecisionDiscovery |



