User flows
Map entry points, decisions, required inputs, and completion. Remove steps only when the task and business rules permit it.
Help users understand what to do, complete the task, and recover when something goes wrong. ACW designs flows and interfaces around the actions your product needs to support.
Contact UsA difficult interface may hide the next action, use unfamiliar labels, require repeated information, or provide no explanation when a task fails. Review the relevant screens alongside support feedback, usage evidence, and the product's operating rules.
The design scope identifies which journeys to change and which questions need testing. Adoption, conversion, and retention are potential measures to investigate, not automatic consequences of new screens.
Review the audience, existing journey, requirements, and available evidence.
Map the intended flow and information hierarchy.
Create the screens and interactions required for that flow.
Check agreed tasks, revise identified issues, and document decisions for implementation.
User flows and navigation decisions for the agreed journeys.
Designed screens and a prototype where included.
Component and state specifications for development.
Review findings and a record of unresolved questions.
Acceptance checks can examine task completion, understanding of feedback, and consistency of repeated actions. The review scope names the users, devices, and methods involved.
A design example, not a client result.
A multi-step request form generates repeated support questions. The scope reviews field requirements, step order, progress feedback, and error recovery. A prototype tests whether intended users understand the information needed and can complete the request.
Existing research can inform the starting point. If direct user testing is needed, agree recruitment, participant access, and responsibilities in the scope.
Yes. The work can improve flows and behavior within existing brand and component rules. Any visual identity changes need their own scope.
No. Implementation can change behavior. Include a review of the built interface when verification after development is required.
Bring the current flow, the people using it, and the evidence of difficulty you already have.