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 Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work.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.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
LowMediumLow
Timedifferent
20-60 min1-3 h30-90 min
Participantsdifferent
13-102-8
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesLearning Review Notes, System Factors, Improvement ActionsConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
LearningKnowledgeUnderstanding
LearningRetrospectiveIncidentOperations
ConstraintsDecisionPlanningOptions
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
Paper illustration for ALPEN Method
Operations
ALPEN Method
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem