Key Takeaways
Treat product design as business problem-solving, not screen decoration
Design is more than polish. Dashinsky argues that a designer's job includes understanding which product should be built, for whom, and how it creates value for users and the company. He describes a career progression from craft and visual execution, to product thinking, to influencing colleagues and decisions. At WeWork, he reviewed more than 100 portfolios and interviewed dozens of designers; a recurring weakness among unsuccessful candidates was focusing on appearance without explaining the business problem their design addressed.
Look beyond the interface. The book calls an industry fixation on visual presentation “Dribbblisation of Design.” Strong visual craft matters, but a beautiful screen cannot rescue a product that solves the wrong problem. A designer should connect user needs to business aims, such as retention, revenue, or access to a service.
The valuable shift is from judging design by its visible artifact to judging it by the decisions that artifact embodies. This aligns with service design, which examines the whole experience across products, staff, policies, and communications. It also gives design a credible place in strategic discussions. The risk is treating business metrics as proof of user benefit: a conversion increase can result from genuine clarity, or from manipulative pressure. The strongest product thinking explains both how an outcome helps the organization and why that outcome is good for the people using the product.
Before drawing, establish why, for whom, and under what conditions
Start with the problem. The book organizes product exercises around 5W1H, a question set that asks why a product is needed, who it serves, when and where it is used, what might be built, and how success will be measured. Dashinsky turns these questions into a working sequence: define the goal, select an audience, understand its context and needs, generate options, choose one, design it, and measure results.
Make uncertainty visible. Interview prompts rarely contain enough information for a perfect answer. Ask clarifying questions about the goal, audience, and expected deliverables. When information is missing, state a reasonable assumption and explain how it shapes the solution. A reservation-management product, for example, might assume that missed bookings are common enough to justify intervention. The point is not to pretend certainty, but to reason responsibly with limited evidence.
A sequence of questions reduces the temptation to treat the first plausible feature as the problem. It also helps an interviewer observe how a candidate thinks, rather than merely inspect a polished outcome. The method resembles a scientific hypothesis: identify what is known, distinguish it from what is assumed, and make the assumption testable. Its main limitation is that a tidy sequence can imply more certainty than a real project permits. In practice, evidence may send a team back to redefine the audience or goal, so the framework works best as a map, not a one-way checklist.
Name a real user's job before brainstorming features
Choose a meaningful audience. Products often serve several groups with different motivations. A healthcare scheduling system may be used by patients and clinic staff, while clinics are the paying customers. In an interview, focus on one major audience first, then describe the relevant differences within it, such as experience level, occupation, location, or mobility.
Put needs in context. Ask where the problem occurs, what triggers it, how much time people have, and what they may be feeling. A bicyclist using navigation in rain needs a different interaction from someone planning a route at home. User stories help connect a person's role, goal, and reason for acting. Mapping a current journey can also reveal pain points, such as ATM queues, forgotten PINs, or exposure to card fraud. These observations become opportunities to investigate, not automatic feature requests.
Context is often the difference between a feature that looks sensible in a meeting and one that works in the world. This connects to human factors research, where time pressure, physical surroundings, and attention limits affect performance. Segmentation can also prevent a product from treating every customer as an average user. Yet categories such as age or occupation are only starting hypotheses, not reliable substitutes for research. Designers should avoid turning demographic labels into assumptions about ability or preference, and should examine whether the proposed experience works for people at the edges of the target group.
Generate unlike solutions before choosing the easiest familiar interface
Explore more than one medium. After defining a need, propose several genuinely different ways to serve it. For bicycle navigation, possibilities include adapting a phone app, using a handlebar-mounted device, or sending directions through a smartwatch's tactile signals. This comparison helps expose tradeoffs that a quick redesign of the existing screen would miss.
Choose with explicit criteria. Dashinsky's Impact/Effort Matrix compares an idea's likely reach, customer value, and business contribution with the effort required to build it. A smartwatch feature may be elegant but reach few customers; a physical device may help riders but demand unfamiliar manufacturing work. Explain why an idea is worth pursuing and what it costs. The matrix supports a reasoned choice, but the chosen idea still needs enough complexity to demonstrate product and interaction design skill.
Generating unlike options is a practical defense against functional fixedness, the tendency to see an object only through its familiar use. It can reveal opportunities in hardware, service operations, or interaction modes that a screen-focused team overlooks. The matrix makes comparison legible, but its apparent precision can be misleading when reach, value, and effort are uncertain. A useful discussion should name confidence levels and unknowns, not just assign ideas to attractive quadrants. Reversibility matters too: an inexpensive experiment may be preferable to a high-impact concept that requires a large, irreversible investment.
Design the journey around tasks, not attractive isolated screens
Show how the experience unfolds. Dashinsky recommends storyboarding a user's sequence of actions and considering what happens immediately before and after using the product. In the bicycle-navigation example, arrival does not necessarily end the need: a rider may still want to know whether a destination is safe for locking a bike. Mapping the wider journey can expose such overlooked moments.
Translate journeys into work. A task list identifies what someone must be able to do, such as enter a destination, check the route, and recognize arrival. For quick ideation, the book's speedy-sketching exercise divides a page into four areas and gives the designer about a minute to sketch a distinct interface in each. The goal is variety, not finish. In a short exercise, concentrate on one or two important flows rather than drawing every screen.
A task-based view makes the design easier to assess: can a person complete the job, recover from an error, and understand what happens next? It also echoes journey mapping in service design, where the experience crosses channels and organizational boundaries. The before-and-after boundary is especially useful because customers rarely experience a product as an isolated screen. Still, task completion alone is not enough. Accessibility, privacy, emotional reassurance, and failure recovery can determine whether a technically successful flow is safe or usable, especially in settings such as healthcare or street navigation.
Measure user benefit and business outcomes together
Close the loop. A product proposal should say how success will be recognized. The book lists measures such as task success, completion time, engagement, retention, revenue, conversion, acquisition, and customer recommendations. The right measure depends on the goal. For a freelancer dashboard, useful signals might include whether people complete suggested next steps and whether they understand their finances and upcoming work.
Pair outcomes with safeguards. A family-doctor dashboard intended to shorten appointments should also track whether patient satisfaction holds steady or improves. That second measure helps reveal whether speed was achieved by reducing care quality. Dashinsky also recommends testing a promising idea before committing to a lengthy build, through an MVP or other experiment. Designers need not invent every target alone; they should show awareness of measurement and collaborate with product and data colleagues.
The paired measures capture an important principle from evaluation science: an intervention can improve one outcome while damaging another. A faster appointment is not a success if patients leave confused. Metrics also shape behavior, so a team should ask what people may optimize when a number becomes a target. Qualitative feedback and observed task performance can explain why a metric changed, while experiments can help distinguish a design effect from unrelated trends. A small test is valuable only when it answers a decision-relevant question, rather than producing activity that merely resembles validation.
Use the exercise to reveal thinking, not pretend certainty
Make the process observable. A design exercise tests more than the final interface. Interviewers can see whether a candidate asks useful questions, communicates decisions, handles feedback, and weighs advantages against limitations. If stuck, the candidate can explain the question being considered, make an assumption, or move to another step instead of going silent. The book advises confirming the expected format, fidelity, deadline, and presentation method before beginning.
Protect time for the design. For a one-hour exercise, Dashinsky suggests reserving about 30 minutes for solving the chosen flow, with shorter blocks for goal, audience, context, options, prioritization, measurement, and review. The exact allocation should shift when the prompt already supplies some answers. The presentation should make the logic behind the design visible, including the assumptions that deserve validation.
This framing makes an interview exercise closer to a collaborative work sample than a puzzle with a hidden answer. It rewards communication and adaptation, qualities that static portfolio images cannot show. There is, however, a measurement problem: performance under observation may reflect anxiety or unfamiliarity with whiteboarding as much as design ability. Clear expectations and a supportive interviewer improve both fairness and the quality of evidence. A strong process should judge the candidate's reasoning and response to new information, not their ability to perform confidence while drawing quickly.
Make design hiring relevant, humane, and fair
Test the work that matters. Hiring teams should decide which skills the role actually requires before choosing an exercise. A take-home task can reveal visual execution and deliverable quality; a live or on-site exercise can expose product reasoning and collaboration. If a role requires both, distinct exercises can test separate gaps, but the process should not become exhausting. Interviewers should explain logistics, offer a comfortable setting, and help candidates who get stuck rather than treating distress as evidence of incompetence.
Avoid disguised consulting. Dashinsky warns against asking candidates to solve a company's own product problems. Interviewers know far more about the context, may favor solutions that match their own views, and risk receiving unpaid work on a live problem. A fair exercise uses a relevant but separate challenge, and evaluates the thinking process rather than searching for one preferred answer.
The advice anticipates a core principle of personnel selection: an assessment is most defensible when it resembles the actual work and is scored against clear criteria. A polished take-home can be confounded by unequal free time, caregiving responsibilities, or access to collaborators, while a live exercise can over-weight performance under pressure. Combining methods can provide a fuller picture, but only if each has a distinct purpose. Ethical design hiring is not just candidate courtesy; it improves the validity of the signal and protects the employer from mistaking privilege or interview fluency for job competence.
Build influence by learning the business, then coach rather than control
Expand the designer's range. The leaders interviewed in the book emphasize business literacy, research, communication, and collaboration. Bobby Ghoshal urges designers to consider the full customer experience, including pricing, marketing, operations, and support. Helen Tran stresses checking whether a target market and its needs have been understood rather than accepting a brief's assumptions. Justin Maxwell highlights discipline, people skills, strategic thinking, and comfort with uncertainty.
Change how leadership works. Mia Blume describes the shift from solving every design problem personally to coaching teammates through questions and attentive listening. Joel Califa adds that candidates should research each employer, tailor their application, and build genuine professional relationships instead of applying indiscriminately. Together, these perspectives frame growth as more than mastering tools: it means helping teams make better decisions and enabling other people to do their best work.
These career perspectives describe influence as a learned practice, not a title. Research and business fluency help designers challenge weak premises; listening and coaching help those insights travel through a team without becoming top-down mandates. This resembles distributed leadership, where expertise is used to improve collective judgment rather than centralize every decision. The caution is that expanding scope can become an excuse to overload designers with responsibility but little authority. A healthy organization pairs broader expectations with access to evidence, decision-makers, and time for the research and collaboration the role demands.
Analysis
Dashinsky's most useful contribution is not a clever answer to any particular design prompt. It is a way to make judgment visible under pressure. The sequence moves from organizational purpose to audience, context, possible interventions, tradeoffs, interaction design, and evidence. That structure helps a candidate avoid the familiar trap of drawing a polished interface before establishing whether the underlying problem matters.
The book also treats design as a bridge between disciplines. Its examples require attention to business models, physical environments, user behavior, implementation effort, and measurement. A shampoo-refill kiosk is not only a screen: it has queues, bottles, payment, filling, and the environmental story after purchase. A healthcare tool is not only appointment booking: access, cost, clinical time, and patient confidence all interact. This systems view is more durable than any interface convention.
The framework is strongest as a scaffold for reasoning and communication, not as a recipe guaranteed to produce the right product. Its impact estimates often rely on assumptions, and matrices can make weak evidence look quantified. User needs and business outcomes can also conflict, so a proposal should explain whose interests a metric serves and what harms it might conceal. In actual product work, research, iteration, and organizational constraints make the process recursive rather than linear.
The interview guidance has a similar strength and limit. A work sample can reveal how candidates ask questions and respond to feedback, but a short exercise is only a proxy for sustained collaboration. The book's emphasis on clear expectations, appropriate tasks, and candidate comfort helps improve that proxy. Employers can make it stronger with consistent evaluation criteria, realistic time demands, and multiple forms of evidence. The enduring lesson is that good design judgment includes not only making an interface, but deciding what deserves to be made, for whom, at what cost, and how its effects will be known.
Review Summary
Solving Product Design Exercises receives overwhelmingly positive reviews, with readers praising its practical framework for tackling design challenges. Many find it invaluable for interview preparation and portfolio building. Designers at various experience levels appreciate the structured approach to problem-solving and the book's relevance to real-world scenarios. Several reviewers credit the book for helping them secure job offers. The exercises and examples are considered particularly useful, and the writing style is described as clear and concise.
People Also Read
Glossary
5W1H
Six problem-framing questionsA questioning method that examines why a product is needed, who it serves, when and where it is used, what could be built, and how success could be measured. Dashinsky uses these questions to organize a product-design exercise, while adding a separate step for solving the selected design direction.
Design Exercise Canvas
A worksheet for product exercisesA printable worksheet that guides a designer through the book's exercise process. It provides prompts for the goal, audience, user context and needs, possible ideas, prioritization, design solution, and measures of success. Its purpose is to help candidates remember the sequence while working through or presenting a challenge.
Impact/Effort Matrix
A tool for comparing optionsA prioritization tool that compares the anticipated impact of product ideas with the effort required to implement them. In the book, impact combines potential reach, customer value, and business contribution. The matrix helps a designer explain why one direction is preferable, while acknowledging that estimates are judgments rather than precise forecasts.
User stories
Needs expressed from a user's viewA way to describe a product need in ordinary language by connecting a user's role to a goal and the benefit behind it. The book presents a template that identifies who is acting, what they want to accomplish, and why it matters. This makes the motivation and context behind a feature easier to discuss.
Dribbblisation of Design
Overemphasis on visual polishDashinsky's label for a design culture that prizes how interfaces look more than whether products work well or create meaningful results. The term refers to the influence of visually focused portfolio and design-sharing communities. The book does not reject craft; it argues that visual execution alone is too narrow a definition of product design.
Customer experience designer
Designer of the whole customer journeyA broader view of a designer's role, discussed in the book's interview with Bobby Ghoshal. It considers how people encounter a company before, during, and after using its product, including influences such as pricing, marketing, operations, and customer support. The concept extends design attention beyond the interface without claiming those other functions belong exclusively to designers.
FAQ
What's "Solving Product Design Exercises: Questions & Answers" about?
- Purpose of the book: The book by Artiom Dashinsky is designed to help designers prepare for product design exercises, which are often part of job interviews in tech companies.
- Focus on skills gap: It addresses the skills gap in design education, particularly in understanding how design impacts business and solving business problems.
- Framework and exercises: The book provides a structured framework for solving design exercises and includes practical examples and exercises to practice.
Why should I read "Solving Product Design Exercises: Questions & Answers"?
- Interview preparation: It is particularly useful for those preparing for product design, UX, and UI/UX design interviews.
- Skill development: The book helps in developing product thinking and understanding the role of design in business contexts.
- Career advancement: It offers insights for entry-level to senior designers on how to progress in their careers and improve their portfolios.
What are the key takeaways of "Solving Product Design Exercises: Questions & Answers"?
- Design beyond aesthetics: Successful designers understand the business impact of design, not just its visual aspects.
- Structured approach: The book emphasizes a structured approach to solving design exercises, focusing on understanding goals, audience, and context.
- Practical exercises: It includes real-world exercises and solutions to help designers practice and improve their skills.
What is a design exercise according to Artiom Dashinsky?
- Definition: A design exercise is a challenge given to candidates during interviews to solve a product design problem and explain their decisions.
- Types: There are live whiteboarding, on-site, and take-home exercises, each testing different skills.
- Purpose: These exercises evaluate a designer's problem-solving process, product thinking, and ability to communicate their ideas.
How does Artiom Dashinsky suggest solving a product design exercise?
- Framework: Dashinsky provides a seven-step framework: Understand your goal, Define the audience, Understand the context and needs, List ideas, Prioritize and choose an idea, Solve, and Measure success.
- Process over solution: Emphasizes following a process rather than jumping straight to a solution to ensure a comprehensive understanding of the problem.
- Critical thinking: Encourages asking questions, making assumptions, and being critical about solutions to demonstrate thoroughness.
What is the "5W1H" technique mentioned in the book?
- Information gathering: The 5W1H technique involves answering six questions: Why, Who, When, Where, What, and How.
- Application in design: It is used to structure the approach to solving design exercises, ensuring all aspects of the problem are considered.
- Adaptability: While based on journalism and research methods, it is adapted for product design to help designers think holistically.
What are some common design exercises included in the book?
- Examples: Designing a kiosk interface, a self-publishing platform for Amazon, a dashboard for freelancers, and improving the ATM experience.
- Variety of challenges: Exercises cover different aspects of design, from interface design to solving business problems.
- Practice opportunities: These exercises provide opportunities for designers to practice and refine their skills in a structured manner.
How does the book address the "Dribbblisation of Design"?
- Visual obsession: The book critiques the focus on visual aesthetics over functionality, a trend exacerbated by platforms like Dribbble.
- Business impact: Emphasizes the importance of understanding how design can solve business problems and not just create appealing visuals.
- Skill development: Encourages designers to develop skills beyond aesthetics, such as product thinking and business strategy.
What advice does Artiom Dashinsky give for presenting a design solution?
- Comprehensive presentation: Include all steps of the framework in the presentation to demonstrate the thought process.
- Clarity and confidence: Be clear about the "why" behind design decisions and be prepared to discuss pros and cons.
- Engagement: Use storytelling and visual aids to engage the audience and clearly communicate the solution.
What are some key interviews included in the book?
- Industry insights: Interviews with design leaders like Bobby Ghoshal, Justin Maxwell, and Helen Tran provide insights into the design industry.
- Career advice: Topics include the importance of business awareness, skills for aspiring founders, and overlooked skills in design.
- Practical tips: Interviews offer practical advice for designers looking to advance their careers or transition into leadership roles.
What are the best quotes from "Solving Product Design Exercises: Questions & Answers" and what do they mean?
- Design's business role: "Design isn’t just about beauty; it’s about market relevance and meaningful results." This highlights the importance of design in achieving business goals.
- Product thinking: "Strong product thinking means that you understand what a good outcome is and how to design an experience that would lead to those good outcomes." Emphasizes the need for designers to think beyond visuals.
- Process importance: "The single most important thing you should remember while solving exercises is to follow a process." Stresses the value of a structured approach in design.
How can "Solving Product Design Exercises: Questions & Answers" help business leaders?
- Hiring insights: Provides guidance on how to interview and evaluate design candidates effectively.
- Understanding design's value: Helps business leaders understand the mindset of successful designers and the role of design in achieving business objectives.
- Defining roles: Offers insights into defining the design role within an organization to maximize its impact.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.