View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Timeline |  Product Discovery Kano Model |  UX Design Service Blueprinting |  Facilitation Dot Voting |
|---|---|---|---|---|
Purposedifferent | When a project, incident, or change process is only remembered in fragments, Timeline brings the sequence back into a readable form. It makes turning points, precursors, and after-effects recognizable over the course of time. | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | When a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 30-90 min | 1-2 Tage | 0.5-2 Tage | 5-15 min |
Participantsdifferent | 2-12 | 10-50 | 6-12 | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Timeline, Milestones, Insight Notes | Kano Matrix, Feature Classes, Priority Themes | Service Blueprint, Fail Points, Ownership Map | Ranked list, Consensus signal, Shortlist |
Tagsno overlap | TimelineFacilitationSequence | SatisfactionPrioritizationCustomer | Service designOperationsJourneyBlueprint | FacilitationVotingConsensusPrioritization |