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 of Shape Up with its method-specific working model.
Delivery
Shape Up
Paper illustration for Learning Review.
Operations
Learning Review
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.Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts.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.
Complexitydifferent
LowMediumMedium
Timedifferent
20-60 min6 Wochen Cycle + 2 Wochen Cool-Down1-3 h
Participantsdifferent
12-4 pro Pitch3-10
Formatdifferent
AsyncWorkshop + asyncWorkshop
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesPitches, Bet-table decisions, Hill charts, Cooldown outcomesLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
LearningKnowledgeUnderstanding
PlanningDeliveryAutonomy
LearningRetrospectiveIncidentOperations
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