UX and ergonomic audit agency: optimise what exists without tearing it all down
Your users are complaining, and you don't want to start from a blank page?
At Akiani, a UX research and design agency since 2013, we audit websites, mobile apps and business software that you want to improve without rebuilding them entirely. We go through your screens with our criteria grids, rank each problem by whether it gets in the way, frustrates or blocks, then decide with you what to fix first. What works, we flag so you leave it alone, and whenever possible we put the diagnosis in front of real user tests.
When an audit is worth it
An audit is for optimising an existing product you don't want to transform entirely. It usually comes on the eve of a redesign that keeps part of what exists, when you've already spotted things that don't work.
- Customer support reports dissatisfaction, which is the most classic case.
- Your sales team regularly hears comments when they show the product to prospects.
- Users complain about the product's usability.
- The product has a history, it may have been built without any ergonomics work, and your teams have noticed through use that things were getting stuck.
Where it starts
We start by inventorying the screens and journeys to audit, not necessarily the whole product. For IPAG it was eight main pages, and for Un Grand Marché, five themes.
How a UX audit works
Weighing each piece of feedback before acting on it
We start with your documentation, access to the product, with test accounts if needed, and interviews with your stakeholders. A single piece of user feedback doesn't weigh much: it's the interview that tells us whether it's an isolated case, or a point that looks marginal but deserves attention. This time also lets us get up to speed on your project.
Every problem matched to a criterion
We identify each problem and match it to an ergonomic criterion: the Bastien and Scapin criteria, the Nielsen heuristics, and broader criteria for what relates to use in accessibility, eco-design and web quality, with the Opquast criteria (the team is Opquast Web Quality certified). We use these grids on all our projects, so the audit is systematic, exhaustive and comparable: two people on the team auditing the same product should reach similar results, and the approach stays comparable from one client to the next.
Friction, frustration or blocker?
For each problem, we ask what it costs in use: a simple point of friction, a frustration, or a blocker that outright stops users from doing what they wanted. When we can, we add an opinion on the nature of the fix, cosmetic or functional, and therefore riskier and more costly. On that point we stay very cautious, because development isn't our job.
Prioritising with you, with the extended team
We present the diagnosis and sort out together what matters and what can wait. For these decisions, we invite you to bring together your extended project team, with the stakeholders able to say whether the result matches the original vision. The core team, our day-to-day contact, stays on for the operational follow-up.
Recommendations come after the sorting
Recommendations prepared without you, during the diagnosis, would risk being hard to implement on your side. So we wait until the sorting is done. After that, either we prepare the recommendations on our side and come back to you, or, and it's what we prefer, we co-design them in a workshop with the core project team, starting to sketch ideas live.
Ideas sketched, then consolidated
An audit can stop at written recommendations. Most often, we illustrate them, and the ideas opened up in the workshop are consolidated, almost always as wireframes, to hand you something usable. If what follows goes beyond the scope of the audit, we can also design it with you.
What you get with a UX audit
The problems, one by one, with their criterion
Every problem found within the scope is described, with the ergonomic criterion it breaches and its severity level.
What works, so you leave it alone
We also record what users identified as working well, so the other fixes don't degrade it.
A roadmap
We list everything that needs to be changed, fixed or improved, with what you need to define your priority levels.
What you need to carry on without us
Because each problem is tied to a criterion, your teams can reread the audit on their own and start applying it to other pages, other areas, perhaps other products.
A UX audit under the microscope: the Défenseur des droits claim form
- Over 70 %of users abandoned the form before the redesign
- 83 %of claims go through the web form
- 29 %fewer phone calls
These figures come from the redesign that followed, which the audit and the tests helped steer.
The client had already reworked the journeys beforehand, in workshops with its business teams, including lawyers. We evaluated the screens against our ergonomic criteria (date fields with no explicit input format, for instance), cross-checked the blocking points with analytics data, then had the form tested at the Maison de la Justice et du Droit in Bordeaux, where the word "jurisdiction" turned out not to be understood by some users.
There was no question of rethinking these journeys entirely: we changed the order of some steps, reduced the number of questions per screen and avoided asking for the same information several times.
Read the case studyThree audits and what came next
Four years after its redesign, IPAG comes back for continuous improvement
Read the case study
Modernising Un Grand Marché without losing its artisan community
Read the case studyFrequently asked questions
It's always tailor-made, and the price depends mostly on the number of screens to audit and the complexity of the journeys. The rest is very secondary. The number of breakpoints matters too, since every extra format adds work. As a guide, our audits are priced between €3,000 and €11,000 excl. VAT. Once the screens and journeys are inventoried, we send you a quote.
When there's an existing product you don't want to transform entirely, and usually when feedback already points to what's not working. If everything has to be rebuilt, we'd rather start from a blank page, and what you need is a design process.
Documentation, access and interviews with your stakeholders, then an evaluation of each screen against our criteria grids, then a presentation and sorting session with your extended project team, and finally recommendations (preferably in a workshop with your core team, most often consolidated into wireframes). To give a sense of timing: on an audit covering desktop and mobile, about four weeks went by between the kick-off meeting and the presentation of findings, then one more month to co-design the recommendations.
A list of problems, each tied to the criterion it breaches and to a severity level, with what works well alongside. For the business school IPAG, the audit of 8 main pages produced recommendations on three priority levels, high, medium and low, grouped under 14 themes such as the navigation menu, information architecture or text legibility, then a before-and-after of the four priority pages, on desktop and mobile. For the Défenseur des droits, the feedback from the users who tested the form was built directly into the audit deck to back up the recommendations.
The audit evaluates the interface against ergonomic criteria, whereas the test puts it in front of real users. In principle, testing is always useful, because combining viewpoints matters, and a handful of users can sometimes be enough. An audit alone is justified when the profiles are very hard or expensive to recruit, or when the schedule leaves no time to organise tests: it's a possible choice, but its effect on quality is not negligible, and it's better to know that when you decide. For Un Grand Marché, the audit targeted five themes, then user tests confirmed the problems we had identified.
All three, consumer or business, brochure sites or applications. Our audits are almost always responsive, on desktop and mobile, and we recommend pooling the effort, because if the responsive work was done properly in the first place, what we saw on desktop rules out part of what we would have flagged on mobile. A tablet or very large screen format can be added, but in 2026 it's rarely requested. We've also been approached to audit control workstations: as soon as a user or an operator faces a socio-technical system, we know how to step in.
Our audits focus on interfaces first, but we do sometimes work on the workstation itself, for example on how dual screens are used.