Netflix recommendation sharing: define, scope and launch the feature

Netflix has already decided to build a feature for sharing recommendations. As the product manager who owns it, explain what happens next: how you turn that decision into a defined, built and launched feature, and how you would know it is working. ```hint Define it before planning it The feature's name could describe several different products depending on who shares, what is shared and where it goes; settle that before planning the work. ``` ### Clarifying Questions - Does sharing recommendations mean sending a single title to someone, publishing a list others can follow, or passing on the picks Netflix makes for you? - Who can receive a share: profiles in the same household, other Netflix members, or anyone through a link in a messaging app? - What is the feature meant to move: engagement of current members, retention, or new sign-ups? - Are there constraints on timeline, team size or launch markets? ### What a Strong Answer Covers - A concrete definition of the feature and the goal it serves, settled before any planning - The senders and recipients the first version serves, and what each of them needs - A scoped first version, what it deliberately leaves out, and the teams and dependencies involved in building it - A rollout and experiment design with a success metric and guardrails - Risks specific to sharing what people watch, and the rules for shipping, iterating or stopping after the test ### Follow-up Questions - If engineering says one part of the first version will take much longer than planned, how do you decide what to cut while keeping the test meaningful? - The test shows many shares but no change in viewing time or retention. What do you conclude, and what do you try next? - How would your plan change if the main goal were attracting new members rather than engaging current ones?