UX Audit & Redesign.
Understand what is getting in the user’s way.
I review an existing website or application through specific user tasks, then turn the findings into a prioritised improvement plan. Where redesign is needed, we focus on the screens and journeys causing difficulty. The audit separates observed problems from assumptions, so your team can make decisions with a clearer reason than “the site feels old.”
Review your user journey→
SYSTEM
Review a journey with a purpose
The audit starts with the task your users are trying to complete: finding a service, submitting a form, onboarding or managing a record. We identify the audience and the business impact of that task before reviewing its interface.
This service suits a product that already exists. It is different from designing a new site from scratch, and it does not require a full redesign when a few targeted changes would solve the problem.
Use the evidence you already have
We review available analytics, support questions and relevant user feedback alongside the interface. Access to this evidence helps distinguish a repeated user problem from a personal design preference.
Where data is missing, I label findings as expert observations or hypotheses. Formal usability studies, tracking implementation and additional participant recruitment require separate scope; they are not implied by a visual review.
Inspect the points where tasks break down
I check navigation, content hierarchy, form instructions, feedback states and mobile behaviour. Keyboard access, focus visibility and readability are considered as part of the interface review, with limits documented.
Each finding includes the affected screen or journey, the problem, why it matters and a proposed next step. Prioritisation weighs the likely impact and implementation effort rather than presenting every issue as equally urgent.
Redesign the agreed problem areas
When redesign is included, I produce wireframes and Figma layouts for the selected journeys. The design explains what changed and which finding it addresses. Your developer can assess it against the existing stack before implementation.
We agree how to judge the changes after release. Depending on the available data, that could involve completion rates, fewer support questions or a task-based review. A design audit cannot promise a percentage improvement in advance.
What the audit delivers
You receive a prioritised findings document, annotated evidence and an improvement roadmap. An audit-only engagement ends with recommendations; an audit-and-redesign engagement also includes the agreed revised screens and handoff notes.
The report distinguishes quick changes, deeper workflow issues and questions needing user research. It is designed to help your team act, not to provide a long list of generic design rules.
Bring one difficult journey
Share the website or application, a representative account if access is needed and the task causing concern. Explain the feedback or drop-off you have observed, and provide anonymised analytics where available. This lets us agree a focused review boundary.
Before
we begin.
Is this a formal accessibility certification?+
No. The interface review can identify accessibility issues, but a formal conformance audit has a separate scope and testing process.
Can you audit without analytics?+
Yes. I can review the interface and tasks, clearly identifying the limitations and which findings remain hypotheses without user evidence.
Will you implement every recommendation?+
Implementation is separately agreed. The audit helps you prioritise changes; redesign and development can be included for selected findings.
Tell me what
needs to change.
Share the experience, the task users struggle with and any evidence you already have.
Review your user journey