Product Journey: definition and contract

A Product Journey is the maintained definition of a meaningful customer or business outcome. It records what must remain true, who performs it, the path and branches involved, the states in which it must work, the checkpoints that prove the outcome, its owner, and its version history.

A Journey is not just a sequence of clicks

A click sequence can reach the final instruction without producing the intended consequence. A signup flow may submit successfully while creating the wrong role, losing an invitation, or leaving the account unusable. The Journey therefore owns the outcome checkpoint—not merely the actions used to reach it.

The execution method may change. A developer can define or import the Journey from code, while a non-developer can record and edit it visually. Those interfaces share one contract and must not silently discard constructs created by the other.

What belongs in a Product Journey

A complete Journey definition includes:

• purpose and intended outcome;
• actor, role, and ownership;
• preconditions and allowed side effects;
• steps, branches, and target identity;
• checkpoints that verify the customer or business consequence;
• context policy for state, data, locale, theme, viewport, and related axes;
• dependencies and downstream outputs;
• immutable version history.

Example: invite a workspace editor

The actions might be “open team settings, enter an email, choose Editor, and send.” The Journey outcome is stronger: the intended recipient receives a valid invitation for the correct workspace and role, and accepting it creates the expected membership without exceeding policy or corrupting another account.

Different State Capsules may exercise owner and admin actors, plan limits, locales, or feature flags. Each Journey Version freezes the exact intent and path used by its Runs.

Journey versus adjacent records

Record	Relationship to the Journey
Test	Executes or describes part of the Journey.
Screenshot	Shows one observed state or an edited explanation of it.
Accessibility finding	Describes one capability-level result within the Journey evidence.
Guide or demo	Explains the Journey through a Rendition.
Release checklist	May summarize Journey readiness but does not replace its evidence or Decisions.

The Journey remains the durable identity connecting all of them. Read the Journey documentation or see how the broader category works in Product Journey Infrastructure.