When good design becomes a safety feature

An offline-first assessment system designed for instructors working in forests, farms and remote environments where reliability mattered more than aesthetics.

Case study overview

I realised very quickly that this wasn't a design problem. It was a reality problem.

The first designs I was shown looked beautiful.

They'd been produced as large A3 Photoshop files with tiny text, intricate layouts and almost no consideration for the devices instructors actually carried into the field.

Then I thought about where these people were using them.

Standing in woodland.

Working in bright sunlight.

Sometimes in heavy rain.

Often wearing gloves.

Usually with little or no mobile signal.

Nobody was sitting behind a desk admiring beautifully crafted layouts. They were trying to assess learners safely while standing outdoors.

That changed how I thought about the project.

The goal wasn't to make the app look better.

It was to make it disappear into the background so instructors could focus on the people in front of them rather than the technology in their hands.

Good design isn't what looks best in the studio. It's what still works when you're standing in a muddy field wearing gloves.

The project moved from digitising paperwork to designing for the real world.

The original thinking focused on replacing paper forms with a digital alternative.

Once we started working with instructors, it became obvious that simply recreating paper on a screen wouldn't be enough.

The app needed to survive poor signal, changing weather, bright sunlight and long working days without becoming another thing instructors had to think about.

That meant stripping away unnecessary complexity and designing around the realities of the environment rather than around the office.

The result wasn't simply a tablet application.

It became a resilient offline-first assessment platform that instructors could genuinely trust.

Every decision started with the environment, not the interface.

Design, development and product thinking happened together.

I discarded the original Photoshop handover almost immediately and rebuilt the product through interactive Figma prototypes that could switch between low and high fidelity depending on the conversation we needed to have. Stakeholders could discuss workflows without being distracted by visual design, then move seamlessly into polished prototypes when required.

Working closely with the engineering team, I developed components directly alongside implementation, resolving edge cases while the product was being built rather than documenting them for someone else to solve later.

At the same time I introduced reusable interaction patterns, accessibility standards and frontend components that became the starting point for future Redox products rather than existing only inside this project.

This project changed how I think about context.

Before Lantra, I tended to think about interfaces first.

After Lantra, I thought about environments.

A screen doesn't exist in isolation.

Sometimes it's used in an office.

Sometimes it's used in bright sunshine.

Sometimes it's being held with muddy gloves while somebody is responsible for another person's safety.

Good products begin by understanding those moments.

That lesson has stayed with me ever since.

Whether I'm designing enterprise software or building QuietStrength, I always try to understand where the product actually lives before deciding what it should look like.