Google Photos Improvement: Pick a User Need, Prioritize Fixes, Define Metrics

Quick Overview

A product improvement exercise on Google Photos: set a goal, choose a user group defined by why they keep photos, find their most painful unsolved problem and propose a prioritized fix. It tests segmentation, awareness of existing features, use of image understanding, and metrics with guardrails for privacy and automated mistakes.

Google Photos Improvement: Pick a User Need, Prioritize Fixes, Define Metrics

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager on Google Photos, Google's app for backing up, organizing, searching and sharing photos and videos. What would you improve, and why? Pick who the improvement is for, find the problem most worth solving for them, propose what you would build first, and explain how you would measure the result. ```hint Segment by why people keep photos Grouping users by how often they open the app tends to give every group the same problems. Ask instead why people take and keep photos, then pick the group whose problem Photos is best placed to solve. ``` ### Clarifying Questions - Which goal should the improvement serve: more engagement, growth in paid storage plans, or keeping users from moving their library to another service? - Is the scope the mobile app only, or also the web and other screens where Photos appears, such as smart displays and TVs? - Are there privacy limits the improvement must respect, such as face grouping being optional and unavailable in some regions? - Is there a known problem to start from, such as falling engagement in one group, or am I free to choose the area? ### What a Strong Answer Covers - A short description of what Photos does today and a goal for the improvement that fits Google's interests. - Segments defined by why people keep photos, and a justified choice of one. - That segment's pain points, ranked by how common and how painful they are, and checked against what Photos already offers. - Prioritized solutions with a clear first version and its trade-offs, using Google's strengths in search and image understanding. - Success metrics tied to the goal, with guardrails for privacy, wrong automatic decisions and storage. ### Follow-up Questions - Your idea relies on recognizing faces. How does it work for users who turn face grouping off or live where it is not offered? - Your improvement might reduce how much storage people use. How does that affect paid storage, and is the trade acceptable? - How would you test the change before launching it to everyone?

Overview: A product improvement exercise on Google Photos: set a goal, choose a user group defined by why they keep photos, find their most painful unsolved problem and propose a prioritized fix. It tests segmentation, awareness of existing features, use of image understanding, and metrics with guardrails for privacy and automated mistakes.

Google logo
Google
Jun 12, 2024
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager on Google Photos, Google's app for backing up, organizing, searching and sharing photos and videos. What would you improve, and why?

Pick who the improvement is for, find the problem most worth solving for them, propose what you would build first, and explain how you would measure the result.

Clarifying Questions Guidance

  • Which goal should the improvement serve: more engagement, growth in paid storage plans, or keeping users from moving their library to another service?
  • Is the scope the mobile app only, or also the web and other screens where Photos appears, such as smart displays and TVs?
  • Are there privacy limits the improvement must respect, such as face grouping being optional and unavailable in some regions?
  • Is there a known problem to start from, such as falling engagement in one group, or am I free to choose the area?

What a Strong Answer Covers Guidance

  • A short description of what Photos does today and a goal for the improvement that fits Google's interests.
  • Segments defined by why people keep photos, and a justified choice of one.
  • That segment's pain points, ranked by how common and how painful they are, and checked against what Photos already offers.
  • Prioritized solutions with a clear first version and its trade-offs, using Google's strengths in search and image understanding.
  • Success metrics tied to the goal, with guardrails for privacy, wrong automatic decisions and storage.

Follow-up Questions Guidance

  • Your idea relies on recognizing faces. How does it work for users who turn face grouping off or live where it is not offered?
  • Your improvement might reduce how much storage people use. How does that affect paid storage, and is the trade acceptable?
  • How would you test the change before launching it to everyone?