Solving Product Design Exercises

Contents

• Part 01 · Foundations
  01Why Product Design Exercises Matter
  02The 7-Step Framework
• Part 02 · Worked Exercises
  03Worked Exercises
• Part 03 · Meta & Career
  04How to Use a Design Exercise When Interviewing
  05Tasks List
  06Interviews with Design Leaders

Why Product Design Exercises Matter

Resumes and portfolios show what you've shipped, but design exercises reveal how you actually think. Companies use them because ambiguous problems under time pressure expose product sense, communication, and collaboration faster than any other interview format.

Process Over Pixels

Interviewers care far more about how you reason through a problem than the polish of your final sketch. Verbalizing trade-offs beats producing a pretty wireframe in silence — your thought process is the artifact being graded, not the drawing.

Ambiguity Is the Point

Exercises are intentionally vague ("Design an alarm clock for the blind") so the interviewer can watch you scope, clarify, and structure an open-ended problem. Trying to eliminate the ambiguity by guessing what the interviewer "wants" misses the test entirely.

Product Sense vs. Craft

Hiring distinguishes between visual/interaction craft (pixels, typography, prototyping) and product sense (business awareness, user empathy, prioritization). Exercises are built specifically to stress-test product sense, which portfolios alone can't prove.

The Interview as a Conversation

A design exercise is a collaborative dialogue, not a monologue or a test. Treating the interviewer as a teammate — checking in, asking for input, accepting hints — produces stronger signal and surfaces information that improves your answer.

Generalist Mindset

Product design exercises reward T-shaped thinkers who can move between user research, business strategy, UX flows, and metrics. Pure specialists struggle because the exercise spans the whole product lifecycle in 45 minutes.

Practice Compounds

Like coding interviews, exercise performance improves dramatically with deliberate practice. Reading the framework once is worthless; running it on 10+ exercises is what makes it automatic during a real interview.

Design exercise

An open-ended product or design problem posed in an interview, typically completed in 30-60 minutes live or as a take-home, used to evaluate thinking process.

Whiteboard interview

A live, in-person or virtual session where the candidate sketches and talks through a design problem on a whiteboard or shared canvas in real time.

Take-home exercise

A longer-form design challenge completed independently over hours or days, often presented back to the team afterward.

Product sense

The intuition for what to build and why, combining user empathy, business judgment, and market awareness — the core trait exercises try to surface.

Portfolio review

The companion interview format where past work is presented; exercises complement portfolios by testing thinking on a fresh, unfamiliar problem.

Signal

Interview shorthand for evidence of a specific skill or trait; exercises are designed to generate high-signal observations quickly.

Hiring loop

The end-to-end interview sequence at a company, of which the design exercise is usually one critical stage.

T-shaped designer

A practitioner with broad cross-disciplinary skills plus deep expertise in one area; the profile exercises reward.

Multiple choice

A candidate produces a beautifully detailed wireframe in near silence, handing it over at the end with a polished flourish. Why is this likely to score poorly?

• AThe wireframe should have been a high-fidelity mockup instead of a sketch.
• BInterviewers grade the visible thought process, not the final artifact's polish.
• CThe candidate didn't spend enough time on visual hierarchy.
• DWireframes are the wrong deliverable for any design exercise.

True / False

The best move when a prompt feels vague (e.g., "Design an alarm clock for the blind") is to silently pick the interpretation you think the interviewer wants and start sketching.

• TrueTrue
• FalseFalse

Multiple choice

A strong portfolio already demonstrates typography, prototyping, and visual hierarchy. What is the design exercise primarily there to stress-test that the portfolio cannot?

• AProduct sense — business awareness, user empathy, and prioritization on an unfamiliar problem.
• BTool fluency in Figma or Sketch.
• CThe candidate's ability to produce pixel-perfect mockups under time pressure.
• DFamiliarity with the interviewer's own product.

Spot the issue

A candidate decides the interviewer is "the judge," refuses every offered hint, and avoids checking in because they think asking for input looks weak. What's the main problem?

• AThey should have asked for a high-fidelity Figma file instead of using the whiteboard.
• BThey should have spent more time on visual polish to compensate.
• CThey're treating the exercise as a monologue when it's meant to be a collaborative dialogue, costing them signal.
• DThey should have specialized into one area rather than ranging across the whole problem.

The 7-Step Framework

The spine of the book. Dashinsky introduces a journalistic 5W1H structure (Why, Who, When/Where, What, How) expanded into seven concrete steps that take a candidate from problem framing all the way through to success metrics. The framework must be internalized so deeply that under interview pressure it becomes the default structure to fall back on.

5W1H Foundation

The framework is built on the journalistic 5W1H questions — Why, Who, When/Where, What, How. Each maps to a step in the canvas, ensuring the answer covers business motivation, audience, context, ideation, and measurement rather than jumping straight to UI.

Step 1 — Why (The Goal)

Frame the business problem behind the prompt before sketching anything. Ask: what opportunity, pain, or stakeholder objective triggers this exercise? Restating the goal in business terms shows business awareness and prevents solving the wrong problem.

Step 2 — Who (Pick One User)

List several plausible user segments, then explicitly pick one to focus on. Designing for "everyone" is the most common failure mode and a red flag for interviewers; committing to one well-defined persona shows discipline and lets you go deeper.

Step 3 — When/Where (Context & Needs)

Map the environment, triggers, and emotional state of the chosen user. Context — subway commute, kitchen counter, hospital lobby — constrains the solution space far more than abstract demographics do, and surfaces real pain points.

Step 4 — What (Generate Multiple Ideas)

Brainstorm 3–4 distinct solution directions before committing to one. Showing breadth signals creativity; presenting only one idea reads as a tunnel-vision designer who hasn't considered alternatives.

Step 5 — Prioritize and Choose

Use an Impact vs. Effort matrix (or a similar 2x2 like Value/Feasibility) to pick the single idea you'll deep-dive. Articulate the trade-off out loud — "I'm picking B because it has higher impact for similar effort" — to score points on rationale.

Step 6 — Solve (Sketch the Chosen Direction)

Sketch wireframes, user flows, or storyboards for the chosen idea. Low fidelity is preferred in whiteboards — clarity over polish — and one well-explained flow beats five half-drawn screens.

Step 7 — How (Measure Success)

Close by defining KPIs that map back to the Why from Step 1. Skipping metrics is one of the most common failure modes; tying the design to measurable outcomes proves business literacy and closes the loop cleanly.

5W1H

Why/Who/When/Where/What/How — the journalistic framework underpinning the Design Exercise Canvas.

Design Exercise Canvas

Dashinsky's named one-page artifact laying out all 7 steps; included as a printable in the book's appendix.

Impact vs. Effort matrix

A 2x2 prioritization tool plotting expected user/business impact against implementation cost.

Persona

A representative user archetype with goals, behaviors, and pain points used to focus design decisions on a specific human.

Pain point

A specific frustration, friction, or unmet need a user experiences — the raw material from which design opportunities are extracted.

Jobs to Be Done (JTBD)

Framework for describing what users are "hiring" a product to accomplish, focusing on the underlying job rather than features.

MVP

Minimum Viable Product — the smallest version of a solution that delivers core value and can be validated; useful for scoping answers to the available time.

KPI

Key Performance Indicator — a specific, measurable metric tied to a goal, such as DAU, conversion rate, or task success rate.

North Star Metric

The single metric that best captures the core value a product delivers (e.g., nights booked for Airbnb); a strong closing move in an exercise.

Multiple choice

What does the 5W1H acronym at the foundation of the framework stand for?

• AWhy, Who, When, Where, What, How.
• BWhy, What, When, Where, Whether, How.
• CWho, What, Why, Whom, Where, How.
• DWhen, Where, Why, Who, Which, How.

Spot the issue

Asked to "design a budgeting tool," a candidate says "users want budgeting tools because everyone struggles with money" and immediately sketches a dashboard. What's the main problem?

• AThey skipped low-fidelity sketches and went straight to a dashboard.
• BThey never restated the business problem in concrete terms, so downstream design decisions aren't anchored to any opportunity or stakeholder objective.
• CThey should have brainstormed visual styles before drawing.
• DDashboards are the wrong artifact for a budgeting tool.

Multiple choice

A candidate lists three plausible user segments — busy parents, college students, and small-business owners — and then says "my solution will work for all of them." Why is this a red flag for interviewers?

• AListing three segments is too many; only one should be named at all.
• BRefusing to commit to one user is the most common failure mode; designing for "everyone" prevents going deep and signals lack of discipline.
• CSmall-business owners aren't a valid persona in a consumer exercise.
• DThe candidate should have skipped Step 2 entirely and gone straight to ideation.

Multiple choice

After narrowing the user and exploring context, a candidate presents a single solution idea and starts detailing it. What does the framework expect instead?

• ASkip directly to KPIs before any ideation.
• BPresent a fully prototyped hi-fi mockup of that one idea.
• CPick the user's favorite color palette before solving.
• DGenerate 3–4 distinct directions, then use a prioritization tool like Impact vs. Effort to choose one and articulate the trade-off out loud.

True / False

Skipping the success-metrics step at the end of an exercise is fine if you've already produced a strong sketch, because the visual answers the "how would we know it worked" question implicitly.

• TrueTrue
• FalseFalse

Worked Exercises

The longest section of the book. Dashinsky walks through five complete worked exercises end-to-end, each demonstrating the 7-step framework on a different exercise type — hardware kiosk, new product, business dashboard, social-good redesign, and critique-and-redesign. The chapter is the book's "show, don't tell" — the framework only sticks once you watch it applied across very different domains.

Hardware Exercise — The Soap Refill Kiosk

A kiosk for refilling liquid soap and shampoo tests handling physical context — queue dynamics, hygiene, shoppers holding bags, dwell time. The lesson: Step 2 (Who) and Step 3 (Where) carry more weight than visual UI for public terminals, and sustainability is named as the explicit business Why driving every downstream choice.

New-Product Exercise — Amazon Self-Publishing

The prompt asks how to lower the barrier for first-time authors self-publishing on Amazon. The key move is narrowing the user — hobbyists vs. mid-list pros vs. academics — and picking one. Demonstrates MVP scoping: instead of redesigning the platform, build one guided formatting wizard that gets the chosen segment to first activation.

Improve-an-Existing-Product Exercise — Freelancer Business Dashboard

A B2B prompt: design a dashboard that helps a freelancer run their business. Closest to the classic "How would you improve X?" interview format. Demonstrates information architecture (ranking dashboard cards by frequency-of-need), HMW statements, Impact/Effort prioritization of widgets, and connecting design to business KPIs like time-saved-per-week and retention.

Social-Good Exercise — Primary Healthcare Access

A high-ambiguity prompt about improving access to primary care. Forces an early definition of "access" (cost? distance? wait times? language?) because the answer determines everything downstream. Introduces service blueprint thinking — the solution spans an app, a phone line, and a clinic visit — and outcome metrics (visits completed, conditions caught early) over screen-level analytics.

Critique & Redesign Exercise — Improve the ATM

The classic "critique an existing flow and redesign it" exercise. The right answer is usually subtraction, not addition: walk the existing flow heuristically, inventory every micro-moment of friction, then optimize the happy path (withdrawing cash) and push everything else to a secondary menu. Edge cases (visually impaired users, foreign cards, queues) are named explicitly to score depth points.

Time-Boxing the Framework

A common thread across all five exercises is explicit time allocation per step. Announce the budget up front ("I'll spend 5 minutes clarifying, 10 ideating, 15 detailing, 5 on metrics") so the interviewer sees the structure and so you finish the full arc instead of running out of time mid-ideation.

Trade-offs as Seniority Signal

In every worked exercise, Dashinsky surfaces explicit trade-offs: density vs. clarity on the dashboard, opinionated defaults vs. customization, depth-of-feature vs. time-in-interview. Naming what you're cutting and why is one of the strongest seniority signals in the book.

Closing with KPIs

Every worked exercise ends with measurable success metrics: completion rate and NPS for the kiosk, activation rate for self-publishing, DAU/MAU and churn for the dashboard, outcome metrics for healthcare, transaction time and error rate for the ATM. Skipping metrics is the most common failure mode — every exercise should close by tying the design back to the Why.

HMW (How Might We)

IDEO-popularized phrasing that converts a pain point into a generative design question — e.g., "HMW reduce time between project end and payment?"

Information Architecture (IA)

How content is organized, labeled, and hierarchically prioritized within a product.

Service blueprint

An extended journey map that includes back-stage actors and systems, not just user-facing screens.

Touchpoint

Any moment a user interacts with the product — signage, screen, dispenser, payment terminal.

Throughput

Number of users served per unit time; critical for queued public terminals like ATMs and kiosks.

Happy path

The dominant successful flow most users follow; should be the most optimized in any redesign.

Friction

Any element that slows or discourages task completion; the primary thing to remove in critique-and-redesign exercises.

DAU/MAU

Daily/Monthly Active Users; the ratio is a common product "stickiness" signal.

Activation

The moment a new user reaches first value (e.g., publishing their first book on Amazon).

NPS

Net Promoter Score — a would-recommend metric used as a satisfaction KPI.

Multiple choice

In Dashinsky's soap-refill kiosk walkthrough, which two of the 7 steps carry the most weight relative to a typical mobile-app exercise?

• AStep 2 (Who) and Step 3 (When/Where)
• BStep 4 (What) and Step 5 (Prioritize)
• CStep 1 (Why) and Step 7 (How)
• DStep 6 (Solve) and Step 7 (How)

Spot the issue

A candidate tackling the Amazon self-publishing prompt says: "I'd build a single great experience that works equally well for hobbyists, academic authors, and mid-list professionals — and ship a redesigned end-to-end platform." What is the main problem with this approach?

• ASelf-publishing is not a real business problem for Amazon.
• BThey failed to narrow to one user segment and scope to an MVP that drives first activation.
• CThey didn't sketch enough screens before talking.
• DThey picked the wrong prioritization framework.

Multiple choice

In the freelancer business dashboard exercise, what does Dashinsky use to rank which dashboard cards earn the most prominent slots?

• AVisual hierarchy rules from typography
• BCost of each card to engineer
• CThe freelancer's frequency-of-need for each piece of information
• DAlphabetical ordering of widget names

Spot the issue

A candidate opens the primary-healthcare-access prompt by immediately sketching an appointment-booking app screen, without pausing to define what "access" means in this prompt. What's the main problem?

• AThey picked a mobile app before considering the phone-line and clinic-visit channels in the service blueprint.
• BThey should have opened with outcome metrics like visits completed before any sketching.
• CThey should have picked one user segment (e.g., rural elderly) before clarifying "access."
• D"Access" is ambiguous (cost, distance, wait time, language) and the chosen definition determines the entire solution — they jumped to UI before framing.

Spot the issue

A candidate ends a strong ATM critique-and-redesign by adding a loyalty-points screen, a chat-with-banker button, and a new promo carousel to the main flow. What's wrong?

• AThey forgot to mention edge cases like foreign cards.
• BThe redesign should subtract friction from the happy path (withdrawing cash), not add features to it.
• CThe new screens should have lived on the happy path instead of a secondary menu.
• DThey should have started with KPIs first.

How to Use a Design Exercise When Interviewing

This chapter flips perspective from candidate to hiring manager, but it does double duty — by revealing exactly how interviewers design exercises and what they grade, it tells candidates what's actually being scored. Dashinsky argues good exercises target the candidate's weakest known skill and optimize for observing thinking process, not a polished artifact.

Identify the Skill Gap First

Before picking an exercise, decide which competency the portfolio did NOT prove — visual craft, product thinking, communication, or collaboration — and test for that specific gap. Generic exercises waste the slot.

Match Format to Skill

Take-home assignments evaluate visual/UI craft and production-ready output; whiteboard exercises expose product thinking, communication, and collaboration under pressure. Using the wrong format for the skill you care about produces noisy signal.

Don't Use Your Own Product

Avoid using your own product as the exercise. Candidates have unfair familiarity (or its opposite), and you bring strong personal opinions — both bias the result and make the exercise about your roadmap rather than the candidate.

Make the Candidate Comfortable

Stress suppresses the very thinking you're trying to evaluate. Introduce yourself, explain ground rules, and signal that thinking out loud is welcomed. A nervous candidate gives a worse answer than the same candidate at ease.

The Constructive-Criticism Probe

Drop one piece of constructive criticism mid-exercise to see how the candidate responds to pushback. How they receive, integrate, or defend their thinking predicts how they'll behave in design critiques on the job.

Help Them When Stuck

Don't watch them drown. The point is to observe how they think, not whether they can solve a novel problem unaided. Offering a nudge is information about how they integrate input, not cheating.

Evaluate Process, Not Output

Grade on: framing the problem, asking sharp clarifying questions, considering multiple users and solutions, articulating trade-offs, tying decisions back to goals, and proposing success metrics. Pixel polish is the weakest signal.

Calibrate to Role Level

Junior designers should show craft and structure; senior designers should show strategic framing, business literacy, and trade-off reasoning. The same exercise can be graded against very different bars depending on the level being hired.

Take-home exercise

A multi-day assignment (typically 4–8 hours of work) used to assess visual/UI quality and end-to-end deliverables.

Whiteboard challenge

A 15–40 minute live problem-solving session, optimized for showing thought process.

On-site exercise

A roughly one-hour in-person task with paper and pen, followed by a presentation at the whiteboard.

Skill gap

The competency missing from a candidate's portfolio that the exercise is specifically designed to surface.

Constructive criticism probe

A deliberately introduced critique used to test how a candidate receives or pushes back on feedback.

Fidelity

The level of polish — low-fi sketch → mid-fi wireframe → hi-fi mockup → prototype.

Scope creep

Letting a take-home balloon beyond the prompt; a common failure mode candidates are warned against.

Calibration

Aligning interviewers on what "good" looks like at each level so grading is consistent across candidates.

Multiple choice

You are designing a take-home for a senior candidate whose portfolio is loaded with polished hi-fi mockups but says little about strategy or trade-offs. According to Dashinsky, what kind of exercise should you give them?

• AAnother take-home, since take-homes are the gold standard regardless of the gap.
• BA whiteboard exercise targeted at product thinking, communication, and trade-off reasoning.
• CA redesign of your own product so you can compare to your team's solution.
• DThe same generic exercise every candidate gets, to keep grading consistent.

True / False

Using your own product as the design exercise is recommended because the interviewer already knows the problem space deeply and can give the candidate accurate feedback.

• TrueTrue
• FalseFalse

Spot the issue

Mid-exercise, the candidate gets visibly stuck and stops talking. The interviewer sits silently to "see if they can work it out alone," and the candidate runs out of time before reaching success metrics. What's the main interviewer mistake?

• AThey should have ended the exercise immediately when the candidate paused.
• BThey should have switched to a different exercise on the fly.
• CThey failed to nudge — the goal is to observe how the candidate integrates input, not whether they can solve a novel problem unaided.
• DThey should have graded primarily on the final sketch quality.

Multiple choice

A junior and a senior candidate complete the same whiteboard prompt. Per Dashinsky's calibration guidance, what should the bar shift toward for the senior?

• AStrategic framing, business literacy, and explicit trade-off reasoning.
• BCleaner sketches and tighter wireframes than the junior produced.
• CMemorized knowledge of the company's existing roadmap.
• DStrict adherence to the 7-step framework's wording.

Tasks List

A deliberate practice catalog — 30+ design prompts spanning B2C, B2B, hardware, accessibility, civic, and mobile problems. The chapter exists to remove the "what should I practice?" excuse and to force the reader to run the framework across enough varied domains that it becomes automatic.

Practice Is the Entire Point

Reading the framework once is worthless; running it on 10+ exercises is what makes it automatic during a real interview. The book is a workbook, not a textbook — Chapter 5 is the homework.

Vary the Domain Deliberately

The prompts span B2C, B2B, hardware, accessibility, civic, mobile, and physical-product problems specifically to prevent pattern-matching to one type. If you only practice mobile apps, you'll freeze when handed a kiosk prompt.

Time-Box Your Practice

Run each prompt under realistic limits — 30, 45, or 60 minutes — so you internalize what fits in the available time. Practicing without a clock teaches you nothing about interview performance.

Mock Interviews

Practicing alone hides communication weaknesses. Mock interviews with a peer or mentor playing the interviewer role surface them — narration habits, response to pushback, time management — which are exactly the things being graded.

The Design Exercise Canvas

The book ships with a one-page printable that scaffolds the 7 steps — Why, Who, When/Where, What, How. Use it during practice so the structure becomes second nature; don't expect to invent it on the fly under pressure.

Build a Case-Study Library

Each completed exercise becomes a portfolio artifact and a story you can pull from in behavioral interviews. Don't throw away your practice work — write it up as a case study and use it later.

Re-solve for Different Audiences

Solving the same prompt for two distinct user segments — e.g., Spotify for commuters vs. Spotify for parents — forces deeper Who/Why work and shows you how dramatically the right answer shifts when the user changes.

Iterate on Your Weakest Step

After each practice session, note where you got stuck. Most candidates plateau on framing (Step 1) or success metrics (Step 7). Target that specific step in the next run instead of just doing more reps generically.

Deliberate practice

Targeted, feedback-driven repetition aimed at weaknesses rather than generic "doing more work."

Time-box

A fixed duration assigned to a task or sub-step to force prioritization and finishing.

Mock interview

A simulated interview run with a peer or mentor playing the interviewer role to expose communication gaps.

Prompt

The one-line problem statement that opens a design exercise — e.g., "Design an app for X user doing Y."

Case study

A written or visual artifact documenting how you solved a problem; the output of a practice exercise turned into portfolio material.

Scope

The boundaries of the problem being solved (platform, user segment, geography, feature surface); strong candidates set scope deliberately.

Reps

Slang for repeated practice runs; the unit of progress in deliberate practice.

Multiple choice

A reader finishes the 7-step framework chapter, highlights it carefully, re-reads it twice, and skips Chapter 5 entirely because "they already understand it." Why does Dashinsky argue this approach fails?

• AThe framework only works after watching mock interviews of others using it.
• BThe framework changes meaningfully between chapters, so Chapter 5 contains updates.
• CWithout running the framework on 10+ varied prompts, it won't be automatic under interview pressure.
• DRe-reading is fine; Chapter 5 is mostly optional appendix material.

Spot the issue

A designer preparing for interviews picks ten practice prompts, all of which are consumer mobile apps because that's their comfort zone, and runs each one to completion. What's the main problem with this practice plan?

• ATen prompts is far too few to see any improvement at all.
• BMobile prompts are too easy and won't build any real skill.
• CBy staying inside one domain they'll pattern-match instead of internalizing the framework, and will freeze on a hardware or B2B prompt.
• DThey should have started with the Design Exercise Canvas before picking any prompts.

True / False

Practicing prompts without a timer is fine as long as you eventually complete them, because the framework's quality matters more than the clock.

• TrueTrue
• FalseFalse

Multiple choice

After six solo practice runs, a candidate notices their answers feel solid on paper but they bombed two real interviews on narration and handling pushback. What does the chapter recommend as the highest-leverage next step?

• ADoing six more solo reps but with stricter time-boxing.
• BRunning mock interviews with a peer or mentor playing the interviewer role.
• CSwitching to take-home format because whiteboards don't suit them.
• DMemorizing the Design Exercise Canvas labels verbatim.

Multiple choice

A candidate has completed 12 practice exercises but throws away each sketch the moment they finish. What opportunity are they missing?

• AThey should be using those exercises to memorize the 5W1H acronym faster.
• BEach completed exercise can be written up as a case study and reused as portfolio material and behavioral-interview stories.
• CThey should be re-solving each prompt at higher fidelity instead of starting new ones.
• DPractice work needs to be destroyed so they don't accidentally reuse it in a real interview.

Interviews with Design Leaders

Five conversations with senior practitioners — Bobby Ghoshal, Justin Maxwell, Helen Tran, Joel Califa, and Mia Blume — each tackling a different career stage from junior IC to founder to manager. Together they argue that craft alone caps your ceiling; business literacy, communication, and treating your career like a product are what unlock senior roles.

Customer Experience Designer

Bobby Ghoshal argues designers should evolve from "UX designer" to "customer experience designer" by learning marketing, finance, and operations. The scope expands from screens to the whole customer journey, which is where senior influence actually happens.

Validate Assumptions Through Research

Helen Tran identifies rigorous user research as the most overlooked skill. Bridging business needs and user needs requires validating that the user and problem actually exist before you draw anything — most failed products skip this step.

Treat Job Hunting as a Design Process

Joel Califa frames the job search itself as a design exercise: you are the product. Research target companies and hiring managers the way you'd research users, build authentic networks instead of cold-applying, and apply Why/Who/What/How to your career.

Founder-Designers Need People Skills

Justin Maxwell emphasizes that negotiation, storytelling, and prioritizing outcomes over aesthetic preferences matter more than tool mastery for designer-founders. Discipline and communication beat craft when you're trying to build a company.

Managing Means Letting Go of the Pen

Mia Blume's central point on design management: great managers ask questions and coach instead of redesigning their reports' work. The hardest transition from IC to manager is resisting the urge to grab the pen.

Business Literacy Unlocks Senior Roles

Across all five interviews, the common thread is connecting design decisions to revenue, retention, and strategy. Pure craft caps you at mid-level; business fluency is the senior-level unlock — and is exactly what design exercises are built to detect.

Networks Beat Applications

Multiple leaders emphasize relationships over portfolio-spam. Being known for something specific, and maintaining relationships with target-company designers, outperforms cold-applying to dozens of openings.

Career as a Product

The book closes by extending the 7-step framework from the exercise to the career itself. Define your Why (what motivates you), pick your Who (companies/managers worth working for), study the context, prioritize, and measure. Apply the framework to yourself.

Customer experience designer

Ghoshal's term for a designer whose scope spans the whole customer lifecycle, not only the product UI.

Business literacy

Working fluency in revenue, growth, unit economics, and operations sufficient to argue trade-offs with PMs and execs.

Validating assumptions

The research practice of checking that the user and need you're designing for actually exist before building.

Design critique

A structured peer review of in-progress design work, used both in interviews and on the job.

Coaching

A management posture of asking questions to develop the designer rather than rewriting their work.

Networking with intent

Building relationships with specific people at target companies as part of a deliberate job search.

IC track

Individual Contributor career path that deepens craft without taking on people management.

Career ceiling

The level at which purely visual/craft skill stops producing promotions; broken only by business and communication skills.

Multiple choice

Bobby Ghoshal argues designers should reframe themselves from "UX designer" to "customer experience designer." What concrete shift does this rebrand demand?

• ALearning marketing, finance, and operations so the scope expands from screens to the full customer journey.
• BSpecializing harder on interaction design and motion to differentiate at the senior level.
• CMoving from product design into pure brand and marketing design.
• DSwitching from B2C to B2B work, where customer journeys are simpler.

Spot the issue

A PM hands a designer a problem statement and a target user persona. The designer immediately opens Figma and starts wireframing, reasoning that the persona was already provided so the user is "validated." Per Helen Tran, what's the main miss?

• AThey should have started with high-fidelity mockups, not wireframes, to save time later.
• BA provided persona is not validation — Tran says rigorous research must confirm the user and the problem actually exist before drawing anything.
• CThey should have negotiated a longer timeline before starting any design work.
• DThe PM, not the designer, should be doing the wireframing.

True / False

According to Justin Maxwell, designer-founders succeed primarily because their craft and tool mastery let them out-produce competitors who can't design.

• TrueTrue
• FalseFalse

Multiple choice

A new design manager keeps grabbing the pen during reviews to "show" their report the right move, and reworks the report's screens between meetings. Per Mia Blume, what's the core management failure here?

• AThe manager isn't reworking enough — managers should produce the final design themselves.
• BThe manager should escalate underperforming reports to HR rather than coach them.
• CGreat managers ask questions and coach to develop the designer, instead of redesigning their reports' work.
• DThe manager should be doing more pair-design sessions and fewer async reviews.

Multiple choice

A senior IC keeps getting passed over for promotion despite stronger visual craft than peers who are advancing. What does the cross-interview thesis of Chapter 6 predict is the real blocker?

• AThey aren't producing enough Dribbble shots to be visible internally.
• BTheir portfolio probably needs a redesign in a more current visual style.
• CThey should switch from product design to design management to advance.
• DThey likely lack business literacy — connecting design decisions to revenue, retention, and strategy — which is the senior-level unlock.