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 |  Architecture Request for Comments |  Decision Making Constraint Analysis |  Decision Making Decision Tree |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 20-60 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30-90 min | 30-90 min |
Participantsdifferent | 1 | 3-20 Reviewer | 2-8 | 1-6 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Decision Tree, Option Map, Assumption List |
Tagsno overlap | LearningKnowledgeUnderstanding | ArchitectureDecisionAsyncGovernance | ConstraintsDecisionPlanningOptions | DecisionTreeOptions |