View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Architecture Request for Comments | ![]() Facilitation Alignment Mapping |
|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-20 Reviewer | 4-12 |
Formatdifferent | Async | Async | Workshop |
Outputdifferent | RAID Log, Status Report Source | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureDecisionAsyncGovernance | AlignmentStakeholdersStrategyFacilitation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






