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 Architecture Decision Record |  Architecture C4 Model |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30-90 min | 15-45 min | 1-4 h | 60-90 min |
Participantsdifferent | 2-12 | 1-3 | 1-5 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Timeline, Milestones, Insight Notes | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Salience Diagram, Strategy per Class |
Tagsno overlap | TimelineFacilitationSequence | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | StakeholdersFacilitationAlignmentGovernance |