View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Rolestorming | ![]() Agile Specification by Example | ![]() Innovation Lotus Blossom | ![]() Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | When a search for ideas stalls, switching roles helps people step outside their own perspective and activate new logics of action. The method reduces habit because contributions arise from a different stance. This brings unfamiliar, often fitting solution approaches into play. | 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 central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. | 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 | Low | Low |
Timedifferent | 30-60 min | 60-90 min pro Feature | 45-90 min | 30-60 min |
Participantsdifferent | 3-12 | 3-6 | 3-10 | 3-7 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Rollenkarten, Ideenpool pro Rolle, Konsolidierte Shortlist | Example Table, Acceptance Tests | Lotus Diagram, Idea Themes, Shortlist | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | BrainstormingIdeationCreativity | AgileRequirementsExamplesBehavior-Driven Development | BrainstormingIdeationCreativityDivergenceWorkshop | Behavior-Driven DevelopmentRequirementsExamplesRefinement |



