Skip to content
Product · Blueprint

Plan and afford my dance travel

How a dancer goes from browsing festivals to a year of them — workshops, passes, rides, rooms and friends — drawn lane by lane. The plan is there; what it costs, and tickets bought anywhere but here, are not.

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 (3): Someone is blocked on someone else, and nothing chases it.
  • By hand (8): A person carries the link or the news between lanes.
  • Silent (9): 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 (/festivals, a festival’s page, My plan’s Year tab, the ticket checkout and its Stripe and TicketTailor webhooks); not yet run end to end with a test dancer and a real checkout. See also the meet new friends blueprint. This is job J4, plan and afford my dance travel.

Friction by phase

Find festivals
⏳1 ✋0 🔇0 · 2/4 not live
Pick the year
⏳0 ✋1 🔇0 · 3/4 not live
Plan workshops
⏳0 ✋0 🔇1 · 3/4 not live
Tickets
⏳2 ✋2 🔇2 · 4/7 not live
Travel and room
⏳0 ✋3 🔇3 · 7/7 not live
Share with friends
⏳0 ✋2 🔇2 · 2/6 not live
The festival
⏳0 ✋0 🔇0 · 3/3 not live
After
⏳0 ✋0 🔇1 · 1/3 not live

Lanes × phases

WhoFind festivalsPick the yearPlan workshopsTicketsTravel and roomShare with friendsThe festivalAfter
Dancer
/festivals, the festival page, My plan
WeDance
Listing, plan, passes, emails
Festival organiser
Event editor, insights
Friends / other dancers
Shared links, the same festival page
Ticket provider
Stripe, TicketTailor, the festival’s own shop

Where it breaks

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