Skip to content

Experience overview

Audience: ux
Status: specced
Owns: UI/UX
Depends on: Personas, Lifecycle, Domain entities

This lens describes user journeys and screens using the shared domain language. Do not invent stage names—use lifecycle codes (DRAFT, PAYMENT, …).

  1. Personas — who acts
  2. Flows — primary journeys keyed to stages
  3. Product capability index — modules (auth, identity, trades, payment, recommendations)
  • Frontend builds routes and components from flows — Frontend overview
  • Tech writing turns flows into audience-facing copy — Narrative
  • QA derives acceptance cases from flows + lifecycle — Test cases
  • Backend only changes when a flow implies a new state or API — API