6 Things Product Managers Should Stop Wasting Time On
Product management is a role with an essentially unlimited demand on attention — there are always more stakeholder relationships to maintain, more user research to conduct, more backlog items to refine, more strategic questions to investigate. Given this reality, the activities product managers spend time on are consequential: time consumed by low-value activities is time unavailable for high-value ones.
These six activities are consistently the most significant time-wasters in product management — activities that consume real PM attention without producing proportionate strategic value.
1. Over-Specifying Features That Will Evolve During Development
Detailed specifications written weeks before development begins are frequently outdated by the time development starts — because the team will discover information during development that requires changes. The investment in creating comprehensive upfront specifications is wasted when those specifications become obsolete before they’re used.
The more productive investment is in articulating the user problem clearly, establishing acceptance criteria that define success, and remaining available to make decisions as implementation specifics are worked out during development.
2. Attending Every Meeting That Might Benefit From PM Presence
Product managers are often pulled into meetings on the logic that they “might have useful input.” This is true but insufficient justification: PMs might provide useful input to hundreds of meetings per quarter, and attending all of them would leave no time for the high-value product work that only PMs can do.
The discipline is distinguishing meetings that require PM input from those that would benefit from it but can proceed without it.
3. Maintaining Elaborate Feature Scoring Spreadsheets
Sophisticated feature scoring models — with 12 weighted criteria, confidence intervals, and elaborate calculation formulas — are a form of analytic theater that produces an impression of rigor without proportionate accuracy. The inputs to these models are themselves estimates; the precision of the calculations typically exceeds the precision of the estimates they’re calculating.
A simpler framework applied consistently and honestly produces better decisions than an elaborate one applied with false precision.
4. Producing Documentation Nobody Reads
Many product teams have invested in comprehensive product specifications, strategy documents, and decision logs that nobody reads. The solution to this isn’t producing better documentation — it’s producing less documentation, chosen more carefully for the audiences that will actually use it.
5. Reactive Customer Requests Without Prioritization Discipline
Responding to each customer request as it arrives — immediately acknowledging it, investigating it, providing personalized updates — creates the impression of responsiveness while consuming enormous PM time with low strategic leverage. A systematic feedback management process that aggregates, synthesizes, and responds to patterns is more valuable and more efficient.
6. Solving Problems That Engineering Should Own
When technical issues arise that block development, some PMs jump in to investigate, facilitate engineering conversations, or track down answers on the development team’s behalf. While collaborative, this is typically both an overreach into engineering’s domain and an inefficient use of PM time that would be better spent on product strategy.
Key Takeaways
The six time-wasters above have a common characteristic: they represent value-creating activities taken to an extreme where the marginal value of additional investment falls below the opportunity cost. Recognizing this threshold — and redirecting time to the high-leverage PM activities that are typically underinvested — consistently produces better outcomes than optimizing any of the low-value activities.
The Metrics Review Ritual
The practices described here are most powerful when they’re embedded in regular rituals: quarterly strategy-metrics alignment reviews, monthly leading indicator check-ins, and sprint reviews that explicitly connect the sprint’s completed work to the strategic outcomes it was designed to advance. These rituals create the organizational discipline that prevents metrics from drifting from strategy, and they create the accountability for making the connections explicit rather than implicit.
The Organizational Health Signal
Teams where metrics aren’t connected to strategy often have a deeper organizational problem: strategy isn’t actually guiding decisions. When the roadmap is built from stakeholder requests rather than strategic priorities, and metrics are selected for trackability rather than strategic relevance, the metrics problem is a symptom of the strategic problem. Fixing the metrics without fixing the underlying strategic disconnect produces better-looking dashboards without better product decisions.
Teams that build the habit of connecting strategy to metrics early, before the pressure of execution makes it feel like overhead, develop the discipline most naturally. Once established, the strategy-metrics connection becomes the lens through which all product decisions are evaluated — which is exactly the goal.