View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Bottleneck Analysis |  Knowledge Modeling Feynman Technique |  Architecture Request for Comments |  Decision Making Constraint Analysis |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 20-60 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30-90 min |
Participantsdifferent | 3-8 | 1 | 3-20 Reviewer | 2-8 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | 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 |
Tagsno overlap | FlowMeasurementConstraints | LearningKnowledgeUnderstanding | ArchitectureDecisionAsyncGovernance | ConstraintsDecisionPlanningOptions |