Google Photos Annual Recap: Diagnose Weak Spots and Prioritize Improvements

Quick Overview

A Google Photos product improvement question about the automatic year-in-review recap. It tests goal setting for a once-a-year feature, user segmentation, handling sensitive memories, prioritizing improvements, choosing metrics and experiments, and privacy trade-offs when recaps are shared.

Google Photos Annual Recap: Diagnose Weak Spots and Prioritize Improvements

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager on Google Photos. The app builds a recap that looks back on a user's year through their photos and videos. How would you make this year-in-review feature better? Explain which users you would improve it for, where it falls short today, which improvements you would prioritize, and how you would measure success. ```hint Decide what the recap is for A feature people see once a year cannot be judged by daily use. Choose the job the recap should do for the person and for Google Photos, and let that choice decide which weaknesses matter most. ``` ### Clarifying Questions - Is the main goal to make the recap more meaningful to the person viewing it, to drive sharing that brings new people to Google Photos, or to bring people back into their library during the rest of the year? - Which users should come first: people with large libraries, casual users with few photos, or families who share albums? - Must the recap remain a once-a-year event, or could the improvement change when and how often it appears? - Are there limits on using AI to interpret faces, places and events beyond the features a user has already turned on? ### What a Strong Answer Covers - A clear goal for the recap and a chosen user segment, justified by how people use Google Photos - Specific weaknesses of an automatic recap, including painful memories, repetitive or low-quality picks, and thin libraries - Prioritized improvements tied to those weaknesses, with a defined first version - Metrics that suit a once-a-year feature (completion, saves, shares, return visits to the library) plus guardrails such as hide and negative-feedback rates - Privacy and sensitivity risks in selecting faces, places and moments automatically and in sharing the result ### Follow-up Questions - How would you test changes to a feature each user sees only once a year? - What would you do if shares rose but more people hid or dismissed their recap? - What should the recap look like for someone whose year is mostly screenshots and receipts?

Overview: A Google Photos product improvement question about the automatic year-in-review recap. It tests goal setting for a once-a-year feature, user segmentation, handling sensitive memories, prioritizing improvements, choosing metrics and experiments, and privacy trade-offs when recaps are shared.

Google logo
Google
Oct 2, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager on Google Photos. The app builds a recap that looks back on a user's year through their photos and videos. How would you make this year-in-review feature better?

Explain which users you would improve it for, where it falls short today, which improvements you would prioritize, and how you would measure success.

Clarifying Questions Guidance

  • Is the main goal to make the recap more meaningful to the person viewing it, to drive sharing that brings new people to Google Photos, or to bring people back into their library during the rest of the year?
  • Which users should come first: people with large libraries, casual users with few photos, or families who share albums?
  • Must the recap remain a once-a-year event, or could the improvement change when and how often it appears?
  • Are there limits on using AI to interpret faces, places and events beyond the features a user has already turned on?

What a Strong Answer Covers Guidance

  • A clear goal for the recap and a chosen user segment, justified by how people use Google Photos
  • Specific weaknesses of an automatic recap, including painful memories, repetitive or low-quality picks, and thin libraries
  • Prioritized improvements tied to those weaknesses, with a defined first version
  • Metrics that suit a once-a-year feature (completion, saves, shares, return visits to the library) plus guardrails such as hide and negative-feedback rates
  • Privacy and sensitivity risks in selecting faces, places and moments automatically and in sharing the result

Follow-up Questions Guidance

  • How would you test changes to a feature each user sees only once a year?
  • What would you do if shares rose but more people hid or dismissed their recap?
  • What should the recap look like for someone whose year is mostly screenshots and receipts?