Back to Blog
Visual Design & Branding

Product design: what it is and how teams resource it

·9 min read
person writing on white paper

Product design is the discipline of shaping how a digital product works and feels for the people who use it. It combines user research, information architecture, interaction design, and visual design to solve real user problems inside business constraints. A product designer moves from understanding a problem to wireframes, prototypes, testing, and a polished interface that ships.

Key takeaways

  • Product design covers the full path from user research to a shipped, usable interface, not just the visual layer.
  • UX design defines how a product works and UI design defines how it looks; strong products need both.
  • The process runs through discovery, definition, wireframing, prototyping, visual design, and testing, then repeats.
  • Product design differs from graphic and web design because it centers on interaction, usability, and iteration over time.
  • Teams resource it in three ways: in-house designers, a product design agency, or a subscription for the visual and UI layer.

What product design is

Product design is the practice of deciding what a digital product should do, how it should behave, and how it should look, all in service of a user goal. The word product matters here. A product designer is responsible for outcomes: does the feature get used, does the user complete the task, does the business metric move. That is a wider remit than making screens attractive.

In practice, product designers sit between users, engineering, and the business. They talk to users to learn what is actually broken, translate that into flows and screens, prototype the solution, test it, and hand a build-ready design to engineers. The role blends research, systems thinking, and craft. For a fuller picture of the day-to-day work and the skills involved, see our guide on what a product designer does.

UX design and UI design

People use UX and UI interchangeably, and that causes real confusion. They describe different work. User experience design, or UX, is about how a product works: the flows, the logic, the order of steps, and whether a person can actually get where they are going without friction. User interface design, or UI, is about how the product looks and responds: the buttons, type, color, spacing, states, and motion that make a flow tangible.

A useful way to hold the distinction is that UX decides that a checkout should be three steps, and UI decides exactly how each of those three screens looks and feels to tap through. A product with great UI and broken UX frustrates people who cannot find what they need. A product with sound UX and weak UI works but feels cheap and loses trust. Serious products invest in both, and many designers practice both. Our deeper piece on UI and UX design unpacks how the two disciplines fit together on a real team.

The product design process, stage by stage

Product design follows a repeatable process. The exact names vary by team, but the shape is consistent: understand, design, validate, refine. It is a loop rather than a straight line, because testing sends you back to earlier stages when something does not work.

Stage What happens Typical output
Discovery and research Interview users, study behavior, review data, define the problem Research findings, personas, problem statement
Definition Frame the goal, scope, and success metric; map user flows Flow diagrams, requirements, success criteria
Wireframing Sketch low-fidelity structure and layout of each screen Wireframes, information architecture
Prototyping Build a clickable model of the flow to feel the interaction Interactive prototype
Visual and UI design Apply brand, type, color, components, and states High-fidelity screens, design system pieces
Testing and iteration Put the design in front of users, measure, and refine Usability findings, revised designs, build-ready handoff

The stages that teams most often skip are discovery and testing, because they feel slower than jumping to screens. That is usually a mistake. A widely cited figure in the field holds that fixing a problem after development costs many times more than catching it in design, which is the entire economic argument for prototyping and testing before engineers write code.

How product design differs from graphic and web design

Product design, graphic design, and web design overlap in visual craft, and that overlap hides real differences in what each one is for. Graphic design communicates a message through a mostly fixed artifact: a logo, a poster, an ad, a brand system. The output is seen more than it is used. Web design builds sites, often marketing sites, where the primary goals are to communicate and convert a visitor.

Product design centers on interaction over time. A product is something a person returns to and operates, so usability, state, edge cases, and iteration dominate the work. A product designer thinks about the empty state, the error state, the hundredth visit, and how the design holds up as features are added. That is why product design leans so heavily on research and testing while graphic design leans on visual concept and message. The tools reflect it too: product teams work in Figma with reusable components and prototypes, where graphic designers often work in Adobe Illustrator or Photoshop on fixed compositions. Choosing the right discipline for a job starts with asking whether people will look at the thing or operate it.

How teams resource product design

Teams staff product design in three main ways, and most growing companies mix them. The first is in-house: hiring product designers as employees. This gives deep product context and tight collaboration with engineering, at the cost of a full salary and the time to recruit. A senior product designer in the United States commonly costs well over one hundred thousand dollars a year in total compensation, which is a real commitment for an early team.

The second is a product design agency or studio, engaged for a defined project such as a new app or a major redesign. Agencies bring senior talent and process for a fixed window, which suits a big push, though they cost more per hour and hold less ongoing context than an employee. Our guide on how product design firms work and how to hire one covers that route in depth. The third is a design subscription, which is best suited to the visual and UI layer: the high-fidelity screens, marketing pages, and brand assets that flow out of the product work. Many teams keep strategy and research in-house, then use a subscription to execute the visual output at volume without new hires.

A practical way to pick a model is to look at how often the product changes. A pre-launch startup still searching for product-market fit gets the most from an in-house or embedded designer who can sit in every product decision as the direction shifts week to week. A company with a stable core product and a steady stream of new marketing pages, feature screens, and brand assets often gets more from a subscription that executes the visual layer quickly. A one-time redesign of a mature app is the classic case for a project-based agency. Most teams pass through all three arrangements as they grow, and mixing them is normal rather than a sign of indecision.

A design subscription such as Design Pal gives product teams senior-level UI and visual design at a flat monthly rate, with source files in Figma and unlimited revisions, so the visual layer keeps pace with the roadmap. You can see the plans on Design Pal’s pricing page.

Frequently asked questions

What is the difference between UX and UI design?

UX design, or user experience design, defines how a product works: the flows, logic, and steps a person moves through to complete a task. UI design, or user interface design, defines how the product looks and responds: the buttons, type, color, spacing, and states. UX decides the structure of a flow, and UI decides how each screen in that flow looks and feels to use.

What are the stages of the product design process?

The process usually runs through six stages: discovery and research to define the problem, definition to set goals and flows, wireframing to sketch structure, prototyping to build a clickable model, visual and UI design to apply brand and components, and testing and iteration to validate with users. It loops rather than runs straight, since testing often sends the work back to earlier stages.

How is product design different from graphic design?

Graphic design communicates a message through a mostly fixed artifact such as a logo, poster, or ad, meant to be seen. Product design shapes a digital product that people operate over time, so it centers on interaction, usability, edge cases, and iteration. Product design leans heavily on research and testing, while graphic design leans on visual concept and message. The output of one is used; the other is viewed.

How do teams resource product design?

Teams resource product design three ways. In-house designers give deep context and tight engineering collaboration at the cost of full salaries. A product design agency brings senior talent and process for a defined project such as a redesign. A design subscription suits the visual and UI layer, executing high-fidelity screens and brand assets at a flat monthly rate. Many companies combine in-house strategy with a subscription for execution.

Mountain landscape

Your team's
design team