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)Starfish RetrospectiveStart Stop Continue
| Criterion |  Operations Process Mapping |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Starfish Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 30-60 min |
Participantsdifferent | 3-10 | Designers, developers as users, and facilitation | 4-12 | 3-12 |
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 | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ProcessOperationsImprovement | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |