Design engineer
Government software doesn't have to feel like government software.
I design for real operators — non-technical staff who need forms, flows, and dashboards they can finish without a manual. UX measured by adoption, not screenshots.
Good architecture is invisible.
Bad UX isn't.
I design the parts people touch — forms, flows, and dashboards that non-technical operators finish without a manual.
In this world
Before / after
Same data. Different respect for the operator.
Government tools are usually built for the database, not the human at the desk. Drag to compare the default with the redesign — bigger type, plain language, and a flow that finishes without a manual.
Assign items to an institution. We'll check stock for you.
| INST_ID * | select... |
| ITM_CODE * | |
| QTY_ALLOC * | 0 |
| BENEF_TYP | select... |
| RMK_TXT |
* mandatory. Use ALL CAPS codes. Contact admin for INST_ID mapping.
The gallery
Screens, up close
Enterprise modules and client builds — tap a tab to switch projects.
Material distribution, inventory & dispatch
01 / 06
The system behind the screens
Design tokens, not one-off styling
Colour, type and shape live as tokens so every screen stays consistent and themeable — the same discipline powering this site's three worlds.