Where this has been tested
Thirteen years on systems where the complexity is not in the interface. It is in the relationships between people, data, and state, and in what happens when one of them is wrong.
Transport planning and management platform
Founding designer. Pre-seed to growth.
Not a delivery app. A system coordinating dispatchers, drivers, and automated route optimisation across hub-to-hub and last-mile distribution, at FMCG scale, multi-stop and multi-constraint, running as one ecosystem.
Marine supply logistics marketplace
Co-founder and product lead. Early stage to acquisition.
Vessel operators, suppliers, and transport partners, coordinating deliveries inside tight scheduling windows. Led product and design from inception through the acquisition.
Integrated operations platform
Product architect. Enterprise, current.
Offshore and onshore teams working from the same system, where permit to work, equipment status, and operational oversight all have to talk to each other across safety, maintenance, and compliance.
The through-line
Systems where the complexity lives in the relationships between actors and data states, and where a wrong design decision has a physical consequence. Thirteen years. Still a designer at heart. Just a very practical one.
Working on something like this?
If you are building something complex and want a second read on it before it gets expensive, write to me.