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 a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.
Complexitydifferent
LowLowMedium
Timedifferent
20-60 min30-60 min1-3 h
Participantsdifferent
13-122-8
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesStart Stop Continue Board, Improvement ActionsIssue Map, Positions, Argument Notes
Tagsno overlap
LearningKnowledgeUnderstanding
RetrospectiveImprovementTeamReflection
RationaleKnowledgeDecision
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 for Sailboat Retrospective
Agile
Sailboat Retrospective
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective