View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Polarity Mapping |  Agile Specification by Example |  Product Discovery Context Canvas |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | 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 an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 h | 60-90 min pro Feature | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 3-6 | 3-10 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Example Table, Acceptance Tests | Context canvas, Open questions, Shared context notes | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | Systems thinkingTradeoffsLeadership | AgileRequirementsExamplesBehavior-Driven Development | ContextFramingRequirementsCanvas | Systems thinkingFramingStakeholders |