View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Discovery Jobs to Be Done | ![]() Architecture Request for Comments | ![]() Decision Making Impact Filter |
|---|---|---|---|
Purposedifferent | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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. | With new ideas or requests, the conversation often turns to solutions too early and to effect too little. An Impact Filter forces the initiative into an effect perspective and checks whether it creates a relevant difference. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 20-45 min |
Participantsdifferent | 5-12 Interviews | 3-20 Reviewer | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Impact Filter, Success Criteria, Next Step |
Tagsno overlap | CustomerOutcomesNeeds | ArchitectureDecisionAsyncGovernance | ImpactOutcomesFramingDecision |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






