methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Purposedifferent
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.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 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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
45-90 min45-90 min1-2 h1-2 h
Participantsdifferent
3-83-103-83-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
CATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsDelegation Board, Decision Boundaries, Role AgreementsInception Canvas, Risks, Goal List, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
Systems thinkingFramingStakeholders
AutonomyRolesTeam
AlignmentArchitectureCanvas
CanvasArchitectureAlignmentWorkshop
Add more methods