View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Facilitation Lean Coffee |  Facilitation Responsibility Poker |  Operations Accountability Ladder |
|---|---|---|---|---|
Purposedifferent | 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 group without a fixed agenda needs to get into useful conversations quickly, Lean Coffee structures the start around interests rather than a presentation. The group itself negotiates which topics get time first and which wait. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-90 min pro Feature | 30-90 min | 45-90 min | 20-45 min |
Participantsdifferent | 3-6 | 3-20 | 3-10 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Prioritized Topics, Discussion Notes, Action Items | Responsibility Map, Role Agreements, Open Questions | Ownership Reflection, Action Commitment, Coaching Notes |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | FacilitationAutonomyDialogue | RolesResponsibilityTeamFacilitation | ResponsibilityLeadershipTeam |