Post-Launch Scorecard for an Apple Release: Customer Experience and Competitive Position

Apple refreshes its products on a regular cadence, adding features and changing designs. Take a recent update to an Apple product and explain how you would work out what it did for two things: the experience of the people who use the product, and Apple's standing against its competitors. ```hint Separate the update from the calendar Apple launches land on a predictable upgrade cycle, a holiday season and rival launches. Decide what you will compare against before you choose metrics, so that the effect you report belongs to the update and not to the time of year. ``` ### Clarifying Questions - Should I pick the update, or is there one in mind, such as a new iPhone generation, a Mac chip transition or an operating-system release? - Is the analysis meant to support a decision (fix, reprice, carry the change into the next generation), or is it a retrospective readout? - Can I assume access to Apple's internal data such as sales, returns, support contacts, opt-in device analytics and surveys, or only to public data? - Should the analysis be global, or focused on particular markets? ### What a Strong Answer Covers - A specific update with explicit hypotheses about what it should change for users and for Apple's competitive position - A credible baseline when no randomized test is possible, separating the update's effect from seasonality, pricing and the normal upgrade cycle - User-experience measures covering adoption and use of the new capabilities, satisfaction, support contacts, returns and qualitative feedback, cut by segment - Competitive measures covering upgrades, switching to and from rivals, model mix and pricing power, and share of the premium segment - A synthesis into a verdict and next steps that states how strong the evidence is ### Follow-up Questions - In its first month the new model sells fewer units than the previous generation did at the same point. How do you tell whether the update is to blame? - Owners praise a new feature in surveys, but usage data shows few of them use it. How do you reconcile the two? - How would your approach change for a software update delivered to devices people already own?