Shortlist strong enterprise products, then set KPIs, a North Star and roadmap for one

This is a multi-part product sense exercise about enterprise software: products that businesses buy for their employees or their operations. First, name five enterprise products you consider well built and with strong market potential, and justify each choice. Then pick one of them and work through how you would measure and grow it. ### Clarifying Questions - Does enterprise software here include developer and data infrastructure sold to companies, or only applications that employees use directly? - Should market potential mean room for the product itself to grow, or the size and growth of the market it competes in? - When I pick one, should I answer as the product manager at the company that builds it, and should the roadmap cover the next year or a longer horizon? ### Part 1 — Five well-built enterprise products with room to grow List five enterprise software products that you think are well made and have strong market potential, and explain what earned each one its place. ```hint Set your tests first Choose two or three tests for "well built" and for "market potential," such as how people adopt the product and what keeps customers paying, and run every pick through them so the list is more than five familiar names. ``` #### What This Part Should Cover - Explicit criteria for product quality and for market potential, applied to every pick - A varied list covering different buyers, categories or pricing models - A specific reason for each pick, grounded in how the product works or how it sells ### Part 2 — Success KPIs and a North Star Choose one product from your list. Define the KPIs that would tell you it is succeeding, then choose one North Star metric for it. ```hint Find the value moment Ask what a customer gets each time the product does its job well, and who sees that value: the person using it every day or the person who pays for it. ``` #### What This Part Should Cover - KPIs spanning adoption, engagement, retention, expansion and revenue, with user-level and account-level measures kept apart - A precisely defined North Star that reflects delivered value, leads revenue and can be moved by the product team - Guardrails that would catch the North Star being inflated in ways that do not help customers ### Part 3 — A roadmap driven by the North Star Given that North Star, lay out the roadmap you would pursue. ```hint Break the metric apart Split the North Star into the few inputs that combine to produce it, then let each roadmap theme push on one of them. ``` #### What This Part Should Cover - Roadmap themes traced to specific inputs of the North Star - A sequence over time with reasons: dependencies, impact, effort and risk - How the effect of each theme on the metric would be checked ### Part 4 — Features that need special attention For the product and the use case you chose, which features need particular care, and why? ```hint Think beyond the daily user In enterprise deals, the people who approve, secure and administer a tool have needs that its everyday users never see. ``` #### What This Part Should Cover - Features specific to the chosen product and use case rather than a generic checklist - The needs of buyers, administrators and security teams alongside those of end users - Which features block a sale or renewal and which drive daily use, in priority order ### What a Strong Answer Covers - A consistent thread from the selection criteria in Part 1 to the chosen product's metrics, roadmap and feature priorities - Recognition that enterprise products have distinct users, buyers and administrators, with each Part addressing the right ones - Metrics and roadmap items specific to the chosen product, not interchangeable with any software tool - Explicit trade-offs, such as one large customer's requests against broad user needs, or bottom-up adoption against top-down controls ### Follow-up Questions - If you had picked a product priced on usage rather than per seat, how would your North Star change? - Your largest customer demands a feature only they need, and building it would delay a roadmap theme. How do you decide? - Your North Star grows for two quarters while revenue retention falls. What would you investigate first?