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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
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.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations.
Complexitydifferent
LowHighLowLow
Timedifferent
20-60 minSeveral meetings plus preparation and analysis; total effort depends on scope1-2 Tage5-20 min
Participantsdifferent
1Evaluation team, architects, and relevant stakeholders1-42-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsArchitecture Document, Context View, Runtime View, Deployment ViewUnderstanding Check, Clarification Notes, Learning Gaps
Tagsno overlap
LearningKnowledgeUnderstanding
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureDocumentationCommunication
LearningUnderstandingCommunication
Add more methods