View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Lean Startup | ![]() Knowledge Modeling IBIS | ![]() Architecture Request for Comments | ![]() Decision Making Argument Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | Wochen bis Monate je Lernzyklus | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h |
Participantsdifferent | 2-8 | 2-8 | 3-20 Reviewer | 1-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Issue Map, Positions, Argument Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | LeanStartupValidationMVP | RationaleKnowledgeDecision | ArchitectureDecisionAsyncGovernance | SensemakingDecisionRationale |



