The product design process is how a team gets from a business opportunity to a product that people use and that moves the numbers. It’s broader than UX craft: it starts with strategy — what to build and why — and only then moves into experience, interface and delivery. Get the front of the process right and everything downstream is cheaper; skip it and you build the wrong thing beautifully.
At Biotik we run this whether we’re shaping a first MVP or reworking a mature product. Here are the phases, and how each ties back to the business.
1. Discovery & strategy
Before any design, get clear on the opportunity: the customer, the market, the business model and the one metric that matters most right now. Product design earns its keep here by refusing to treat “build feature X” as a given and asking what outcome you’re actually chasing.
- Customer and market research; jobs-to-be-done
- Business goals and the metric to move (acquisition, activation, revenue)
- Scope and constraints — what’s in, what’s explicitly out
2. Define the problem
Turn discovery into a sharp, prioritised problem statement everyone agrees on. For a new product this is where the MVP takes shape — the smallest thing that delivers real value and tests the riskiest assumption. Deciding what not to build is as important as deciding what to.
3. Ideate & design the experience
Now the design work: user flows, information architecture and the interface, built from reusable components. This is the UX and UI layer of product design — structure first, then surface — always in service of the outcome defined earlier, not decoration for its own sake.
- Flows and information architecture
- Wireframes, then high-fidelity UI
- Content and interaction design
4. Prototype & test
Make it clickable and put it in front of real people before engineering commits. Prototyping and usability testing de-risk the expensive part — the build — by catching confusing flows and false assumptions while they’re still cheap to change. On an existing product, a UX audit plays the same role in reverse.
5. Build, ship & measure
Design doesn’t end at handover. The team ships production-ready screens plus a design system engineering can build against, then watches the metric it set out to move. Product design is accountable to that number — if it didn’t move, the process feeds the learning back into the next cycle.
How it differs from “UX design”
UX design is a phase within this — the craft of making the experience usable. Product design wraps around it, adding the strategy at the front (what to build, for whom, to what end) and accountability at the back (did it work?). One is about getting the interface right; the other is about getting the whole bet right. On most engagements they’re done by the same senior team, moving fluidly from business goal to shipped screen.
