As a professional UX designer, my most complex web design project involved creating an application specifically tailored for firefighters. The goal was to develop a comprehensive tool that would assist them in gathering building and site information, conducting annual fire checks, and managing keys to various properties.
One of the most complex design projects I have worked on was a web application built specifically for firefighters.
At first glance, the brief sounded straightforward: create a tool that helped fire services collect building and site information, complete annual fire safety checks, and manage access keys for different properties.
But the deeper I got into the project, the clearer it became that this was not just another admin system.
This was a product for people who might need information quickly, under pressure, in difficult physical conditions, and sometimes while responding to an emergency. The users were not sitting comfortably at a desk with time to explore a complicated interface. They could be in a moving fire truck, wearing heavy gear, dealing with poor visibility, noise, stress, and limited time.
That changed everything.
The challenge was not simply to design something that looked good. The challenge was to design something that could stay useful when the environment around the user was chaotic.
Understanding the real context
I started with a user-centred design approach, but in this project that meant going beyond standard requirements gathering.
I conducted interviews with firefighters to understand how they worked, what information they needed before arriving at a site, what slowed them down, and what could create risk during an incident. I wanted to understand not only what the application needed to contain, but also when, where, and how that information would be used.
A key insight was that firefighters did not need more information. They needed the right information, presented clearly, quickly, and in the correct order.
In emergency contexts, too much detail can become noise. The interface had to help users make fast decisions, not force them to search through layers of data.
Designing for pressure, not perfection
The application had to support several important tasks:
Firefighters needed to see key building and site details at a glance. They needed to know the best route from the fire station to the location. They needed to find out where property keys were stored. They also needed to identify vulnerable areas, high-risk zones, hazards, and other critical information before arriving on site.
Because the users were not necessarily highly technical, the interaction model had to be simple and predictable. I focused on a modular structure, clear hierarchy, large touch-friendly areas, and high-contrast screens that could be read quickly in poor conditions.
The design avoided unnecessary complexity. Instead of trying to show everything at once, the application surfaced the most important information first, then allowed users to access deeper details when needed.
The goal was to reduce cognitive load. In practical terms, that meant fewer decisions, clearer labels, obvious actions, and layouts that could still make sense in a stressful environment.
Collaboration and iteration
This was not a project that could be designed in isolation.
I led weekly workshops and demos with the wider project team to keep everyone aligned. These sessions helped turn abstract requirements into practical product decisions. They also gave developers, stakeholders, and subject-matter experts a shared understanding of why certain design choices mattered.
I worked closely with the development team throughout the process to make sure the design was realistic to build and that the final implementation preserved the core user experience.
Usability testing with firefighters was especially important. Their feedback helped validate the structure, highlight confusing areas, and refine the interface so it better matched their real-world workflow.
What made the project complex
The complexity of this project did not come from flashy features or unusual technology.
It came from the responsibility of the context.
Designing for firefighters meant designing for users who may be tired, distracted, under pressure, and physically restricted by their environment. It meant creating an interface that could support preparation, inspection, and emergency response without getting in the way.
Every design decision had to answer a simple question:
Will this help someone find the right information faster when it matters?
That question became the centre of the project.
The outcome
The final product was a practical, accessible, and highly focused application that helped firefighters manage site information, inspections, keys, routes, and risk areas in one place.
More importantly, it presented that information in a way that matched the reality of their work.
This project taught me that complex UX is not always about designing more. Sometimes, the hardest and most valuable work is deciding what to remove, what to prioritise, and how to make a product feel calm and reliable in a high-pressure situation.