Vet and stage the launch of an inherited product list as a new e-commerce PM

You have just joined an e-commerce company as a product manager. Before you arrived, the team drew up a list of "suggested products". Explain how you would review that list and how you would roll out the products that come out of the review. ### Clarifying Questions - Is the list made up of new features or services for the store and its shoppers, new merchandise the company would start selling, or items to be recommended to shoppers? - Which outcome is the company focused on right now (new customers, conversion, order value, repeat purchases or margin), and is the team measured against a specific target? - How long is the list, how much engineering capacity is there, and has any item already been started or promised to leadership? - What evidence sits behind each suggestion: customer research, data analysis, a competitor's move, or a stakeholder's request? ### Part 1 — Review the list Describe how you would assess the suggestions: what you need to learn first, which criteria you would apply, and how you would decide which items go ahead, wait or are dropped, keeping in mind that you are new and the team wrote the list. ```hint You did not write this list Before ranking anything, find out what problem and evidence each item came from and what the company most needs right now. Re-ranking the team's ideas on instinct costs you both accuracy and the team's trust. ``` #### What This Part Should Cover - The context gathered before judging: company goals, customer and funnel data, and the reasoning behind each item. - Explicit criteria applied the same way to every item, including the strength of the evidence and the cost. - A decision process that involves the team and ends in a clear call for every item. ### Part 2 — Roll out the chosen products For the items you decide to pursue, explain how you would order them, validate them, release them to shoppers, measure the results and decide whether to expand, change or withdraw each one. ```hint Release small enough to learn An online store can show a change to a small slice of shoppers and compare them with everyone else. Decide what you would need to see in that slice before widening it, and what would make you pull back. ``` #### What This Part Should Cover - An order based on dependencies, risk, expected impact and the sales calendar. - A staged release with success metrics and guardrails set before launch. - Decision rules for expanding, iterating or rolling back, and how results are shared. ### What a Strong Answer Covers - Pinning down what the list actually contains before proposing a process. - A review grounded in company goals and evidence rather than opinion. - A transparent prioritization method with explicit criteria. - A staged, measured rollout with guardrails and a rollback plan. - Bringing the team along as a new PM who inherited someone else's list. ### Follow-up Questions - The executive who sponsored one suggestion wants it shipped first, but it scores low on your criteria. How do you handle that? - An A/B test of one launched product shows more conversions but also more returns. Do you expand it? - Two items on the list both change the checkout page. How do you sequence and test them so that their effects can be told apart?