View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations PDCA Cycle |  Architecture arc42 |  Facilitation Stakeholder Salience Model |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | 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. | 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 | Low | Medium | Medium |
Timedifferent | 1 h bis mehrere Wochen | 1-2 Tage | 60-90 min | 1-2 h |
Participantsdifferent | 1-8 | 1-4 | 3-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Architecture Document, Context View, Runtime View, Deployment View | Salience Diagram, Strategy per Class | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Continuous improvementLeanExperiments | ArchitectureDocumentationCommunication | StakeholdersFacilitationAlignmentGovernance | AlignmentStakeholdersStrategyFacilitation |