My first instinct was to go straight to revenue and I think that was the wrong entry point.
Acknowledge the request without defensiveness, then reframe the conversation around Google's strategic priorities and Maps' unique value. Build a data-driven case that quantifies Maps' contributions to revenue, user engagement, and ecosystem lock-in, while proposing a forward-looking investment thesis. Close by inviting a collaborative discussion on trade-offs rather than simply defending the status quo.
Pro tip: Don't just defend Maps—show you understand why the shutdown request might exist (e.g., cost concerns, strategic shift) and address those root causes with data and alternatives. This demonstrates strategic empathy and maturity.
Ask clarifying questions to understand the rationale behind the request (e.g., cost, strategic focus, performance) without being confrontational. This shows you're listening and helps tailor your response.
Present data on Maps' direct and indirect contributions: revenue (ads, licensing), user engagement (DAU/MAU, time spent), and ecosystem integration (Search, Assistant, Android, Cloud).
Explain how Maps fortifies Google's position against competitors (Apple, Amazon, TomTom) and enables future innovations (AR, autonomous vehicles, local commerce).
If cost is a concern, suggest optimizations (e.g., reducing low-value features, leveraging AI for efficiency) or a phased investment plan that aligns with broader company goals.
Propose a collaborative review with stakeholders to evaluate trade-offs and make a data-informed decision, reinforcing your commitment to Google's success.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.