Product design
We start with the job the product does and how people will use it, then design an interface that can be built and evolved.
Founders and product teams that need an interface for a real scenario, not a pile of screens.
From problem to interface
- Interviews and user-flow analysis
- Information architecture and screen structure
- Prototype and validation of the key path
- Visual language, components and design system
- Handoff to engineering with states and specs
What you get
- Flow map and priorities
- Clickable prototype
- Design system and tokens
- Engineering spec
Formats
Problem framing, flows, structure and a prototype of the key path. Validates an idea before engineering.
Components, tokens, states and rules for the team that will evolve the product.
What we need from you
- Product goal and core users
- Existing materials: analytics, interviews, designs
- Timeline and technology constraints
- Decision maker on the product
Boundaries. Design does not replace engineering or guarantee product success. Business decisions stay with the client.
FAQ
01Can we start without a spec?
Yes. The sprint is designed to frame the problem and validate the flow before engineering.
02What is delivered?
Flow map, prototype, visual language and an engineering spec.
03Do you work with existing products?
Yes. We start with an interface and flow audit, then propose an improvement plan.
Discuss a product.
Tell us about the task — we will propose a format and first step.