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 Delegation Poker |  Architecture Architecture Communication Canvas |  Architecture arc42 |  Architecture Architecture Inception Canvas |
|---|---|---|---|---|
Purposedifferent | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 60-120 min | 1-2 Tage | 1-2 h |
Participantsdifferent | 3-10 | 2-8 | 1-4 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | AutonomyRolesTeam | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication | AlignmentArchitectureCanvas |