Product improvement plan for the Stories feature in the Facebook app

As a product manager, you are asked how you would improve Stories on Facebook, the short-lived photos and videos people share with their friends. Decide what the improvement should achieve, choose the users you are designing for, propose and prioritize changes, and explain how you would know whether they worked. ```hint Pick a side of the format A Story only exists if someone posts it, and it only matters if someone watches it. Decide which side you are working on and which group within it, then ask what stops that group from doing more of it today. ``` ### Clarifying Questions - Is the aim more people posting Stories, more Stories watched per person, more replies and conversations started from Stories, or revenue from the ads shown between Stories? - Is the scope the mobile app only, or desktop as well? - Are Stories cross-posted from Instagram, and Stories from Pages and creators, in scope, or only Stories shared among friends and family? ### What a Strong Answer Covers - A goal for Stories tied to why the format matters to Facebook, with the metric that would show progress toward it - People on both the posting and the watching side compared, with one segment chosen and the reason for the choice - Pain points drawn from that segment's path through making or watching a Story, ranked by how much each holds the segment back - Solutions compared with explicit criteria such as impact, effort and risk, ending in a prioritized plan - A primary success metric with guardrails, the main risks, and how the change would be tested before a full launch ### Follow-up Questions - How would you test your top idea when what one person posts changes what their friends see, and what result would make you roll it back? - If posting rose but each Story drew fewer views and replies, would you call the change a success? Why or why not? - Many people share the same Story to both Instagram and Facebook. How would that change your plan or the way you measure it?