UX map
Every user journey, stage by stage. Read a row for one person's experience from first visit to bringing friends; read a column to see how well the whole product handles that moment.
How to read it
Click a status to hide it, a journey to focus it, an item for its page and stories. “Gap” marks a stage that needs something and has nothing built or planned. Those are judgement calls, not stories.
Stage health
Seeker only.
Journeys × stages
| Journey | Discover first hears of it | Evaluate is this for me? | Commit sign up · RSVP · buy | Show up the night / the event | Come back the next week | Bring others friends, partners, crew |
|---|---|---|---|---|---|---|
C1 Seeker Find your dance J1 “Start dancing without feeling lost” | ||||||
C2 Student Find your teacher J2 “Get better and keep momentum” | ||||||
C3 Regular Find your floor J3 “Never dance alone — go with people I know” | ||||||
C4 Traveler Plan your festival year J4 “Plan and afford my dance travel” | ||||||
C5 Artist Get booked J5 “Get discovered and booked as an artist” | ||||||
C6 Host & venue Private event, rent a space J6 “Run a great event / throw a great night” | ||||||
C7 Organizer Run events & festivals J6 “Run a great event / throw a great night” | ||||||
C8 Member Account, identity, trust J7 “Trust it's real — real people, real faces, no fakes” |
What the map shows
Read on 2026-11-17. Re-read it when the map changes.
“Come back” is the weakest stage.
10 of 18 return items are partial, missing or gaps. Dancers get a few emails (a review the morning after, a mutual dance friend, a cancellation) and still have no inbox, no push, and no note when someone they follow posts a new night.
The business side is ahead of the dancer side.
Organizer and Artist are mostly green: event setup, flyers, Instagram, websites, invites, and email to contacts. Seeker and Traveler are mostly amber. Tools for organisers are growing faster than the dancer demand that makes them worth paying for.
Nothing turns a Seeker into a Regular.
There is still no beginner-level filter, and the taster list still does not say what to wear. A review email goes out the morning after a class (#632). It does not lead to the weekly social at the same school.
Traveler features are built but empty.
Ride shares, roommates, dinners and who's going only work with several real people on the same festival. Mutual dance friends now show on My plan, and the other dancer gets an email (#634 #636).
Using the site found what reading the code missed.
From the 2026-11-14 walk, still true: door check-in has no screen, the promo kit lives only in the AI app, and there is no festival map. Since then: Who's going faces are back on the event page (#605), a new event from the form stays a draft (#559), and the venue and artist answer bar sits above the phone tab bar (#551).
Handoffs between journeys
Where one person's journey turns into another's.
- C1 → C3Seeker becomes a Regulargap
After a first class, nothing leads to the weekly socials at the same school or venue.
- C3 → C4Regular goes to a first festivalpartial
The city page shows festivals, but there is no "people from your scene are going" signal.
- C3 → C5Regular starts teaching or DJingpartial
A dancer's page can become a business page (#474), but no flow invites it.
- C7 → C5Organizer invites an artistlive
An invite link lands on a review page the artist can answer (#515–517).
- C7 → C6Organizer asks a venuelive
A venue ask lands on a page the owner can answer (#514).
- C4 → C8Shared plan turns a friend into a memberlive
Shared plan view → "add friend" → sign-up.
- C7 → C3Organizer's RSVP poll brings dancers inlive
The poll works signed out and confirms on sign-up.
Sources
The routes in app/pages (docs, sketches and admin left out), the landing-promise stories in docs/issues/P*.md with statuses corrected against merged PRs, and the email senders in server/utils/email.ts, then checked by using the site on 2026-11-14: signed out on 2026.wedance.vip, and as a dancer, an organiser, a venue and an artist on a local copy of the database, on desktop and a phone (RAZ-898; what couldn't be run is in RAZ-931). Re-read against the code on 2026-11-17, from #518 through #652 (RAZ-1035). Data lives in app/lib/ux-map.ts: update an item when you ship or change it. The job each journey serves is on Jobs to be done. For stories mapped to tables and procedures, see User stories.