Looking after it

Real-world user testing

The person who built a system is the worst person to test it, because they know how it's meant to work. We use it the way everybody else does.

A shop owner in an apron standing in the open doorway of his bright shop on a sunny high street

What we do

We work out who really uses your system, then we do their jobs from start to finish. That might be office staff taking an order, a driver checking a run list on a phone in the rain, or a customer placing an order on site with one bar of signal.

We note where steps are confusing, where things fail, what nobody would notice on a busy day, and what would catch someone out at the worst moment. We also check that it works on the phones and tablets people actually carry.

What you get

  • A round of testing as each type of user, on the devices they use.
  • A plain list of what tripped us up, worst first, with how to fix it.
  • As a one-off, or regularly after each significant change.

Why it’s worth it

Staff rarely complain about a system. They work around it, keep their own spreadsheet on the side, or ring the person who built it. All of that costs you time, and none of it shows up anywhere. Customers don’t complain either. They just order from someone else.

AI tools make it especially easy to add features quickly, and easy for a change to one screen to break another without anyone noticing. Testing like a real user is how you find out.

Questions

Will it put test orders into our live system?

Not without your go-ahead. We agree what can and can’t be tested, use test accounts where we can, and clear up afterwards. We list everything we did.

Can this be part of the audit?

Yes, it’s an optional part of the audit, and it can also stand on its own.

Last updated 6 November 2026.

Find out where you stand.

Tell us what you’ve built. We’ll agree the scope and the price with you before anything starts.

Talk to usSee an example report