Skip to content
Back to blogs

Product design sketching

TL;DR: Product design sketching uses quick drawings to explore a proposed experience. Sketch one task, show the important choices and feedback, then use the discussion to decide what to prototype. Clear thinking matters more than polished drawing.

Rewritten and updated from All About Product Design Sketching, originally published . Original archive byline: magic213.

A designer’s desk with a laptop, sketching tools, plants and a whiteboard

Photography by Mia Baker / Unsplash

In this article

Introduction

Product design sketching is the use of simple drawings to explore how a product could work. For a website or app, a sketch can show a layout, a sequence of screens or the response to an action. Use it to compare ideas before investing in detailed design.

What to put on paper

Start with the person, their goal and the point where they need help. Draw the information and controls needed for that task, then show what happens after an action. A short annotation can explain behaviour that a static box cannot.

A sketch is a discussion tool. It can expose a missing decision or suggest another approach, but it does not confirm that the experience is usable or technically ready.

Sketch before polishing

Sketching makes different interpretations visible while they are still inexpensive to change. Compare the structure and journey before debating colour, typography or decorative detail.

  • Exploration: several possible arrangements can be discussed without presenting one as final.
  • Explanation: labels and simple sequences can make an unfamiliar interaction easier to follow.
  • Memory: notes beside a drawing can preserve the reason behind a decision.
  • Feedback: people can point to a specific part of the proposal and explain their question.
  • Handover: the team can identify which details need a wireframe, prototype or technical review next.

Make the idea understandable

Give each sketch enough context for someone else to walk through it. Include the start, the main choice, the response and a way back when something goes wrong.

Frame the question before drawing

Write one sentence describing what the team needs to understand. For example, you may need to decide where product information belongs or how someone moves from a preview to a comparison. That question gives the sketch a useful boundary and helps you avoid drawing unrelated detail.

Include enough context to explain the task. Name the person, the starting point and the result they need. If the drawing depends on an assumption about content or system behaviour, note it visibly. The conversation can then distinguish a design possibility from something already confirmed.

Show relationships and a sequence

Use simple shapes, arrows and labels to show how the proposal fits together. A single screen can communicate hierarchy, while a short sequence can explain what changes after an action. Choose the view that makes the important relationship easiest to discuss.

Use realistic content where it affects the decision. A product name, a long service label or an important explanation may change the arrangement. Placeholder boxes can hide those questions. The aim is not a polished layout; it is a clear representation of the information and choices the product will need.

Use the discussion to choose the next step

Ask people to walk through the task using the sketch. Note where they interpret it differently, what information they expect and which behaviours need clarification. Record the reasoning behind feedback so the next version addresses the question rather than simply accommodating a visual preference.

Decide what the sketch has answered and what remains unknown. Some decisions may need a more detailed wireframe or an interactive prototype. Others need research or a technical conversation. A drawing is useful when it helps the team choose the next activity with a clearer purpose.

Use the right level of detail
FormUseful forWhat to make clear
Exploratory sketchComparing early arrangementsThe question and the alternatives
Annotated sketchExplaining a proposed interactionLabels, sequence and assumptions
WireframeReviewing structure and contentInformation hierarchy and page relationships
Interactive prototypeTrying a proposed journeyWhich behaviours are demonstrated

Run a sketching session

Choose one question for the session and keep the drawing focused on it. Ask reviewers to describe what they think happens before explaining your intention.

  1. Choose a task. Describe the person and the action the product needs to support. Keep the scenario small enough to examine in one discussion.
  2. Draw more than one possibility. Explore different arrangements before treating a direction as settled. Vary the structure or sequence in a way that relates to the task.
  3. Add useful annotations. Label controls, information and important changes. Mark assumptions or unanswered questions beside the part of the drawing they affect.
  4. Walk through the proposal. Ask participants to explain what they think happens. Listen for missing context and different interpretations rather than coaching them towards the intended answer.
  5. Record the decision. Keep the chosen direction and its reasoning together. Identify whether the next step is another sketch, a prototype, research or technical clarification.

Avoid drawing the wrong thing

A polished sketch can still represent the wrong task. Review the assumptions behind the drawing and decide which need user research, a working prototype or technical input.

  • Presenting a single early sketch as the only possible direction.
  • Adding visual polish while leaving the task, content or interaction unclear.
  • Leaving controls and transitions unlabelled, so each viewer invents a different explanation.
  • Collecting comments without recording the problem or assumption behind them.
  • Treating a sketch as evidence that the interface will work with real users or production integrations.

Frequently asked questions

Do I need drawing skills for product design sketching?

Simple shapes and clear labels are enough for many product discussions. Focus on communicating the structure, sequence and question. The drawing needs to be understandable to the people reviewing it.

Should we sketch on paper or use a digital tool?

Choose the medium that suits the team and the discussion. Paper can be useful for quick shared exploration, while digital tools may help distributed collaboration. The purpose of the sketch matters more than a particular application.

How is a sketch different from a wireframe?

A sketch often explores a possibility quickly and informally. A wireframe usually provides a more deliberate view of information structure and page relationships. Agree on the purpose of the work rather than relying on the label alone.

When should a sketch become a prototype?

Move to a prototype when the question needs a more tangible interaction to examine. A sequence that depends on navigation or feedback may benefit from being tried. Keep clear which behaviours the prototype will demonstrate and which remain assumptions.

Can sketches reduce the need for testing?

Sketches can clarify ideas and expose questions early, but they do not replace review of the working experience. Use the sketch to decide what needs testing. Observe realistic tasks as the product becomes more tangible.

Conclusion

Sketch to make an idea easier to question. Keep the task clear, record feedback and take the unresolved decisions into prototyping. Our product development guide explains how that early work fits into a wider release.

Sources and further reading

All articles

Plan your next step.

Tell us which part of your website, app or product needs work. We’ll help you define an approach.

Discuss your project