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 IBIS |  Innovation Lean Startup |  Architecture Request for Comments |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | Wochen bis Monate je Lernzyklus | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min |
Participantsdifferent | 2-8 | 2-8 | 3-20 Reviewer | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Issue Map, Positions, Argument Notes | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale |
Tagsno overlap | RationaleKnowledgeDecision | LeanStartupValidationMVP | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance |