Understand the Numbers, Then Own Your Part
You’re told to do everything, you still have to commit to something, and you’re held to numbers you don’t fully support. Here’s where to start.
Autumn brings vibrant colors, cooler temperatures, and the dread of annual planning.
Many companies I have worked with take the typical top-down approach. The executive team meets, often at an off-site or two, and comes up with their “numbers.” Those numbers become the goals and objectives handed to the next level of leadership, and the teams are asked to create the plan to achieve them. Essentially, make the numbers. Companies need to grow, and that growth is measured in numbers — customer growth, revenue growth, profitability growth. We all wish it started with the customer, but that is not always true.
As a product manager, this can feel overwhelming. You can see how much work there is just to fix what you already have, and you have no idea how you can do more to move the numbers you are now held to. You would hope your product leaders have carried what you know about the customer into those executive conversations, but that does not always happen.
So what can you do when it feels like you have no control over the inputs or the outputs of a plan, yet you know the customer and the problem so well?
Often, the most difficult challenge in planning is getting out of the way of your own frustration.
Start by understanding the why behind the numbers. Before you decide you don’t support the numbers, seek to understand where they came from. Ask questions about them. Talk with the people who track customers, usage, and retention. Understand the financials. You may not understand every driver behind the numbers. What you learn may confirm your doubts. However, you can still understand enough to know what you can control.
Then control what you can control. There are so many moving parts you know need to change, but the best thing you can do is show how you can change your part. Be the first domino to fall, and show how it can impact others.
I had a client once where I was rebuilding their product organization. One PM was focused on our onboarding experience. Like everyone, they were told the growth numbers. Instead of pushing back, they asked good questions about those numbers and talked with several of our Product Directors about how we tracked customers, usage, activation, and retention. They didn’t understand every driver behind customer growth, but they understood enough to see what they could influence — return usage. Did a customer come back daily, weekly, or monthly, or did they become inactive?
They saw that onboarding was where we were losing customers. We asked customers to do too much before they ever got to the product. This was a legacy problem — as the product scaled, new onboarding tasks were added and it got complicated. So they asked if they could try an experiment — cut the onboarding checklist down to the two or three key tasks and move the rest to a place customers could visit later with reminders, so nothing stopped them from starting to use the product.
I was always open to trying different approaches and experimenting — even if it wasn’t on the roadmap. But what convinced me, and what I was able to share with the executive team, was their one-page proposal — the hypothesis, the scope, the proposed impact, and the resources needed. It was clear, concise, and low cost. Was this going to solve our growth issue? Absolutely not. But it was a real opportunity to try something different and learn from it.
It worked. More people completed onboarding and took a first action, but the number we cared about was return usage, and we saw it increase. We needed to watch it over time, so they kept refining and extending the experiment. They took control of what they could control and proposed something different.
That is the lesson. Build your case, use data, and show how your work directly impacts the numbers.
Leadership will want the big initiatives that move the numbers. But it is the small ideas, the first few steps, that make all the difference. Executing alongside the roadmap, small experiments show you where to invest more. That means something has to give. With what you know about the numbers and customers, have the courage to propose deprioritizing the initiatives least likely to move the numbers.
And if you seek to understand and still disagree? Clearly articulate the risk. Executives and other leaders in the company often don’t understand the customer and the product at the level of detail you do, so they may not see the risk the way you see it. Be clear, but respectful. No executive likes surprises.
You know your space. You know your customers. You don’t have to solve all of the company’s challenges. You have to solve the ones you manage every day.