5 Product Management Resolutions That Actually Make a Difference
The typical professional New Year’s resolution is a vague aspiration: “be more strategic,” “communicate better,” “focus more on users.” These are genuinely good intentions that rarely translate into changed behavior, because they’re not specific enough to act on and not measurable enough to know whether they’re happening.
The product management resolutions that actually make a difference are the specific, actionable commitments that can be scheduled, tracked, and evaluated — ones that, if kept, would genuinely change the quality of product work.
Resolution 1: Talk to At Least Two Users Every Week, Every Week
Most product managers talk to users less frequently than they know they should. The resolution to conduct user research “regularly” or “more often” fails because it creates no specific commitment. The resolution to talk to at least two users every week — scheduled, tracked, and held to even during busy periods — creates the habit that transforms user understanding from occasional to continuous.
Two conversations per week is 100 per year. This volume creates the pattern recognition that makes product intuition genuinely reliable rather than lucky.
Resolution 2: Write Down the Reasoning Behind Every Significant Product Decision
Product decisions made without documented reasoning repeat themselves when new team members join, when stakeholders challenge historical choices, and when the PM needs to remember why a direction was chosen. The habit of writing one paragraph of reasoning for every significant decision — in a shared, searchable format — creates organizational memory that pays dividends for years.
Resolution 3: Define Success Before Every Feature, Not After
The most common product measurement failure is beginning success measurement only after a feature ships — when the team naturally gravitates to the metrics that show best. The resolution to define specific success metrics before every feature enters development creates the accountability that drives honest post-launch evaluation.
Resolution 4: Have One Difficult Conversation Every Week
Product managers who avoid difficult conversations — the stakeholder relationship that’s drifting, the team dynamic that’s creating friction, the strategic disagreement that hasn’t been surfaced — accumulate unresolved problems that eventually become crises. The resolution to have one difficult conversation per week — addressing something real rather than something comfortable — creates the discipline that prevents small problems from becoming large ones.
Resolution 5: Spend 20% of Your Time on Discovery, Every Sprint
The discovery work that most directly improves product quality — user research, competitive analysis, prototype testing, exploratory customer conversations — is the first thing squeezed by execution pressure. The resolution to protect 20% of time for discovery work in every sprint, regardless of sprint demands, creates the sustained investment that keeps the product grounded in user reality.
Key Takeaways
The product management resolutions that make a real difference are specific, actionable, and accountable: two user conversations weekly, documented decision reasoning, pre-defined success metrics, regular difficult conversations, and protected discovery time. Each of these creates a new behavior rather than an aspiration, and each would, if maintained through the year, measurably improve the quality of product work and the product outcomes that follow.
Building the Why Habit
Like any habit, asking “why?” consistently requires practice before it becomes automatic. Starting with low-stakes contexts — asking why in routine team meetings about minor backlog items — develops the habit before it’s needed for high-stakes decisions where the discomfort is highest. Product managers who practice the question consistently in every context find that it becomes a genuine cognitive reflex rather than a deliberate technique, and that the product decisions that emerge from reflexive “why?” asking are consistently better than those that don’t.