Product Design Case Mix
You will be assigned one of three product design scenarios. For the assigned scenario, outline the product vision, target users, key journeys, MVP features, technical approach, success metrics, risks, and rollout plan.
Constraints & Assumptions
-
Clarify which scenario you are answering before starting.
-
State assumptions and keep the MVP coherent rather than trying to solve every future case.
-
Include enough technical architecture to show feasibility, but keep the answer product-led.
-
Include metrics and risks specific to the chosen scenario.
Clarifying Questions to Ask
-
Which scenario should I answer: cross-border books, delivery ETA, or next-generation washer?
-
What company assets, geographies, launch timeline, and team size should I assume?
-
Should the answer emphasize customer experience, technical systems, operations, or go-to-market?
-
Are there regulatory, compliance, or hardware constraints I should treat as fixed?
Part 1 - Cross-Border Commerce: U.S. Books to Korean Customers
Design how to sell and deliver physical U.S. books to customers in Korea.
What This Part Should Cover
-
Target customers, localized discovery, landed cost, Korean address and payment flows, customs, shipping, returns, support, and tracking.
-
Workstreams across product, catalog, tax, compliance, logistics, payments, fraud, support, analytics, and marketing.
-
Metrics such as conversion, delivery-promise accuracy, CSAT, WISMO contacts, margin, refunds, and repeat purchase.
Part 2 - Customer ETA Experience
Design an end-to-end web experience that shows accurate delivery estimates across the shopping journey.
What This Part Should Cover
-
ETA surfaces on PDP, cart, checkout, order details, notifications, and support tools.
-
Backend dependencies such as inventory, fulfillment, carrier, weather, cutoff times, geolocation, promise engine, and tracking events.
-
Latency, confidence ranges, unexpected events, proactive updates, and promise accuracy metrics.
Part 3 - Next-Generation Washer
Design a next-generation washing machine.
What This Part Should Cover
-
Target segments, core user needs, product differentiation, hardware and software features, and service or consumables opportunities.
-
Go-to-market strategy including positioning, pricing, channels, launch plan, and post-launch iteration.
-
Metrics such as conversion, usage, cycle success, service incidents, returns, NPS, attachment, and reliability.
What a Strong Answer Covers
-
Clear product vision and user segmentation.
-
Practical MVP and phased roadmap.
-
Technical and operational feasibility.
-
Metrics that connect user value to business outcomes.
-
Scenario-specific trade-offs and risks.
Follow-up Questions
-
What would you cut from v1?
-
Which metric would you choose as the North Star?
-
What is the biggest operational risk?
-
How would you validate demand before building?
-
What backend dependency worries you most?
