methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Learning Review.
Operations
Learning Review
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Purposedifferent
After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.
Complexitydifferent
MediumMediumHigh
Timedifferent
1-3 h2–4 h review as a planning range; preparation and evaluation additionalHalber Tag
Participantsdifferent
3-10Designers, developers as users, and facilitation5-20
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Learning Review Notes, System Factors, Improvement ActionsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
LearningRetrospectiveIncidentOperations
ArchitectureEngineeringFeedbackValidationTasks
ResilienceOperationsIncident
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem