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 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitysame | Low | Low | Low |
Timedifferent | 1 h bis mehrere Wochen | 1-2 Tage | 60–90 min |
Participantsdifferent | 1-8 | 1-4 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Architecture Document, Context View, Runtime View, Deployment View | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Continuous improvementLeanExperiments | ArchitectureDocumentationCommunication | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
