View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Accountability LadderTeam Topologies Interaction ModesSpecification by ExampleExample Mapping
| Criterion |  Operations Accountability Ladder |  Team Design Team Topologies Interaction Modes |  Agile Specification by Example |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 20-45 min | Half day | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 1-8 | Team-Leads plus Architecture | 3-6 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Ownership Reflection, Action Commitment, Coaching Notes | Interaction Heat Map, Agreements per Pair | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ResponsibilityLeadershipTeam | TeamAlignmentCollaborationOrganization | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |