
obvious
Redesigning the asset register of a health & safety platform, so crews can trust what they see and coordinators can't get it wrong.
CASE STUDY .
MY ROLE
Product Designer (UX/UI)
1 Day
Create . Move . Deactivate
Figma . Figma Make . Claude
TIMELINE
SCOPE
TOOLS
DESIGN CHALLENGE


A one-day take-home design challenge for an EHS software company. Brand, data and screens are anonymised; “Fieldline” is a placeholder name.
Making "safe to use?"
This project focused on improving the Asset Register experience by making equipment safety status clearer and easier to understand. The goal was to help users quickly identify whether an asset is safe to use, requires attention, or needs further action, while simplifying key workflows such as adding assets, completing required fields, and managing safety information. Through a user-centered redesign, I aimed to reduce confusion, prevent mistakes, and create a more intuitive and efficient experience.
Project Overview


THE CHALLENGE
An EHS platform keeps a register of every physical asset a company owns: trucks, excavators, gas detectors, fire extinguishers. Each one is linked to the inspections people complete for it.
ONE DAY TO FIX THE SCREENS CREWS RELY ON FOR SAFTY


Safety coordinators and fleet managers manage dozens to hundreds of assets, on desktop and under time pressure. Above all, they need to know which assets are safe to use today.




DESCOVERY
I audited the current list, view and create screens and logged 18 issues. Four of them shaped everything that followed.
Before designing anything, I clicked through every screen


18
issues found
Also: no required-field markers · hex codes for colour · mileage on fire extinguishers · an always-editable view page · “Are you sure?” as the only warning before deactivating. Illustrations are simplified recreations.
FRAMING
One question to design around






HOW THE DAY WENT


Decision 1
A list that leads with safety


ASSET LIST
Status pills, the only colour
Text, icon and colour together. Custom colours no longer compete with safety.
“4 pending forms” replaces an unlabelled number badge.
Chips that count and filter
One click answers “what isn't safe today?”
Out of Service and In Repair rise to the top of every category.
Unsafe assets first
Counts on every tab
Category tabs on top, Active / Deactivated inside, so lifecycle and status never mix.
Pending forms in words
Decision 2
Creating an asset in four required fields


Status pills, the only colour
Text, icon and colour together. Custom colours no longer compete with safety.
“4 pending forms” replaces an unlabelled number badge.
Chips that count and filter
One click answers “what isn't safe today?”
Out of Service and In Repair rise to the top of every category.
Unsafe assets first
Counts on every tab
Category tabs on top, Active / Deactivated inside, so lifecycle and status never mix.
Pending forms in words
CREAT ASSET . THE REQUIRED STORY
Decision 3
Make mistakes cheap, and the next step obvious


“Start inspection” is the next step
The user story ends with crews inspecting the asset, so the page leads there. A toast links back to the list.
Read-only by default
The old view page was always in edit mode. Now, editing is a deliberate choice.
Nothing hides on a long form. Section numbers turn red, so problems are easy to spot.
An error summary that links to each field
Errors that explain the fix
“Enter a 10-digit phone number, like (555) 010-2214.” Errors clear as soon as the field is fixed.
VALIDATION AND NEXT STEP
Decision 4
Risky actions that explain themselves


Deactivate: consequences, not “Are you sure?”
Warns about pending forms, keeps history, records a reason, offers the safer option (Out of Service), and ends with Undo.
Shows the current and new category, asks for a valid type, and lists what moves with the asset: forms, notes, history.
Move: from → to, and what comes along
Both live behind a “More” menu on the asset page. They're rare and risky, so they shouldn't sit next to everyday actions.
MOVE & DEACTIVATE . OPTIONAL STORIES
15 addition, zero new colours


Every new component is built only from the existing tokens, so it's easy for developers to build and is consistent across screens.
SYSTEM THINKING




How I used AI to move fast, without handing over the thinking


A full audit, two design directions, nine screens, two prototype flows and a documented design system don't usually fit into one day. AI made that possible. I used it as a fast collaborator and kept every decision.
AI - ASSISTED WORKFLOW






WHERE | OVERRULED AI
What one day taught me
REFLECTION


How I worked with AI: Claude helped me audit, compare directions and draft copy and prompts; Figma Make generated first-pass screens from my spec. The judgement, decisions and final file were mine, and I reviewed everything AI produced.



