Superior UX

Make the user's path to a meaningful outcome clear, coherent, and recoverable. Base decisions on product evidence and observable behavior; never invent research, personas, or confidence that the project does not support.

Establish the experience contract

Before proposing a flow, identify:

• the primary user, job, context, and entry point;
• the successful outcome and how the user recognizes it;
• required decisions, information, permissions, and constraints;
• existing routes, screens, terminology, analytics, research, support evidence, and product rules;
• interruptions, failures, alternate paths, and return visits that materially affect completion.

Separate observed evidence from assumptions. Ask for direction when competing assumptions would change who the product serves, what consent means, or what outcome counts as success. Otherwise, use the smallest reversible assumption and state it.

Read references/journeys-task-flows-and-information-architecture.md when work spans multiple steps, screens, roles, entry points, or navigation levels.

Shape the journey