Ditch the resolution: Smarter goal setting for product leaders

Every January, my feed fills up with declarations like “This is the year!” or “New year, new roadmap!” And just like that, product teams rush to set big, sweeping goals. But much like personal resolutions, these reactive goals rarely survive the first quarter.

And honestly? I get it. I’ve made the same mistake — both personally and professionally.

When it comes to goal setting for product leaders, the temptation to overhaul everything in Q1 is real. But resolutions often lead to more chaos than clarity. Let’s talk about why product leaders should stop setting traditional resolutions — and what to do instead.

The problem with resolutions in product teams

Resolutions feel good in the moment. They’re shiny. They suggest change. But too often, they’re reactive responses to perceived shortcomings — like a drop in engagement, a late feature launch, or a competitor’s flashy new release.

That’s when we see:

• Feature dumping to “catch up” or make a splash.
  
• Vanity metrics prioritized over meaningful outcomes.
  
• Unrealistic roadmaps that ignore team capacity and user needs.
  

Resolutions like these set teams up to fail. Why? Because they’re:

• Too vague (“We’ll be more innovative!”),
  
• Too ambitious without structure (“Let’s double our user base!”),
  
• And not tied to a long-term product vision.
  

Product teams deserve better.

It’s time to rethink goal setting for product leaders. Instead of short-lived resolutions, the best teams use frameworks grounded in vision, data, and user needs — not gut reactions or competitor pressure.

Why I stopped setting resolutions (and what I do instead)

Years ago, I gave up resolutions in my personal life after failing one too many times. Instead, I started choosing a guiding word each year — something that grounded me in how I wanted to grow, not just what I wanted to do.

As a leader, I realized this practice translated beautifully into product strategy.

When your goals are rooted in values and direction — not just performance metrics — your team is more aligned, focused, and motivated. Think of it like a North Star.

Some of my past words:

• “Vibrant” — when I needed to step into visibility as a business owner.
  
• “Fearless” — which taught me I really needed courage, not fearlessness.
  
• “Aware” — which pushed me to become more attuned to my team, my clients, and myself.
  

Each word became a lens through which I made decisions — and that approach worked better than any checklist or resolution.

What this looks like in a product setting

Let’s say your team’s Q1 resolution is: “Improve retention.”

Sure, that’s important. But it’s also vague.

Instead, imagine your guiding focus is “Clarity.” That shifts the conversation:

• Do users understand the value they’re getting?
  
• Are our onboarding steps clear?
  
• Is our roadmap aligned with what users actually need?
  

Then, instead of vague resolutions, you start using tools like:

• OKRs that ladder up to your product vision,
  
• UX metrics that reflect real user outcomes,
  
• Agile planning that adapts based on evidence, not impulse.
  

We’ve seen this with product teams that come to us after setting ambitious goals but seeing little progress. Once we slow down and refocus on real user needs, their goals start to shift — from feature delivery to experience outcomes. With the right UX metrics and OKRs, teams stop reacting and start leading.

In our experience, the most successful goal setting for product leaders isn’t reactive — it’s reflective, strategic, and connected to how users actually experience the product.

Make goal setting intentional (and user-centered)

If you’re a product leader, you’re not just setting goals for your team — you’re shaping how your entire organization defines success.

So here’s what I recommend instead of New Year’s resolutions:

1. Choose a North Star value for the year — something that reflects the kind of product experience you want to deliver.
   
2. Align goals with product vision — tie everything to that bigger picture.
   
3. Use OKRs to break big ideas into actionable outcomes — and make sure they’re measurable and meaningful.
   
4. Loop in user insights early and often — real user needs should shape what gets prioritized.
   

And don’t wait for January. The best time to set better goals? Right now.