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 of a four-quadrant grid with tasks sorted by importance and urgency and translated into actions.
Decision Making
Eisenhower Matrix
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
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Purposedifferent
It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.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.When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.
Complexitysame
LowLowLowLow
Timedifferent
15-30 min20-60 min30-60 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
1-613-12Scrum Team
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Eisenhower Matrix, Action List, Delegation NotesPlain-language Explanation, Knowledge Gaps, Study NotesStart Stop Continue Board, Improvement ActionsImprovement actions, Team agreements
Tagsno overlap
PrioritizationFocusTasks
LearningKnowledgeUnderstanding
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementLearning
Add more methods