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 arc42 | ![]() Agile Start Stop Continue | ![]() Agile Starfish Retrospective |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 1-2 Tage | 30-60 min | 45-90 min |
Participantsdifferent | 1 | 1-4 | 3-12 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Architecture Document, Context View, Runtime View, Deployment View | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | KnowledgeProductivityOrganization | ArchitectureDocumentationCommunication | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |



