View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Process MappingARID (Active Reviews for Intermediate Designs)Start Stop Continue4Ls Retrospective
| Criterion |  Operations Process Mapping |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Start Stop Continue |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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. | 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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min | 45–75 min |
Participantsdifferent | 3-10 | Designers, developers as users, and facilitation | 3-12 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ProcessOperationsImprovement | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |