View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Feynman TechniqueFishbone DiagramATAM (Architecture Tradeoff Analysis Method)After-Action Review
| Criterion |  Knowledge Modeling Feynman Technique |  Operations Fishbone Diagram |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations After-Action 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 20-60 min | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 20-45 min |
Participantsdifferent | 1 | 2-8 | Evaluation team, architects, and relevant stakeholders | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Fishbone Diagram, Cause Categories, Investigation Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Lessons learned, Action items, Event summary |
Tagsno overlap | LearningKnowledgeUnderstanding | Root causeQualityOperations | ArchitectureQualityRiskTradeoffsStakeholders | LearningOperationsImprovement |