The UX map

Every RISR screen, organized by experience. Walk it in the real app, change it in plain words, and review it on the Jam board.

Browse. Walk. Ask. Hand off.

For Alex: the new way to work on RISR screens (52 seconds, no sound)

How it works

Think in experiences: the jobs people do in RISR. Each one is a path of real screens with demo data.

The experiences page, grouped by stage
1 · Browse

Every experience

All 25 experiences on one page, grouped by stage. Filter by who it's for, or search in your own words.

Walking a path, with the choices at a fork
2 · Walk

The real app

Step through any path screen by screen. At a choice, try every option. Other versions are one click away, and any screen has a link you can share.

The client list with the renamed button
3 · Ask

Plain words

Say what should change. An agent changes the real screen and shows it to you on the same path.

The Jam board with Changed badges and main's version underneath
4 · Hand off

On the board

Changed screens land on Jam with a badge, and main's version sits under each one. Then it goes to engineering as a draft PR.

The full walkthrough

Everything end to end: browsing experiences, walking paths, one real change request from Alex's message to the Jam board, and the main board.

2 minutes 32 seconds, no sound

Under the hood

The board is built from the code, so it always matches what ships.

ExperiencesEvery path and screen, written down once
→
Demo dataEach screen has its own fixed data, so it looks the same every time
→
ScreenshotsEvery screen captured, every click checked, gaps listed
→
Jam boardOne main board, plus a board for each change with what's different marked
→
Kept in syncEvery change is checked automatically and the board updates
25experiences
122screens
54clicks checked
17 minfrom Alex's request to the board, in our test run

Not sure what's different?

Screens that change with the situation, like who's looking, an empty list or an error, are shown as other versions. Each one says exactly what's different. The board also lists the gaps: screens and choices nobody has mapped yet.

  • The board: RISR UX map on Jam (RISR team)
  • Try it: ask your agent to use the ux-map skill, for example "make this button say…" or "show me the version where…"
  • The code: risr-monorepo #1032
Walking another version of a screen, with what's different