Services
Product Design
Working out how the product should behave before development turns every change into an expensive one.
A good fit when an idea needs structure before development starts, or when an existing workflow has become harder to use than it should be.
Tell us what you are working onWhat this can include.
We help shape the product itself: what problem it is solving, which journeys matter most, what information belongs on each screen and how the interface should respond when things go right or wrong. The design is made to survive implementation, not just look good in a prototype.
The exact scope depends on the product, the team and what already exists. These are the areas we can bring into the project when they are useful.
- Discovery and research
- Product strategy
- User flows and wireframes
- UI and design systems
- Interactive prototypes
- Usability review
How we usually think about it.
- 01
Work out the decision or task the product is helping with
We clarify the audience, the problem and the smallest useful experience. Mapping the important journeys early usually exposes missing information and competing priorities before they become expensive code changes.
- 02
Design the whole flow, not only the happy path
Wireframes and prototypes cover the order of actions, the words people see and the feedback they receive. Empty, error and confirmation states are included because those are often the moments when people decide whether they trust the product.
- 03
Use a visual system that can survive development
Typography, spacing, color and reusable patterns keep the product consistent. We make design decisions with implementation in mind so the finished build does not drift away from the prototype.
A real example
SpendWise
A WianTribe product · In development
SpendWise shows these decisions in practice: matching-period comparisons, clearly labelled estimates and a statement preview before anything is saved. It is WianTribe's own Android product in development, using fictional sample data in the case-study screens.
Read the SpendWise case studyA couple of common questions.
Can we do a design phase before committing to development?
Yes. A discovery or prototype phase can help answer the important questions before a larger build starts. We agree what needs to be learned and what deliverables will be useful before deciding how far to take that phase.
What can a design handoff include?
Depending on the project, it can include user flows, interface designs, reusable patterns, responsive layouts and behavior notes for important states and interactions.
Let’s talk
Got something you're trying to build?
You do not need a finished brief. Tell us what you are working on, what is not working yet and what you would like the product to do. We can take it from there.