When software is not landing well with the people who use it, there is a temptation to reach for something big: a new feature, a new dashboard, sometimes a whole new system. In my experience the better answer is usually smaller and less glamorous. Find out where people are getting stuck, and fix exactly that.

On Sunday 19 January 2026 I spent the day doing just that for the Report Creator on the FHRS platform I look after for FHR Services. By the end of the day I had made 29 separate changes, every one of them aimed at making the tool easier to use. Here is what changed, and why I think this kind of work is so often undervalued.

What the Report Creator is for

FHR Services runs a platform used by multi-site food businesses to keep on top of food hygiene compliance, using official data published by the Food Standards Agency. The Report Creator is where clients build their own compliance reports covering their sites: choosing what information to include, how to filter it and how to lay it out.

It is set out as a multi-step form that takes you through the settings a stage at a time. That structure is sensible. The trouble was what sat inside it.

What users were finding confusing

Client feedback told us that people were getting confused when building reports. A large part of the problem was the layout: related settings were not grouped together logically, so it was not always obvious where to find something or what to do next.

A handful of other rough edges made things worse. Some features did not behave the way people expected, and parts of the screen showed empty placeholders with nothing in them.

What I changed in one day

Some of the 29 changes were tiny. Grouped the way a user would notice them:

  • Settings grouped logically: I reorganised the layout of the multi-step form so that related settings sit together. This was the change aimed most directly at the confusion clients had reported.

  • Better drag-and-drop: I improved how drag-and-drop works in the Report Creator. When a tool invites people to drag things around, it has to respond the way they expect, every time.

  • Filters and preview that work: custom filters were not behaving properly, and the preview button had a fault. I fixed both. A preview that cannot be relied on is worse than no preview at all, because it teaches people not to trust what they see.

  • No more empty placeholders: I removed placeholders that appeared with nothing in them. An empty box on screen makes people wonder whether something has failed to load, or whether they have done something wrong.

The Scottish edge case

England, Wales and Northern Ireland use the familiar 0 to 5 food hygiene ratings. Scotland runs its own system, the Food Hygiene Information Scheme (FHIS), run by Food Standards Scotland. Instead of a number, a business gets a simple result such as Pass or Improvement Required.

There is also a status called Awaiting Inspection. It applies to new food businesses, or businesses with a new owner, that have not been inspected yet. That is perfectly normal, but it means there is no result to show, and a report has to cope with that sensibly. I made sure the Report Creator handles those cases properly.

It is a good example of an edge case: something that only affects some users, some of the time, and is easy to miss unless you understand the world your users work in.

The follow-up fixes

Usability work rarely finishes in a day. Over the next two days I kept going with smaller improvements:

  • Faster filter counts: I improved the performance of the counts shown when filtering, so they appear more quickly.

  • Tidier text: I reduced font sizes and fixed a number of labels.

  • Sorting by date: I fixed a bug in how dates were sorted.

  • No more typing in midnight: filtering by inspection date used to require a time as well as a date, so people had to enter midnight to get the results they wanted. I removed the time requirement. Nobody thinks of an inspection date as having a time of day, so the form should not ask for one.

  • Latest, second last and third last: I fixed the logic behind the options for showing the latest, second last or third last report.

Protecting the improvements

The risk with a burst of changes like this is that a later change quietly undoes one of them. So I added automated tests to the part of the platform that actually generates the reports.

A report builder lets people combine output fields in many different ways, and every combination needs to produce a correct report. The tests cover all of the report output field combinations. They run automatically, so if a future change breaks one, it is caught before it reaches a client rather than after.

Lessons for business owners

  • Listen to how people actually use it: the people using your software every day know where it hurts. Look at the tool through their eyes and work out what is behind their feedback.

  • Small fixes add up: none of these changes would make a headline on its own. Together they turn a tool people find confusing into one they can get on with.

  • Confusion has a cost: when software is hard to use, people work around it, raise support requests or simply give up. Over time, each of those costs far more than fixing the problem. Usability fixes are often among the cheapest improvements you can make.

Big new features have their place. But if your users are struggling with what you already have, that is usually the better place to start.

Further reading

If you want to explore the thinking behind this kind of work, these are good places to start:

Is your software confusing the people who use it?

If your team or your clients are struggling with a platform you depend on, the answer is often a set of small, targeted fixes rather than a rebuild. A fixed-price Platform Audit is a sensible first step, and my Maintain support retainers cover exactly this kind of steady, ongoing improvement.

You can read more about the wider FHRS work in the story of the platform going live and the full case study, or get in touch directly. No jargon, no pressure.

The smallest safe first step

Not sure where your platform stands?

The fixed-price Platform Audit reviews your code, security and server, and gives you a plain-English report with a prioritised, costed action plan. £1,950, within two weeks.

champaign-2.png

Apr 29, 2026

From broken reports to a bottle of Champagne: the FHRS platform launch

I took over a food safety compliance SaaS that was timing out on reports, leaking memory on imports, and had serious security gaps. Here's what I fixed, and how Paul marked the launch.