I didn’t jump straight to routes or traffic. Instead, I asked myself: who are we under-serving, and what business outcome are we chasing? We aligned on India, mobile (iOS/Android), and an engagement goal: lift DAU/MAU within six months. With that, I segmented users by use-case frequency and chose a non-obvious but high-leverage segment: K–10 kids. They rarely open Maps themselves, but introducing them early can create new, repeatable sessions and long-term habits (with the right safeguards).
What I learned about this segment
Kids typically experience Maps passively—sitting beside a parent, tapping “start,” or peeking at the blue dot. They’re curious (landmarks, places), but current flows don’t give them agency. The last mile is also confidence-sensitive: kids won’t be allowed to navigate alone unless the experience is built for safety and trust.
Key problems to solve
No kid-friendly entry points or reasons to open Maps on their own.
Curiosity and learning (social science, geography) aren’t connected to Maps in a structured way.
Parents don’t trust solo navigation; there’s no “safe radius” or guardrails.
Moments kids care about (e.g., “that ice-cream shop we passed”) aren’t captured effortlessly.
What I’d build
Kids Mode (priority 0–6 months): a gated profile with a parent-defined safe radius, vetted POIs (schools, libraries, playgrounds), simplified UI, and “hand-off” guidance (“now ask an adult to confirm”). Parents get real-time follow and proactive alerts. This creates new, short, safe sessions that can repeat daily.
Contextual Maps (6–18 months): a lightweight memory of kid-initiated moments—“save this place,” “remind me on Saturday,” or “bookmark this route for tuition.” Voice-first capture; replay as nudges.
Voice Travel Buddy: a constrained, child-safe assistant layered on Google Assistant: “What’s that monument?” “Can we stop for water?” Minimal counter-questions, predictable, parent-approved responses.
Maps for Education: teacher/parent-enabled collections that turn syllabus topics into map explorations (rivers, forts, landforms) with safe, tappable stories. This ties curiosity to repeat usage.
Why start with Kids Mode
It maximizes reach (every family smartphone), has clear impact on DAU/MAU via short, frequent sessions, and is feasible within six months by reusing existing permissions, Live View, Location Sharing, and Family Link primitives. Contextual memory and the travel buddy follow once the base loop exists; education layers on as a distribution channel via schools.
Risks and trade-offs
Performance on low-end devices (solve with a low-graphics variant), over-notification risk (parent controls, sensible defaults), and safety/accuracy (whitelist POIs, strict policies, parent confirmation at decision points).
How I’d measure it
North Star: DAU/MAU for Kids Mode profiles.
Leading indicators: new kid profiles created, weekly active kid sessions, average kid session length, % successful “safe-radius” trips, saves/bookmarks created by kids, parent opt-in/retention.
Counter-metrics: parent-reported confusion, drop-offs during setup, any decline in core adult navigation satisfaction.
Summary
Rather than squeezing another minute from commuters, I’d unlock a new, habit-forming user loop: make Maps a safe, simple companion for kids and a trusted co-pilot for parents. Ship Kids Mode first to create frequent, low-friction sessions; then deepen value with contextual memory and a tightly scoped travel buddy, and finally scale learning through education bundles. This sequencing grows engagement quickly, responsibly, and in a way competitors aren’t addressing.