Prioritize new Outlook features for a chosen user segment and define success metrics

Imagine you are a product manager at Microsoft responsible for Outlook, the company's app for email, calendar, contacts and tasks, which runs on desktop, on the web and on iOS and Android. The interviewer asks how you would make it better. Decide whose experience you would improve and why, identify the problems that matter most to those users, propose and prioritize improvements, and explain how you would measure whether they worked. ```hint Narrow the job first Outlook serves very different people doing very different jobs: clearing an inbox, booking meetings, keeping track of what they promised. Commit to one group of users and walk through their day in the app before you brainstorm features. ``` ### Clarifying Questions - Which surface is in scope: the desktop client, the web app or the mobile apps, and are we improving it for work and school accounts, personal accounts, or both? - Which outcome matters most to the team: time saved for users, daily engagement, retention of paying business customers against rival suites, or growth in personal users? - Is any part of the product off limits or already being reworked, such as the calendar or the task list? - Must new features work within enterprise admin controls and compliance rules, for example features an IT department can switch off? ### What a Strong Answer Covers - A goal for the improvement tied to Outlook's role for its users and for Microsoft, and a reasoned choice of one segment over others such as enterprise knowledge workers, personal users or students. - Pain points drawn from a concrete workflow of that segment (inbox triage, follow-ups, scheduling across time zones, meeting preparation), ranked by how often they happen and how much they hurt. - Several distinct solutions prioritized by impact, effort and confidence, with the chosen one described clearly enough to build a first version. - A primary success metric plus guardrails suited to Outlook, such as missed important mail, notification volume and privacy. - Risks and trade-offs specific to an email and calendar product: trust in automated sorting, enterprise control, and consistency across platforms. ### Follow-up Questions - Your top idea depends on automatically judging which messages need the user's action. How do you handle a user who misses a critical email because the judgment was wrong? - How would your plan change if the goal were to win personal users from free consumer email apps instead of making business users more productive? - IT admins can disable new features for their whole organization. How does that affect your rollout plan and how you read your metrics?