What is product design?
The term covers two related crafts. In the physical world, product design, or industrial design, shapes objects: a chair, a speaker, a bottle, a lamp. In the digital world, which is how the term is most often used today, it means designing software products, the apps, tools and platforms people use again and again, and it spans the whole problem rather than one screen of it. A digital product designer works on what the product should do, how it is structured, how each flow behaves and what every state of the interface looks like.
It sits where three questions meet. Is it desirable: do people want it? Is it feasible: can it be built? Is it viable: does it work as a business? A product designer spends as much time with engineers, data and customer feedback as with a design file, because a beautiful interface for the wrong product is still the wrong product.
Why it matters
Why product design matters
A website is visited; a product is used, often daily, and every small friction is multiplied by every use. Good product design is why one tool becomes a habit and its competitor becomes a free trial that was never renewed. It shapes retention, support costs, word of mouth and how quickly new features can be added without breaking the old ones. It is also where a brand is lived rather than advertised: for the people who rely on it, the product is the brand experience, and no campaign can make up for a product that frustrates them.
In practice
How product design works in practice
- 01
Work starts with the problem. Research with the people who would use the product (interviews, observation, data from what they use now) defines what they are trying to do and where they get stuck. That becomes a set of flows and a structure, sketched and then prototyped, so ideas can be tried with real users before anything is built. Engineers are in the room early, because what is easy to build and what is hard often changes the design.
- 02
Then the product ships, and the real design work begins. Usage data, support conversations and direct feedback show what people actually do, and the design is refined in short cycles: a flow simplified, a feature removed, a new one tested with a small group first. A shared design system keeps the interface consistent as it grows, so the hundredth screen looks and behaves like the first.
At RIOT
Product design at RIOT
Alongside the work we make for clients, we design and run products of our own. Krova is production software, built as a web app. AltSounds is a music video channel and Muvvoo a music video database, both web products, and vandal_ is our creative shop. Building them in-house keeps us honest about the difference between a design that presents well and one that holds up when people rely on it.
Watch out
What people get wrong about product design
Equating it with the interface. The screens are the visible part, but most product design decisions are about what the product does and does not do, and the hardest is usually what to leave out. Second, designing features rather than outcomes: a roadmap of things to add instead of problems to solve. Third, treating launch as the finish line. A product that is not redesigned in response to how people use it slowly becomes a product nobody chose.
