View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Feynman Technique | ![]() Knowledge Modeling Concept Mapping | ![]() Agile Start Stop Continue | ![]() Agile Mad Sad Glad |
|---|---|---|---|---|
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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20-60 min | 1-2 h | 30-60 min | 30-60 min |
Participantsdifferent | 1 | 1-8 | 3-12 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Concept Map, Relationship Labels, Knowledge Gaps | Start Stop Continue Board, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | LearningKnowledgeUnderstanding | KnowledgeConceptsMappingSensemaking | RetrospectiveImprovementTeamReflection | RetrospectiveTeamReflection |



