To avoid getting lost in data, PMs should first define the decision they need to make (e.g., improve ROI, increase usability). This goal then dictates which data to gather and from whom. Patterns should be grouped by desired user outcomes, not feature requests, creating a more strategic path to delivery.
Related Insights
In early stages, the key to an effective product roadmap is ruthlessly prioritizing based on the severity of customer pain. A feature is only worth building if it solves an acute, costly problem. If customers aren't in enough pain to spend money and time, the idea is irrelevant for near-term revenue generation.
The old product leadership model was a "rat race" of adding features and specs. The new model prioritizes deep user understanding and data to solve the core problem, even if it results in fewer features on the box.
Customers request specific features (supply), but this masks the true demand—the underlying problem they're trying to solve. Focusing on the 'why' behind the request leads to simpler, more effective solutions, like building a digest email instead of a complex 'advanced settings' page.
When handed a specific solution to build, don't just execute. Reverse-engineer the intended customer behavior and outcome. This creates an opportunity to define better success metrics, pressure-test the underlying problem, and potentially propose more effective solutions in the future.
Raw customer feedback is noise. To make it actionable for Product, organize it along two dimensions: impact and frequency. This simple framework separates signal from noise, distinguishing high-priority, high-impact issues from niche requests and creating a clear basis for roadmap decisions.
Avoid the trap of building features for a single customer, which grinds products to a halt. When a high-stakes customer makes a specific request, the goal is to reframe and build it in a way that benefits the entire customer base, turning a one-off demand into a strategic win-win.
Dedicate a recurring 'Customer Day' not only for user interviews but for the team to step back from tactical work. Use this time to synthesize existing data, analyze market trends, and refocus on the core 'why' behind the product, preventing the team from getting lost in the weeds of feature development.
Instead of waiting for experience teams to request an API, platform teams should analyze top-level business goals and proactively propose services that unlock new use cases. This shifts the dynamic from a reactive service desk to a strategic partner.
Instead of starting with available data, marketers should first identify and rank key business decisions by their potential financial impact. This decision-first approach ensures data collection and analysis efforts are focused on what truly drives business value, preventing 'analysis paralysis' and resource waste.
Outbound Sync's founder filters all product decisions through one question: 'Will this help our customer close another deal?' This value-based 'True North' allows him to prioritize ruthlessly, even fixing upstream partners' data issues if it directly impacts his customers' results.
