View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Operations Gemba Walk | ![]() Delivery RAID Log |
|---|---|---|---|
Purposedifferent | 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 15-45 min | 30-120 min | 30 min Setup, dann laufend |
Participantsdifferent | 1-3 | 2-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Observation Notes, Improvement Ideas | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | LeanObservationProcessOperations | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






