View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps ChatOps |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Starfish Retrospective |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together. | 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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | Ongoing | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 1-4 Wochen |
Participantsdifferent | 2-20 | Designers, developers as users, and facilitation | 4-12 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Chat Transcript, Action Log, Automations | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Starfish Board, Practice Changes, Experiments | Experiment results, Decision log, Learning summary |
Tagsno overlap | CollaborationEngineeringIncident | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveImprovementExperimentsTeam | ExperimentsGrowthAnalyticsValidation |