I jumped straight into features without anchoring on who the user actually is.
Start by clarifying the ambiguous prompt: define the user, platform, and business goal (e.g., a consumer app for discovering restaurants or a B2B tool for restaurant owners). Then structure your answer around user needs, a prioritized feature set, and success metrics, while tying choices back to Google's ecosystem and strengths.
Pro tip: Anchor your design in a specific user scenario and explicitly state what you are NOT building; this shows product maturity and prevents scope creep. Also, mention how you would leverage Google's assets (Maps, Search, Assistant) to create a differentiated experience.
Ask clarifying questions to define the target user, platform, and primary goal. For example, is this for diners or restaurant owners? Is it a standalone app or integrated into Google Maps?
Identify the core jobs-to-be-done for your chosen user. For diners: discovering restaurants, browsing menus, and ordering. For owners: managing menu updates and analytics.
Brainstorm features, then prioritize using a framework like RICE or MoSCoW. Define a minimal viable product that addresses the most critical user needs and aligns with business goals.
Sketch the key user flows (e.g., search, view menu, order) and highlight how Google's technologies (Maps, Lens, Assistant) could enhance the experience. Focus on simplicity and speed.
Propose metrics like daily active users, menu views, order conversion rate, and restaurant retention. Outline a plan for A/B testing and iterative improvements based on data.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.