# Product Design

Product design shapes how a product addresses user needs through its capabilities, interactions, content, and form within real constraints.

- Type: practice
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-20
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/product-design/>)

## What it means

Product design is the practice of investigating needs, exploring possible solutions, and refining how a product works and appears. In digital products it connects research, interaction and visual design, prototyping, and evaluation. Role boundaries vary, but the work requires collaboration with product management and engineering throughout discovery and delivery.

## Why it matters

A feature can satisfy a written requirement while leaving people confused or unable to achieve their goal. Product design makes assumptions visible and examines the experience as a whole, helping the team choose a useful approach before and after release.

## When to use it

Use product design when creating a product, changing a workflow, or improving an existing experience. The depth of exploration should match the uncertainty; a well-understood maintenance change does not need a full discovery cycle.

## How it works

1. Understand the people, context, desired outcomes, and constraints.
2. Frame the problem using research and operational evidence.
3. Explore alternative capabilities and interactions rather than committing to the first screen idea.
4. Prototype and evaluate the uncertainties that matter most.
5. Collaborate on content, accessibility, technical behavior, and implementation details.
6. Review real use after release and adapt the design.

## A practical example

A document-sharing team investigates why invitations fail. Instead of only redesigning the button, it explores permission language, recipient identity, and recovery from a wrong address. The final design includes an understandable permission choice and a way to correct an invitation.

## Where it breaks

Design cannot independently guarantee demand, technical feasibility, or commercial viability. Time and access to users constrain learning. Attractive artifacts can conceal weak problem understanding, and title-based ownership can obstruct collaboration.

## Common mistakes

- Treating product design as visual decoration after requirements are fixed.
- Counting screens produced as customer value.
- Ending design involvement at handoff.

## Sources

1. [Product Design](<https://ixdf.org/literature/topics/product-design>) — Interaction Design Foundation · Educational reference
2. [The Double Diamond](<https://www.designcouncil.org.uk/resources/the-double-diamond/>) — Design Council · Method guide

## Related topics

- [Product Trio](<https://wiki.soroush.uk/topic/product-trio/>)
- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
- [Design Handoff](<https://wiki.soroush.uk/topic/design-handoff/>)
