Product design
Product design is the least generative work we do. The hard part is deciding what to build, and no model has an opinion about your users. What tools accelerate is everything after that decision.
Embedded rather than commissioned
Product designers join your standups, read your tickets and argue with your engineers. They work at your cadence, not in monthly delivery batches, because a feature spec written in isolation is a document nobody follows.
From question to shippable spec
Work usually starts with flows and wireframes, moves through interface design once the shape is agreed, and ends in a spec covering states, edge cases and empty screens. The unglamorous states are where most handoffs quietly fail.
Working with your engineers
Designers here read the codebase constraints before proposing anything. If your framework makes a pattern expensive, we would rather know in week one than argue about it in a sprint review. Good product design is partly knowing what is cheap to build.
- Flows, wireframes, interface design
- Edge cases, empty and error states specified
- Joins your standups and ticket reviews
- Prototypes for testing before build
Questions about product design
Will the designer join our sprints?
Yes. Product designers sit in standups, read tickets and argue with engineers. They work at your cadence rather than delivering in monthly batches, because specs written in isolation get ignored.
What do we actually receive at the end?
Flows, wireframes, interface designs and a spec covering states, edge cases and empty screens. The unglamorous states are where most handoffs quietly fail, so they are documented explicitly.
Where to go next
Related pages people usually read alongside this one.
Tell us what needs designing
Send the brief in whatever state it exists. We read it before the call rather than making you present it.