Shopbox: unifying a fragmented POS ecosystem
How I redesigned the core POS and back-office experience, established a shared product language and later moved into product leadership.
At a glance
The challenge. Shopbox served two very different environments. Retail staff needed an interface that was fast and predictable during service, while owners and finance teams needed to manage increasingly complex information across stores, products, transactions and employees. The existing experience had grown unevenly across the POS app and web back-office — the problem was not simply visual inconsistency, the product needed a clearer underlying system.
My role. I joined Shopbox as a designer working across the entire product: redesigning information architecture and interfaces, designing new product flows, conducting research with customers and working closely with development, sales and the CTO on product logic. As the redesign matured, my role gradually expanded into product leadership, including prioritisation, specifications, stakeholder communication and distributed delivery.
One ecosystem, multiple interfaces: the iPad POS built for speed during service, and the web back-office built for denser management workflows.
Establish one product language
We adopted Material Design as a common foundation across the iPad POS and web back-office. The objective was not to apply a visual style. It was to reduce the number of different interaction patterns users and developers had to understand. From that foundation, I designed reusable patterns and established greater consistency across the wider system.
The system made future feature development easier because common behaviours no longer had to be reinvented for every screen.
Consistency is useful when it reduces decisions.
A shared design language meant common behaviours no longer had to be reinvented for every new screen.
Design the POS for speed
The POS lived in a very different environment from a conventional web product. A café or restaurant employee does not want to explore an interface — they need to complete an action quickly while other things are happening around them.
I worked across flows including ordering, tables and rooms, payments, receipts, search, editing, onboarding and different company structures. Interaction decisions prioritised speed, clear status and predictable feedback.
The receipt and kiosk module, designed for quick recognition under time pressure.
Make the back-office understandable
The web back-office had to support much denser workflows: products, inventory, transactions, sales reporting, customers, staff and store configuration.
I worked with the CTO, developers and sales to rethink not only the screens but parts of the underlying logic. The goal was a system where navigation, data entry and management behaviours remained predictable as functionality expanded.
The back-office dashboard, built for owners and finance staff managing multiple stores.
Move from interface problems to product problems
As the redesign became more established, my work increasingly moved upstream. I became more involved in feature opportunities, prioritisation, product specifications, client requirements, communication with development and long-term product direction.
Working with a geographically distributed development team also exposed problems that design files could not solve. That experience later became the subject of my Master's research into distributed software development, and it influenced how I structured specifications and team communication from then on.
A design system cannot repair unclear product logic.
Visual consistency helped, but some of the hardest problems required changing how the product itself behaved — not just how it looked.
What changed
Core workflows redesigned around daily operational use.
Shared navigation and interaction patterns across complex management workflows.
Common patterns that reduced unnecessary reinvention.
More structured specifications, prioritisation and communication with the distributed team.
Interface problems often reveal deeper problems.
A design system cannot repair unclear product logic. That experience shaped how I work today — I rarely treat UX as the final layer of product development. Interface problems often reveal deeper problems in information architecture, priorities or product logic.
Have something worth building?
I'm interested in senior product, product design and hybrid leadership roles.