Annual Planning: What Will the Product Team Work On?
Updated: Nov 8
In short: once the company goals are set, don't plan the year around the products you already have. Take a step back, write one story of how the product will help the organization reach its goals, pick only a few bets with a clear "stop" definition, and decide what current work you'll drop to make room for them.
The 2027 company goals are set. So what will the product team actually work on?
This is the question I'm working on with my clients right now. It's annual planning season, the company goals are finally agreed, and everyone is ready to move. And this is exactly the moment when it's easiest to go back to business as usual.
What's the First Instinct?
The first instinct is usually to start from the products we already have and plan the year around them. What can we add, what should we fix, what did we promise last year that we still haven't delivered.
It makes sense. It's what the team knows, it's already in motion, and there are people, budgets and commitments attached to it.
But the company goals are new information. For the first time in months, we know where the organization is going. If we plan the year from the products we already have, we miss the chance to ask if they're still the best way to get there.
Why Is Annual Planning the Right Moment?
Once the roadmap is set and the work has started, changing direction gets expensive. People are assigned, promises are made, and every change feels like a step back.
Right now, nothing is locked yet. It's a good moment to check that we're building what's most valuable for our customers and for these new goals, and to challenge what comes next.
That doesn't mean throwing everything away and starting from zero. Most of what a team is already doing is there for a good reason. It means looking at it again, with the new goals in front of us, before we commit to another year of it.
So how do we do it while keeping our feet on the ground?
What I'm Doing With My Clients
1. Take a step back.
Ask why we're here, and how everything we do works together to create value.
This isn't about one product or one feature. It's about the whole picture: the products, the services and the teams, and how together they help the people we serve. When we look at it this way, we often find that the value is in how things connect, not in any single product.
2. Write one story.
Write a story of how the product will help the organization get to its goals. Base it on what we learn from customers and data, and use the products we already have, but don't start from them.
Why a story? Because a story is something everyone can follow, from leadership to the teams doing the work. If we can't tell it in a simple way, we're probably not ready to choose where to focus.
3. Pick only a few bets.
Bets are our best guesses for what will get us there. And a bet is exactly that, a bet. Some won't work.
So we pick only a few, and we agree on a "stop" definition for each one: how we'll know early that it isn't working. Without it, a bet slowly turns into a project that never ends, because nobody ever decided what "not working" looks like.
4. Drop something.
Decide what current work we'll drop to make room for the new bets.
This is the hardest step, and the one most teams skip. Planning usually only adds. But the new goals don't come with extra people or extra hours. If nothing stops, the new bets just pile on top of everything else, and nothing gets the focus it needs.
If you're using AI in your planning sessions this year, I also shared my dos and don'ts for that here.
Do You Need a Product Team for This?
No. I use these steps with product teams, and I use them with organizations that don't have a product team at all. Many of the teams I work with build programs, services and tools without anyone calling it "product".
The questions are the same. Where are we going, what's most valuable to get there, and what are we willing to stop doing to make room for it.
The goals tell us where we're going. The bets are how we find out if we can get there.
FAQ
What should a product team do after the company goals are set? Take a step back before planning any work. Look at how everything you do creates value, write one story of how the product will help the organization reach its goals, and only then choose a few bets.
What's a product bet? A bet is your best guess for what will help you reach a goal. It's called a bet because some won't work, so you pick only a few and check early if they're working.
What's a "stop" definition? It's how you'll know early that a bet isn't working. You agree on it before you start, so the bet doesn't turn into a project that never ends.
Why should we drop work during annual planning? Because new goals don't come with extra people or extra hours. If nothing stops, the new bets pile on top of everything else and nothing gets real focus.



Comments