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 |  Systems Thinking CATWOE Analysis |  Architecture Software Architecture Canvas |  Facilitation Expectation Mapping |
|---|---|---|---|---|
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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 1-2 h | 45-90 min |
Participantsdifferent | 3-10 | 3-8 | 3-10 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Architecture Canvas, Goals, Constraints, Quality Attributes | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | AutonomyRolesTeam | Systems thinkingFramingStakeholders | CanvasArchitectureAlignmentWorkshop | AlignmentStakeholdersTeam |