01 — Product Design
Product
Design
We work with founders, product teams, and the occasional brave enterprise on products that need to hold up — under user scrutiny, engineering reality, and the pressure of what comes next.
Our process starts with the uncomfortable questions: what problem are we actually solving, who holds that problem and what does their world look like, and what would winning feel like in six months. The answers usually reveal that the brief needs to change before the work begins.
We stay close to the build. Design fails in handoff when nobody owns the gap between Figma and production. We don't produce artefacts and disappear — we stay in the room until the product ships in the same shape it was designed.
What's included
- 01Discovery & Research
Not just user interviews. We map the actual problem space — current mental models, workarounds, decision contexts, competitive dynamics — before drawing a single frame. The output is a shared understanding that prevents false starts, not a research report that gets filed away.
- 02Information Architecture
The invisible layer that determines whether users learn your product quickly or never learn it at all. We design the mental models you want users to have, then map every structural decision — navigation, hierarchy, flows, labels — against that model. Ambiguity in IA shows up as support tickets and churn.
- 03Interaction Design
Every state a component can be in. Every transition between states. Every error condition, loading state, and empty state. Every micro-interaction that either builds confidence or erodes it. This is the work that separates products that feel considered from products that feel assembled in a hurry.
- 04Visual Design
The layer that makes intent legible at a glance. Typography that guides without demanding attention. Colour that communicates before language does. Spacing that creates relationships between elements. We design visually with the same rigour we apply to interaction — system-first, never decoratively.
- 05Prototyping & Validation
We prototype to answer specific questions, not to impress stakeholders. Paper for flow logic. Mid-fidelity for interaction assumptions. High-fidelity for visual sign-off. The fidelity matches the question — nothing more, nothing less.
- 06Handoff & Documentation
Most designs fail in the gap between Figma and production. We close that gap with documentation that engineers don't have to interpret: every state, every edge case, every responsive behaviour annotated and explained. Specs that stand up when we're not in the room.
04 — Start a Conversation
Most projects start with a short conversation. Tell us what you're building and we'll tell you honestly whether we're the right fit.
Get in touch.