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 Working Agreements |  Facilitation Expectation Mapping |  Innovation Brainstorming |  Innovation Reverse Brainstorming |
|---|---|---|---|---|
Purposedifferent | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 30-60 min | 30-60 min |
Participantsdifferent | 3-12 | 3-12 | 4-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Expectation Map, Alignment Notes, Agreements | Idea pool, Theme clusters, Shortlist | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | TeamCollaborationAgile | AlignmentStakeholdersTeam | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityRisk |