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 ARID (Active Reviews for Intermediate Designs) |  Facilitation Consensus Workshop |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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 | Medium |
Timedifferent | 30-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 1-2 h |
Participantsdifferent | 2-12 | Designers, developers as users, and facilitation | 5-30 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Timeline, Milestones, Insight Notes | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Consensus Clusters, Theme Titles, Priority Areas | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | TimelineFacilitationSequence | ArchitectureEngineeringFeedbackValidationTasks | FacilitationConsensusWorkshopAlignment | AlignmentStakeholdersStrategyFacilitation |