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 |  Product Discovery Context Canvas |  Agile Specification by Example |  Systems Thinking Rich Picture |
|---|---|---|---|---|
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 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. | 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. | A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 h | 45-90 min | 60-90 min pro Feature | 30-90 min |
Participantsdifferent | 3-12 | 3-10 | 3-6 | 2-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Context canvas, Open questions, Shared context notes | Example Table, Acceptance Tests | Rich Picture, Problem Framing Notes |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ContextFramingRequirementsCanvas | AgileRequirementsExamplesBehavior-Driven Development | Systems thinkingSoft systemsFramingVisualization |