Find an Unmet Need Among iPhone Users and Propose an iOS Improvement

Quick Overview

A product improvement prompt that puts the candidate in charge of iOS, Apple's iPhone operating system, and asks how they would make it better. It tests narrowing a huge user base to one segment, finding needs that iOS does not already address, prioritizing privacy-respecting solutions, and measuring impact.

Find an Unmet Need Among iPhone Users and Propose an iOS Improvement

Company: Adobe

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Imagine you are the product manager responsible for iOS, the operating system that runs Apple's iPhone. How would you improve it? Choose the users the improvement is for, the problem you would solve for them, the changes you would make, and how you would know the changes succeeded. ```hint Narrow before you build iOS serves a vast and varied user base, so improving it for everyone at once leads to a vague answer. Pick one group of iPhone users and one situation where iOS lets them down today, and check that your fix is not something iOS already ships. ``` ### Clarifying Questions - Is the improvement for the iPhone only, or should it also consider how iOS works with the Apple Watch, iPad and Mac? - What should the change do for Apple: strengthen loyalty and upgrades, grow paid services, or raise customer satisfaction? - Should I target a particular group, such as parents, older users or power users, or is the whole iPhone base in scope? - Which constraints must I respect, such as Apple's on-device privacy approach and the yearly iOS release cycle? ### What a Strong Answer Covers - Apple's goal for iOS and how the proposed improvement serves it, stated before any features. - A segmentation of iPhone users with a reasoned choice of one group. - Specific pain points for that group, with awareness of what iOS already offers so the proposal is not an existing feature. - Prioritized solutions that fit Apple's privacy and design principles, with a rollout plan. - Success metrics with guardrails, including how to measure impact when usage data is limited, and the main risks. ### Follow-up Questions - Apple collects limited usage data by design. How would you measure whether your improvement worked? - Your improvement works best if third-party app developers adopt a new API. How would you get them to? - What evidence from the beta would make you hold the feature back from the next release?

Overview: A product improvement prompt that puts the candidate in charge of iOS, Apple's iPhone operating system, and asks how they would make it better. It tests narrowing a huge user base to one segment, finding needs that iOS does not already address, prioritizing privacy-respecting solutions, and measuring impact.

Adobe logo
Adobe
Aug 18, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Imagine you are the product manager responsible for iOS, the operating system that runs Apple's iPhone. How would you improve it? Choose the users the improvement is for, the problem you would solve for them, the changes you would make, and how you would know the changes succeeded.

Clarifying Questions Guidance

  • Is the improvement for the iPhone only, or should it also consider how iOS works with the Apple Watch, iPad and Mac?
  • What should the change do for Apple: strengthen loyalty and upgrades, grow paid services, or raise customer satisfaction?
  • Should I target a particular group, such as parents, older users or power users, or is the whole iPhone base in scope?
  • Which constraints must I respect, such as Apple's on-device privacy approach and the yearly iOS release cycle?

What a Strong Answer Covers Guidance

  • Apple's goal for iOS and how the proposed improvement serves it, stated before any features.
  • A segmentation of iPhone users with a reasoned choice of one group.
  • Specific pain points for that group, with awareness of what iOS already offers so the proposal is not an existing feature.
  • Prioritized solutions that fit Apple's privacy and design principles, with a rollout plan.
  • Success metrics with guardrails, including how to measure impact when usage data is limited, and the main risks.

Follow-up Questions Guidance

  • Apple collects limited usage data by design. How would you measure whether your improvement worked?
  • Your improvement works best if third-party app developers adopt a new API. How would you get them to?
  • What evidence from the beta would make you hold the feature back from the next release?