Fixing a frustrating everyday product and planning its market launch

Choose a product that you use every day, that you dislike, and that you cannot easily avoid. Explain what makes it frustrating, propose how you would improve it, and describe how you would bring the improved version to market. ### Clarifying Questions - Can the product be one my employer requires me to use, or should it be a consumer product from my personal life? - Should I pick a Google product, or is any product fine? - For the go-to-market part, am I a PM at the company that owns the product, or an outsider launching a competing alternative? - Is there a time frame or resource limit for the improvement, such as what a small team could ship within a set period? ### Part 1 — Choose the product and diagnose the problem Name the product, explain why you still have to use it every day, and break down what makes it frustrating. Identify who else shares the frustration and which pain point matters most. ```hint Why can't you quit it? The reason you are stuck with the product (an employer mandate, a network effect, no real alternative) shapes both the fix and the launch. Say it out loud before listing complaints. ``` #### What This Part Should Cover - A product that genuinely fits "disliked but used daily", with the lock-in reason stated. - User segments beyond the candidate and the distinct pain points of each. - One pain point chosen on frequency, severity and breadth, with evidence beyond personal annoyance. ### Part 2 — Improve it Propose improvements that address the pain point you chose, decide what to build first, and explain how you would measure whether the change worked. ```hint Root cause first Ask why the frustrating moment exists from the product owner's side, not just yours: an incentive, a technical constraint or a missing signal often explains it, and the strongest fix targets that cause. ``` #### What This Part Should Cover - Several distinct solution ideas compared on impact, effort and risk. - A scoped first version with the reason it comes first. - Success metrics and guardrails tied to the chosen pain point. ### Part 3 — Take it to market Explain how you would launch the improvement: which users you would target first, how you would position it, which channels and pricing or packaging you would use, and how you would roll it out. ```hint Start where the pain peaks Look for the users and the moment in which the problem hurts most; that is a natural first audience and a natural place to introduce the change. ``` #### What This Part Should Cover - A launch segment and positioning tied to the pain point. - Channels, pricing or packaging, and a phased rollout with go or no-go criteria. - Launch metrics and the main adoption risks. ### What a Strong Answer Covers - One coherent thread from the frustration through the fix to the launch, rather than three disconnected answers. - Empathy for users other than the candidate, backed by data or research they would gather. - Prioritization with explicit trade-offs at each stage. - Measurable outcomes for both the product change and the launch. ### Follow-up Questions - Your improvement raises user satisfaction but lowers a revenue metric the product's owner cares about. How do you make the case for shipping it? - Adoption after launch is far below target. How do you tell whether the problem is the product or the go-to-market? - A competitor copies your improvement within a few months. What keeps your advantage?