View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Timeline |  Architecture arc42 |  Facilitation Stakeholder Salience Model |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | When a project, incident, or change process is only remembered in fragments, Timeline brings the sequence back into a readable form. It makes turning points, precursors, and after-effects recognizable over the course of time. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 | Low | Low | Medium | Low |
Timedifferent | 30-90 min | 1-2 Tage | 60-90 min | 15-45 min |
Participantsdifferent | 2-12 | 1-4 | 3-6 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Timeline, Milestones, Insight Notes | Architecture Document, Context View, Runtime View, Deployment View | Salience Diagram, Strategy per Class | ADR File, Decision Log, Rationale |
Tagsno overlap | TimelineFacilitationSequence | ArchitectureDocumentationCommunication | StakeholdersFacilitationAlignmentGovernance | ArchitectureRationaleDocumentationGovernance |