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 ARID (Active Reviews for Intermediate Designs) |  Architecture C4 Model |  Operations Getting Things Done |
|---|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h Setup, laufend | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 h | 1-2 h Setup, laufend |
Participantsdifferent | 1 | Designers, developers as users, and facilitation | 1-5 | 1 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Context Diagram, Container Diagram, Component Diagram | Action Lists, Project List, Review Routine |
Tagsno overlap | KnowledgeProductivityOrganization | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureCommunicationVisualization | ProductivityPlanningTasksExecution |