Skip to content
Product · Blueprint

Meet new friends

How a dancer goes from joining WeDance to dancing with someone they didn’t know, drawn lane by lane. The bottom row is the other dancer: most of the journey never reaches them.

How to read it

Status (as on the UX map)
  • Live, real data
  • Partial or mock data
  • Promised, not built
  • Gap: nothing planned
Friction markers
  • Waits (1): Someone is blocked on someone else, and nothing chases it.
  • By hand (1): A person carries the link or the news between lanes.
  • Silent (5): An answer or change doesn’t reach the side that needs it.

Gaps are where markers cluster. Click a step for its code, or a gap below to light up its steps. Built from the code on 2026-11-16 (/meet, the festival page’s “Shall we dance?”, and the unshipped matches in this sketch); not yet run end to end with two test dancers. See also the event setup blueprint. This is job J3, never dance alone.

Friction by phase

Join
⏳0 ✋0 🔇0 · 1/2 not live
Be findable
⏳0 ✋0 🔇0 · 2/4 not live
Browse
⏳1 ✋0 🔇0 · 1/4 not live
Say yes
⏳0 ✋0 🔇3 · 2/4 not live
Match
⏳0 ✋0 🔇1 · 1/3 not live
Meet on the floor
⏳0 ✋1 🔇0 · 2/4 not live
After
⏳0 ✋0 🔇1 · 2/2 not live

Lanes × phases

WhoJoinBe findableBrowseSay yesMatchMeet on the floorAfter
You
My plan, /meet, festival pages
WeDance
Deck, waves, emails
The other dancer
Their deck, their festival page

Where it breaks

Each gap is a cluster of markers. Click one to light its steps on the blueprint.