PM thread: prioritize via outcomes
A threaded dialogue between junior and senior product managers argued that teams should filter user feature requests through product strategy and desired outcomes—favoring high-impact bulk actions over one-off custom dashboards. The thread frames prioritization as matching user needs to measurable business outcomes, not simply triangulating raw feedback volume. That approach gives a clear rubric for roadmap choices and for defending trade-offs during interviews and stakeholder reviews. (x.com)
A junior product manager asks a familiar question: if 20 customers request a custom dashboard and 3 customers ask for bulk actions, which one goes on the roadmap first? The senior answer is that counting requests is not strategy; the first step is asking which option moves a business outcome like retention, activation, or expansion. (threadreaderapp.com) That sounds abstract until you picture the work. A custom dashboard often helps one account see information in its own preferred layout, while bulk actions can let every account edit 500 records in one move instead of 500 clicks. (eleken.co) Product teams usually hear the loudest pain, not the biggest opportunity. Sales hears the deal at risk this week, support hears the ticket that exploded this morning, and leadership hears the customer with the largest contract value. (threadreaderapp.com) That is why raw feedback volume can mislead a roadmap. Ten requests from ten different people can still point to a narrow edge case, while three requests can reveal a repeated workflow that affects onboarding speed, error rates, and daily usage across the whole product. (threadreaderapp.com) The senior product manager’s filter is simple: start with the company goal, then trace the chain from feature to user behavior to metric. If nobody can explain how feature X changes metric Y, the team does not have a strategy; it has a formatted wish list. (threadreaderapp.com) That changes the dashboard-versus-bulk-action debate. If the company needs expansion revenue in enterprise accounts, a dashboard that closes a six-figure renewal can win; if the company needs broader activation and lower support load, bulk actions can beat a louder but narrower request. (threadreaderapp.com) The point is not “ignore customers.” The point is to translate customer requests into the underlying job, like “I need to review 2,000 rows faster” or “I need executives to spot anomalies in 30 seconds,” because the request is often just the customer’s guessed solution. (threadreaderapp.com) Good teams build a habit around that translation. George Nurijanian’s other writing recommends capturing feedback in a structured format with issue type, customer segment, and impact, so product managers can compare patterns instead of reacting to anecdotes. (threadreaderapp.com) That gives a product manager a defensible sentence in roadmap reviews: “We are not declining dashboards because users are wrong; we are choosing the workflow that improves time-to-value for 60 percent of active admins and cuts support tickets in the segment we need to grow.” Clear outcomes beat vague empathy every time. (threadreaderapp.com) It also explains why strong product interviews keep circling back to outcomes. Interviewers are testing whether a candidate can turn a pile of requests into a decision rule, name the metric that matters, and show the trade-off without hiding behind “the customer asked for it.” (nurijanian.substack.com) The senior product manager in that exchange is really describing a shift in job definition. A product manager is not a vote counter or a backlog clerk; the job is choosing the smallest set of bets that creates the most value for users and the business at the same time. (threadreaderapp.com)
