1. Google Map Share & Group Chat
Product School Final Project
Thomas Rand-Nash

2. What Problems Are We Addressing?
For Users on Group Trips (now)
• Must switch between multiple apps to communicate, navigate & explore
• Cannot find or use existing location sharing tools
For Google’s Business (longer term)
• Using multiple, non-Google apps:
• Reduces information/preference gathering opportunities
• Reduces monetization opportunities
• Reduces engagement opportunities with other google products

3. What Are We Building, & Why?
What: Add map sharing + group chat to mobile maps
Why: User wins
• Reduced friction
• Seamless experience
Why: Google wins
• More & different types of user data
• More channels for relevant, high $ ads
• More channels for other google products
= Increased Engagement, Retention, Revenue
Time
Engagement / Retention Revenue

4. Who Are We Building For?

5. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off

6. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1

7. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1

8. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1

9. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1

10. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2

11. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2

12. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

13. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

14. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

15. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

16. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

17. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

18. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

19. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

20. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

21. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

22. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1 User 2
1

23. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1
1

24. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1
1

25. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1
1

26. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable feature on/off
User 1
1

27. How Will It Work?
• Should be intuitively easy to use
• Should not interfere with normal app operation
• Should enable on/off, restoring old version
User should
be able to
share map
User should be
able to invite
contacts
Invitee should
be able to
accept invite
All users should
be able to share
maps
All users should
be able to add
text & video to
group chat

28. How Will We Measure If It’s Working?
Goal: Increase user engagement & retention
Category Activity / Metric Fraction Users (MAU)
Total Total Google Maps Installs 100% 1B

29. How Will We Measure If It’s Working?
Category Activity / Metric Fraction Users (MAU)
Total Total Google Maps Installs 100% 1B
Activation New Version Updates (<1mo) 50% 500M
Goal: Increase user engagement & retention

30. How Will We Measure If It’s Working?
Category Activity / Metric Fraction Users (MAU)
Total Total Google Maps Installs 100% 1B
Activation New Version Updates (<1mo) 50% 500M
Activation Use app for group trips 20% 90M
Goal: Increase user engagement & retention

31. How Will We Measure If It’s Working?
Category Activity / Metric Fraction Users (MAU)
Total Total Google Maps Installs 100% 1B
Activation New Version Updates (<1mo) 50% 500M
Activation Use app for group trips 20% 90M
Activation /
Engagement
Share map within 1mo 26%
Retention /
Engagement
Contribute chat content
• >100 text / mo
• >5 pictures per month
• >75 min/mo
75%
Retention Continue using 3mo later 75%
23.5M
35M
26M
Goal: Increase user engagement & retention

32. How Will We Measure If It’s Working?
Category Activity / Metric Fraction Users (MAU)
Total Total Google Maps Installs 100% 1B
Activation New Version Updates (<1mo) 50% 500M
Activation Use app for group trips 20% 90M
Activation /
Engagement
Share map within 1mo 26%
Retention /
Engagement
Contribute chat content
• >100 text / month
• >5 pictures / month
• >75 min / month
75%
Retention Continue using 3mo later 75%
23.5M
18M
26M
Goal: Increase user engagement & retention

33. It’s Got Hook Power!
• App update notification
• Prominent share button • Accept invitation
• Friend’s new content
• New discoveries• Contribute chat content
• Learn share/chat features
• Take a group trip, want to share

34. How Will We Measure If It’s Working?
Category Activity / Metric Fraction Users (MAU)
Total Total Google Maps Installs 100% 1B
Activation New Version Updates (<1mo) 50% 500M
Activation Use app for group trips 20% 180M
Activation /
Engagement
Share map within 1mo 26%
Retention /
Engagement
Contribute chat content
• >100 text / month
• >5 pictures / month
• >75 min / month
75%
Retention Continue using 3mo later 75%
23.5M
18M
26M
Goal: Increase user engagement & retention

35. How Will We Measure If It’s Working?
Category Activity / Metric Fraction Users (MAU)
Total Total Google Maps Installs 100% 1B
Activation New Version Updates 90% 900M
Activation Use app for group trips 20% 180M
Activation /
Engagement
Share map within 1mo 26%
Retention /
Engagement
Contribute chat content
• >100 text / month
• >5 pictures / month
• >75 min / month
75%
Retention Use once or more within 3mo 75%
47M
35M
13M
Goal: Increase user engagement & retention

36. How Will We Let The People Know?

37. How Will We Let The People Know?
Pre-Launch
 Dog fooding
 Tutorial screens, language & video
 FAQ updates
 Press release, blog language
 Multiple social media posts
Two, 2-Week Sprints

38. How Will We Let The People Know?
Pre-Launch
 Dog fooding
 Tutorial screens, language & video
 FAQ updates
 Press release, blog language
 Multiple social media posts
Two, 2-Week Sprints

39. How Will We Let The People Know?
Pre-Launch
 Dog fooding
 Tutorial screens, language & video
 FAQ updates
 Press release, blog language
 Multiple social media posts
Two, 2-Week Sprints
Launch
 Maps blog post
 Maps twitter posts
 In-app updates
 YouTube example video
 App store language & image updates

40. How Will We Let The People Know?
Pre-Launch
 Dog fooding
 Tutorial screens, language & video
 FAQ updates
 Press release, blog language
 Multiple social media posts
Two, 2-Week Sprints
Launch
 Maps blog post
 Maps twitter posts
 In-app updates
 YouTube example video
 App store language & image updates
Post-Launch
 Updated blog posts
 Gmail non-updated users

41. What Is The Roadmap?
ENGAGEMENT / RETENTION REVENUE
LONGER-TERMNEAR-TERM
Map sharing + chat
 Users get familiar with chat in maps
 Google better understands user behavior
Incorporate other services as chat bots
 Wallet, recos, event creation (roll out depends on data)
 Maps transforms into go-to app for group travel
In chat ads & recs
 Highly targeted & relevant
 High revenue per click
Data
Collection &
Analysis
Data
Collection &
Analysis
Data
Collection &
Analysis

42. What Do We Need To Built It?
Sprint 1: 2 Weeks
Goal: Map Share
Sprint 2: 2 Weeks
Goal: Group Chat, Integration
Product
Design / UX
Engineering
Marketing
Wireframe
share pages
Wireframe
Chat pages
Share Mock
ups / Assets
Chat Mock
ups / Assets
App stores
page views
Tutorial
views
FAQ
answers Marketing
walk through
Blog, press
release assets
Share QA
Help write
Release copy
Map share integration Chat integration
Share +
Chat QA
Set-up analytics
Snyc with product
to discuss new
functionality and
message
Create tutorial,
blog, social media,
app store language
App
Stores
Prep
Create YouTube
tutorial and
experience videos
Create reminder
email and
continuing blog post
language