Concept
Meridian
Web applicationAn operations platform concept for logistics teams who currently run scheduling across three spreadsheets and a group chat.
- Product strategy
- UX architecture
- Web application
- Backend
Design
Designed for people. Engineered for scale.
Design is where a product becomes understandable. Structure first, interface second, decoration almost never.
Technology
- Figma
- Design tokens
- Prototyping tools
- Component documentation
The problem
What usually goes wrong
Screens get designed before anyone agrees what the product does. The result is a beautiful set of images that fall apart the moment real data, empty states and errors arrive.
Or design is treated as a final coat of paint, applied to a structure nobody questioned.
Our approach
What we do instead
We work from the flow outwards: what the user is trying to finish, what they need to see, what can be removed.
Then we build a system — type scale, spacing, components, states — so the product stays coherent as it grows and engineering has something real to build against.
Capabilities
User and stakeholder research
Information architecture
Flow and journey design
Wireframing and prototyping
Interface design systems
Design tokens and component libraries
Accessibility and contrast standards
Motion and interaction specification
Design-to-engineering handover
Deliverables
What you actually receive.
Scoped per engagement — this is the shape of it, not a fixed package.
01Flows and information architecture
02Interactive prototype for key journeys
03Interface design across breakpoints
04Component library with states
05Design tokens ready for implementation
06Accessibility annotations
Process
How this work runs.
Six stages, adapted to the shape of this particular engagement.
01
Understand
Users, business constraints and existing evidence.
02
Structure
Flows, hierarchy and information architecture.
03
Prototype
Make it clickable before it is pretty.
04
Design
Interface, system and every state that matters.
05
Specify
Tokens, components and handover engineering can use.
06
Support
Stay involved while it is built.
Related work
Where this shows up.
Internal concepts and prototypes that exercise this capability. Labelled, because they are not client engagements.
Yes. We hand over documented systems your engineers can implement, and stay available during the build.
As much as the decision requires. Sometimes that is six interviews; sometimes it is reading your support tickets.
Next step
Product hard to use, or hard to explain?
Tell us the situation in a couple of sentences. We will come back with what we would do first, and whether we are the right people for it.