Ramping Up on an Unfamiliar Product to Build Its Roadmap

You need to create a product roadmap for a product you have no prior knowledge of. Walk through how you would approach it, from getting up to speed to a roadmap the team can work from. ```hint Learn before you rank Split the work into a learning phase and a planning phase: decide what you must understand about the business, the users, the data and the commitments already made before any item earns a place on the roadmap. ``` ### Clarifying Questions - Have I just joined and inherited a live product with a team, users and possibly an existing roadmap, or is this a product that has not launched yet? - How soon is the roadmap expected, and does it have to fit a planning cycle such as a quarterly or annual review? - Who is the main audience: the engineering team, leadership, sales and customers, or all of them? - Are there commitments already made to customers or leadership that the roadmap must honor? ### What a Strong Answer Covers - A structured ramp-up across company goals, users, data, market and stakeholders by function - How the evidence becomes a ranked set of problems, with an explicit prioritization method and stated confidence - A roadmap format suited to uncertainty: problems and outcomes over dated features, more detail near term than far term - Alignment and iteration: how the draft is reviewed, shared and revised as learning accumulates - How inherited commitments and early wins are handled without locking in a plan too soon ### Follow-up Questions - Leadership wants a roadmap in your second week, before you have finished learning. What do you deliver, and how do you present its confidence? - The engineering backlog and the commitments sales made to a large customer point in opposite directions. How do you reconcile them? - A quarter later, the top roadmap bet is not moving its metric. How do you change course without losing stakeholder trust?