View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordEat the FrogARID (Active Reviews for Intermediate Designs)Ivy Lee Method
| Criterion |  Architecture Architecture Decision Record |  Operations Eat the Frog |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Ivy Lee Method |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | The method protects energy and attention for the task that creates the largest progress and is often postponed. | 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. | With a restless workday full of too many open items, the method creates radical simplicity. It directs attention to a short sequence instead of a broad, still-open field. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 15-90 min daily | 2–4 h review as a planning range; preparation and evaluation additional | 5-10 min daily |
Participantsdifferent | 1-3 | 1 | Designers, developers as users, and facilitation | 1 |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Priority Task, Completion Note, Daily Focus | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Daily Priority List, Completion Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | PrioritizationProductivityFocusExecution | ArchitectureEngineeringFeedbackValidationTasks | PrioritizationProductivityExecution |