View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Design Design Studio |  Agile Working Agreements |  Facilitation Team Charter |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | When several designs need to be quickly put in relation to each other, it makes ideas visible and comparable. It encourages early variants instead of long upfront debates. | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 45-90 min | 2-4 h | 45-90 min |
Participantsdifferent | 3-8 | 3-12 | 3-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Sketches, Concept Directions, Design Decisions | Working Agreements, Team Norms, Review Cadence | Team Charter, Working Norms, Role Notes | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | SketchingCollaborationIdeation | TeamCollaborationAgile | TeamAlignmentCollaboration | AlignmentStakeholdersTeam |