06 / Services
Product Design
Most product failures are decisions, not code. We define scope, model the user experience, and prototype the hard parts first, so engineering builds the right thing once.
When this applies
Reasons companies call us about this.
If more than one of these is true, this is probably the right starting point.
- You know the problem and not the product
- Stakeholders disagree on what is being built
- An existing product confuses new users
- You need something credible to show before you fund the build
Scope
What the engagement includes.
Scope is written down and approved before engineering begins. Anything outside it is quoted, not assumed.
Deliverables
- Discovery, research, and scope definition
- User flows and information architecture
- Interface design and design system
- Interactive prototypes
- Design-to-engineering specification
- Usability review and iteration
Technology
- Figma component systems
- Design tokens
- Clickable prototypes
- Accessibility standards
- Responsive and adaptive layout
- Motion specification
How we work
The phases for this work.
- 01
Discover
Understand the company, the users, the business model, the technical environment, and the objective.
- 02
Define
Set product scope, architecture, priorities, and the technical requirements that follow from them.
- 03
Design
Build the user experience, interface system, prototypes, and product flows.
- 04
Build
Engineer the application on an architecture meant to survive its second year.
- 05
Validate
Test functionality, responsive behavior, performance, accessibility, and integrations.
- 06
Launch
Deploy, instrument, monitor, and support the product in production.
Related
Capabilities that usually pair with this.
Start a project
Have a product design project?
Send the problem, the constraints, and the timeline. We will come back with scope, approach, and a number.
Custom product engagements typically begin at $10k.