View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations A3 Problem Solving |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Learning Card |  Product Discovery Product Kata |
|---|---|---|---|---|
Purposedifferent | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. | Product Kata helps clarify customer problems, solution ideas, and evidence through a repeatable improvement routine. It captures direction, current metric, target metric, experiment notes, and learning. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 45-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 25-40 min | 1-2 Wochen je Loop |
Participantsdifferent | 2-5 | Designers, developers as users, and facilitation | 1-5 | 3-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Learning Card with evidence and next action | Direction, Current metric, Target metric, Experiment note, Learning report |
Tagsno overlap | LeanProblem solvingCoachingOperations | ArchitectureEngineeringFeedbackValidationTasks | ExperimentsValidationDiscoveryLearning | OutcomesDiscoveryLearningIterationCoaching |