News on field service management and optimization

Software Ergonomics: What a UX Audit Improved in Cadulis

Software ergonomics: technician using the field service application with their thumb on a smartphone. AI-generated image, fictional character.
Two buttons that do the same thing under two different names. Two others so close together that you click the wrong one. This is what the UX audit by UX-KEY found in Cadulis.

Summary

On the same Cadulis page, two buttons triggered the same action. They didn’t have the same name. We hadn’t noticed, because we know our tool by heart—and that’s exactly the problem. The usability of software is judged by those who actually use it.

Since October 2024, the Metz-based agency UX-KEY has been observing the real-world usage of our application and sends us a report every month. We’ll show you how their system works and what it made us fix, before wrapping up with the key usability questions to ask any software vendor before choosing your solution.

Why usability matters twice as much for field service software

A poorly designed screen at the office can be tolerated. In the field, the technician holds their phone in one hand, sometimes with gloves, often between two jobs and with the client waiting. They don’t have time to hunt for a button. Nor to redo a failed entry.

And then there’s everything the office doesn’t see: the screen in full sunlight on a rooftop, the weak signal in a basement, an older personal phone with enlarged fonts.

Then there’s repetition. Three seconds lost at every job closure, twenty times a day, multiplied by a team and by a year, and it adds up fast.

When the tool becomes frustrating, it ends up being bypassed. The technician jots things down in a notebook, calls the office, sends a photo by SMS. The software is installed, but no longer used. We discussed this in our article on digitizing field teams and managing resistance to change; a big part of that resistance comes down to software usability details that no one took the time to look at.

The problem is, a software vendor is poorly placed to spot these issues. They know where every function is, they never hit the wrong button. That’s why an outside perspective, based on usage data, is so valuable.

How UX-KEY’s UX audit works

UX-KEY is an agency based in Metz, founded in 2019, specializing in user experience for online business software (CRM, ERP, HR tools).

UX-KEY logo, UX audit and software usability agency for B2B SaaS

A script that observes real usage

A data collection script is installed on the application. It records interaction data to trace user navigation. According to UX-KEY, it only captures non-personal data, and the agency publishes its compliance charters for GDPR and the European AI regulation.

The patent for their journey analysis technology, filed in 2020, covers real-time tracking of page structure changes. This is important for a tool like ours, where screens are constantly being recomposed (a schedule reloading, a job sheet opening on top). The result notably takes the form of heatmaps, showing where users click.

Assisted analysis, human conclusions

An AI helps sort this data. But the audit itself is still carried out by the agency’s UX designers, who interpret behaviors and write the recommendations.

One report per month, one topic per report

Every month, we receive a report focused on a single topic, such as the usability of a workflow, accessibility, mobile display, or label wording. Friction points are listed and recommendations prioritized.

A one-off audit often ends up in a drawer. This one comes back to the table every month, and decisions have to be made (fix, schedule, or accept as is).

We’re not the only field service software in this situation. UX-KEY, for example, describes how they made job tracking and maintenance ticket management more intuitive for DriveIM, a technical management platform for real estate.

What the audit improved in our software’s usability

Nothing spectacular, just flaws that no one here noticed anymore.

Two buttons, two names, one action

On certain pages, two buttons triggered the same action under different labels. We knew. A user, on the other hand, sees two names and expects two functions: they wonder which to choose, hesitate, or worse, think they’re missing a step.

Web accessibility guidelines set the same principle for a website. Criterion 3.2.4 of the WCAG 2.2 requires that components with the same function be identified consistently. We have standardized the labels.

Buttons placed too close together

Elsewhere, buttons were placed so close together that a click could hit the neighboring one. With a mouse, it’s manageable. With a thumb, in a poorly lit stairwell, you sometimes trigger an action you didn’t want.

The guidelines also provide a reference here. Criterion 2.5.8 of the WCAG 2.2, level AA, sets a target of at least 24 CSS pixels per side, or sufficient spacing between smaller targets. We have revised the spacing of the affected buttons.

Why no one reported it to us

No one calls their software vendor to say they hesitated for two seconds in front of a button, or that they misclicked once during the week. They grumble, redo, and get used to it. This kind of friction is mostly visible in usage data, when someone takes the time to look.

What a UX audit can’t replace

A software usability audit has its limits. It shows where users get stuck; it doesn’t always explain why, or what they might need that doesn’t exist yet.

Direct feedback remains irreplaceable. A technician explaining that they enter their hours in the evening because they don’t have time on site teaches the vendor something no heatmap ever could. Training also remains important, even with a well-designed tool.

Then there’s prioritization. Fixing a usability issue takes development time that can’t be spent elsewhere. The report prioritizes; the team decides.

Five usability questions to ask before choosing your software

You don’t need to be a designer to judge the usability of field service software. During a demo or trial, these five questions are enough to make a decision.

Software usability: the five questions to ask during a field service software demo

  1. Does the same action have the same name everywhere? Browse through three or four screens. If "Validate," "Save," and "Finish" seem to do the same thing, your technicians will hesitate.
  2. Are the buttons easily tappable with a finger? Do the demo on a phone, not on the editor's computer. Try it with your thumb, using just one hand.
  3. How many screens are needed to close out a job? Count them. Every extra screen will be experienced a hundred times a week.
  4. What happens when a mistake is made? A destructive action should require confirmation, and a data entry error should be correctable without having to start over.
  5. How does the editor know what bothers its users? This is the most revealing question. A vague answer ("our clients are happy") is worth less than a method: user feedback, usage data, external audit.

One more tip. Have one of your technicians test the tool, not just the person who will sign the contract. In ten minutes of trial, they’ll spot what even the best-prepared demo won’t show, and you’ll know if they’ll really use it once out in the field.

Are you yourself a software publisher? The SaaS interface UX design guide published by UX-KEY details the process, from user research to testing.

For the rest of the selection process (features, pricing, commitment), our guide to choosing the best field service management software reviews the other criteria.

Software ergonomics: an ongoing project

Every new feature adds a button, a screen, a label, and therefore a chance to muddle what was once clear. The remedy is simple: regularly observe how the tool is actually used, and fix the small issues before they become workarounds.

We do this with UX-KEY, one report per month. And if you want to judge for yourself, ask us for a demonstration on a phone, with your own jobs.

Share the post:
Latest article