Journeys & navigation
The path from a person’s goal to a useful result. First visits, everyday tasks and the steps between screens.
- Task flows
- Navigation
- First & repeat use
UX audit services
An expert review of your product or website. Clear findings, the evidence behind them and a practical order of fixes.
Discuss your auditGood work starts with the right people.
The message does not explain why the invite failed or how to correct it.
People may retry the same address or ask support. The screen alone cannot tell us.
Review invite errors and support tickets. Observe people completing this task.
We agree the journeys first, then choose the depth
of review and research they need.
The path from a person’s goal to a useful result. First visits, everyday tasks and the steps between screens.
A heuristic review of clear actions, visible status, consistency and error recovery, using established usability principles.
The details around the main flow: empty screens, loading, permissions and the words that guide the next step.
Keyboard access, focus, contrast and screen reader labels. We check the journeys in scope against agreed WCAG criteria.
Drop-off points, recurring tickets and earlier research. Available evidence that helps us decide where to look.
Relevant people completing real tasks. We observe where they hesitate, misread or get stuck, when sessions are in scope.
From evidence to action
We weigh severity, how many people may be affected and the strength of the evidence. Your team helps estimate the effort and dependencies behind each fix.
Expert findings can be prioritised before user testing. We make the evidence and confidence clear, and flag assumptions that need further research.
We look for recurring patterns and shared causes, so one change can address several problems. Each recommendation includes a reason for its priority.
How a UX audit runs
Five stages. Early findings during the review.
A shared decision at the end.
Set the direction
Start from the decision you need to make: what to improve before a release, where a journey loses people, or whether a redesign is needed.
We agree with you
The journeys, user types, platforms and available evidence. A fixed scope, price and timeline.
You receive
A focused review
Inspect the experience
Review the key tasks against established usability principles. Inspect navigation, feedback and error recovery from the perspective of new and returning users.
We agree with you
Which tasks and roles need a closer look, and which observations need more evidence.
You receive
Issues in their context
Connect the evidence
Bring in available analytics, support history and earlier research. Where sessions are in scope, observe relevant people completing the tasks.
We agree with you
What is directly observed, what the data supports and what is still a hypothesis.
You receive
Clear reasons behind the findings
Choose the next moves
Group recurring issues. Weigh severity, reach and confidence, then estimate effort and dependencies with your team.
We agree with you
Which problems to fix first, which assumptions need validation and which improvements can wait.
You receive
A practical order of work
Make the findings actionable
Walk your team through the evidence and recommended changes. Discuss trade-offs, answer questions and agree the next steps.
We agree with you
What to fix, investigate or leave for later. Your team keeps the report and can carry out the work.
You receive
Ready for your team
What stays with your teamYour audit, delivered
Start with one critical journey, the key workflows in a product, or the paths through a website. We agree the scope, price and timing before the review.
Discuss your auditYour team can implement the recommendations.
We can help with design and development afterwards.
Annotated screens, observed problems and the evidence behind them. Assumptions are clearly marked.
Ranked recommendations with severity, confidence and effort estimates. Recurring patterns grouped together.
A walkthrough of the findings, open questions and agreed actions. The report and files are yours to keep.
It depends on the journeys in scope, the user types, the evidence available, the platforms and whether usability sessions are included. After a first conversation we propose a scope and agree a fixed price for it before the audit starts. Any additional work is approved by you first.
The timeline is agreed with the scope. A focused audit of one journey is the shortest; a full product audit with usability sessions takes longer, because participants need to be recruited and scheduled. You see early findings during the review, before the final walkthrough.
A ranked list of issues with annotated screens, supporting evidence, a severity assessment and recommended changes. We distinguish observed effects from estimated impact. Priorities account for severity, reach and confidence, with effort and dependencies reviewed with your team. We walk you through the findings, and the report and files are yours to keep and share.
Yes, as part of an audit or on their own. Participants come from your customers or a matching audience, recruited together with you. They complete the key tasks on a prototype or the live product while we observe, and you get session notes, the issues found and their severity.
It helps. Read access to your analytics and a sample of support tickets tie findings to what users do, and we agree that access upfront. A UX audit uses analytics to find where to look; conversion rate optimization uses it to test changes on revenue paths over time.
Yes. In SaaS products and web apps we focus on onboarding, roles and the daily workflow, and a SaaS UX audit can open a wider SaaS design project. On websites we look at navigation, page structure, content, forms and the path to an inquiry or sign-up.
Yes. Findings are written for the people who will act on them: the screen, the problem and the recommended change, with enough detail for a designer or developer to pick up. We can answer questions while your team works through the list.
You decide. Your team can work through the list, or we design and build the fixes, following the agreed priorities, through product design or, for a site that needs more than fixes, a website redesign. When we build the fixes, bugs within the delivered scope are fixed for 30 days after handover at no extra cost.