Point One Zero Platform architecturev11 · generated viewSign in to edit
Playbook › Track 4: Experience design

Track 4: Experience design

Track 4: experience design. Led by the design lead, applying traditional design thinking to an AI-native product: personas, journeys, research, and prototyping, with AIX principles layered on so that trust, provenance, and human control are designed in rather than bolted on.

Step by step

Research

  1. Persona identification. Who consumes outputs, who reviews them, who operates the system day to day; personas are roles with goals and constraints, never named individuals.
  2. User research. Interviews and observation with each persona; synthetic surveys widen coverage where access is limited, validated against the real interviews and never used as the sole basis for a gate decision.
  3. Journey maps. Current state and future state per persona: where AI enters the journey, where humans steer and decide, and where the moments of trust are won or lost.

Design

  1. Channel strategy. Channel-agnostic by design: the same capability reachable through chat, embedded surfaces, voice, and proactive notification, with one conversation following the user across channels. Findings from Discovery section G land as the C1 channel mix.
  2. Prototyping. Low-fidelity to interactive, tested against the journey maps with real users; corrections captured as structured feedback into the eval stream.
  3. AIX principles applied. Provenance visible on every value, review affordances at every gate, steering and interruption always available, uncertainty communicated honestly, and nothing rendered that cannot be traced to an approved source.
  4. UI and UX system application. House templates, formats, tone and branding mapped to the C1 values so the experience is configured per client, never redesigned per client.
  5. Surface engineering. P1Z-built surfaces (web app, desktop shell, mobile, voice) are thin shells over one shared UI core package: the render tree, streaming message views, and the conversation state machine. Shells hold no business logic; a new channel is a new shell over the same core, and every surface enters through the north gateway.

Deliverables

DeliverableLands as
Personas and journey mapsEngagement record; drive HITL placement and channel decisions
Validated prototypesReference for the Experience layer build
Channel mix, templates, formats, toneThe C1 band values
AIX pattern decisionsApplied through the renderer and review surfaces

This track uses: Discovery sections C and G, the C1 band, and the L1 Experience layer page.