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 Software Architecture Canvas | ![]() Agile Starfish Retrospective | ![]() Architecture Architecture Inception Canvas |
|---|---|---|---|---|
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. | 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. | 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 1-2 h | 45-90 min | 1-2 h |
Participantsdifferent | 1 | 3-10 | 4-12 | 3-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Architecture Canvas, Goals, Constraints, Quality Attributes | Starfish Board, Practice Changes, Experiments | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | KnowledgeProductivityOrganization | CanvasArchitectureAlignmentWorkshop | RetrospectiveImprovementExperimentsTeam | AlignmentArchitectureCanvas |



