User journeys
Exercise the browser path that creates activation, trust, or revenue.
Exercise the browser path that creates activation, trust, or revenue.
What this feature is for
User journeys describe a small set of browser actions such as sign up, sign in, onboarding, or checkout. They verify what a customer can actually do rather than what an endpoint claims to do. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.
Before you open it
A reachable environment, stable test credentials or fixtures, and a short path with a clear success condition.
Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.
Run the workflow
Describe the steps, keep selectors resilient, run the journey against a preview, and promote the same definition to production verification after release.
- Open the feature from the dashboard outcome hub.
- Choose the app and environment that match the decision you are making.
- Run or save the configuration, then wait for the evidence state to settle.
- Assign the next action to an owner before leaving the page.
Read the evidence
Journey evidence includes each step, timing, screenshots or artifacts where available, and the exact step that failed. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.
When the result is not healthy
Keep test accounts isolated and avoid destructive actions in a production journey. Fix the first failed step; later failures are often cascading symptoms.
Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.
Use it with the rest of PreFlight
Use Journey Canary with GitHub checks, Production Twin, and Health to watch both release and live behavior. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.