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 C4 Model |  Facilitation Responsibility Poker |  Architecture Architecture Communication 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 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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 1-4 h | 45-90 min | 60-120 min |
Participantsdifferent | 3-10 | 1-5 | 3-10 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Context Diagram, Container Diagram, Component Diagram | Responsibility Map, Role Agreements, Open Questions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | AutonomyRolesTeam | ArchitectureCommunicationVisualization | RolesResponsibilityTeamFacilitation | ArchitectureCommunicationStakeholdersCanvas |