Observed the real process
Ran on-site research and documented the analogue end-to-end workflow, surfacing issues such as missing auto-save, destructive edits and broken media handling.
01 / 05
From fragmented paper records to one traceable lifecycle
The product replaces a legacy workflow built around paper, disconnected media and repeated manual entry.
Staff previously had to re-type records across systems while tracking physical items through multiple locations and custody changes. Important operational details were difficult to maintain, and written requirements did not fully reflect the realities of work on site.
The platform is designed to create a single, auditable view of every item and every change throughout its lifecycle.
~40
Requirements restructured
2
Connected product workstreams
1
Shared audit trail
QR
Physical-to-digital labelling
02 / 05
Leading the design workstream end to end
I owned the design direction, not disciplinary people management.
As the Product / UX Design Lead, I led discovery, requirements definition, interaction design, prototyping and design delivery across web and mobile. I translated legal, domain and operational constraints into journeys, task flows, wireframes and interactive prototypes.
I worked as the design voice inside a cross-functional team of concept specialists, engineers and public-sector domain stakeholders, using prototypes and documented decisions to make complex discussions concrete.
03 / 05
A simpler path from field research to build-ready flows
Reframed the requirements
Turned roughly 40 fragmented requirements into a screen inventory and information architecture organised around core domain objects.
Designed the core product
Created the filterable registry, rich item detail with audit history, guided capture wizard and nested storage-location management.
Worked within the system
Built on the mandated government component library, documented gaps and fed them into the shared design-system process.
Made blockers visible
Maintained a decision register for unresolved questions so stakeholders knew what was blocking design and when a decision was needed.
Aligned before build
Embedded design in requirements workshops so flows and components were agreed with concept and engineering before implementation.
04 / 05
Ways of working: from manual documents to AI-native requirements
What changed
Structured source of truth
Requirements moved into a structured, version-controlled format in Visual Studio Code instead of being maintained as disconnected documents.
Agent-supported maintenance
AI agents create and update epics, user stories and feature roadmaps according to agreed standards, with the team reviewing and approving the output.
Design inside requirements
Concept, design and engineering agree flows and components together, reducing the gap between written intent, prototype and implementation.
Progressive rollout
I co-established the approach with engineering and introduced it progressively as the first use of this working model within the regional public-sector practice.
Next ambition: generate UI flows and initial screens from the same structured requirements, creating a tighter loop between requirement, prototype and build.
05 / 05
A clearer product direction with traceability built in
Product outcome
The design establishes one coherent place to capture, find and manage inventory while making custody transfers and record changes auditable. Because the project is ongoing, these are intended product outcomes rather than claimed measured impact.
Team outcome
The working model aligns concept, design and engineering earlier, makes unresolved decisions explicit and keeps requirements closer to the current development state.