I lead product design across the eight modules. UX strategy, the design system, and the one AI pattern every AI feature here is built on.
This is the overview. Deeper case studies cover the design system, the KPI dashboard builder, the AI RFQ experience, and vendor certificate management.
HikeOn is a multi-module ERP for a US foodservice and sustainable-packaging brand with a 30,000-SKU catalog.
When I joined the back office ran on disconnected tools: a separate PIM, spreadsheets for forecasting, a custom queue for print orders, supplier POs in email threads.
There was no shared design system, and AI features were being bolted on one modal at a time. The business was scaling. The tooling wasn't.
Design direction for the whole product, reviewed monthly with the PM and founder.
Sole owner: architecture, tokens, governance and the Figma ↔ Vue.js handoff.
The interaction model all eight AI use cases are built from.
The highest-margin category and the messiest one operationally. I led that module myself.
I resisted the pull to start redesigning screens. Twelve engineers were already building. Start with screens and they end up rebuilding behind you.
250+ components on a three-layer token architecture. Maps 1:1 to Vue.js. Light, dark and density resolve through the same tokens, so nothing forks.
Full case study →One pattern: suggestion, confidence, "why this?", accept / edit / dismiss. All eight use cases are built from those four parts, so an operator learns it once and knows what they are looking at everywhere else.
See it applied →
A single custom-print order runs through artwork upload, MOQ and material checks, a proof cycle, supplier handoff, press scheduling and sample approval. Which suppliers are involved depends on the substrate.
It was tracked in Slack, not the system. The product was heading toward a stack of modals. I built one ordered surface per order instead.
Operators were jumping between artwork, supplier and customer threads. The timeline puts all of it in one order.
"Awaiting customer approval" is a state the system holds, and it has an SLA on it. Nobody infers it from an email thread.
Every order used to need a brief assembled by hand from three places. Now it is one action.
The system is in production and still growing. Specific outcomes, like the 85% of vendor certificates that auto-validate without manual re-key, sit in the deeper case studies.
Spending the first months on a system and a pattern instead of screens felt slow to everyone except the twelve engineers who stopped rebuilding the same things.Principle carried forward · HikeOn ERP