
I hear it constantly: “Product needs to drive business results.”
And I agree. That’s where we should be headed.
But the reality inside most organizations looks very different.
The product leaders I talk to every week aren’t sitting in the C-suite shaping strategy. They’re five layers down. Strategy gets handed to them. Roadmaps get handed to them. Expectations get handed to them.
And then they’re told to own outcomes.
This role is harder than people want to admit.
You’re not quite in executive leadership. You’re not fully in engineering either. You sit in the middle, touching everything, accountable for everything… but not always empowered to change the things that matter most.
At the same time, the expectations keep increasing:
But here’s the tension no one says out loud:
You’re often not even in the room where those outcomes are defined.
And the data backs this up. According to Atlassian’s State of Product 2026 report, 85% of product professionals say they’re involved in strategy, yet nearly half don’t actually have time to do real strategic work. They’re buried in meetings, stakeholder requests, and reactive execution.
So yes, product is “more strategic.”
But in practice, most teams are still operating in controlled environments where decisions are made upstream.
That disconnect is what creates the frustration.
You’re being told to think like a business leader…
Without access to business context.
You’re expected to drive outcomes…
Without control over the strategy behind them.
And because roles are expanding, product is now overlapping with sales, marketing, and customer success. As Amy Mitchell explains, product managers are increasingly expected to translate business outcomes without actually defining them.
You absorb the ambiguity, but you don’t own the source of it.
That’s the job today.
So what happens?
A lot of product leaders quietly make a choice.
They stay in their lane.
They execute. They stay busy. They deliver what’s asked.
And honestly, I get it.
It’s the easier path.
But most product leaders I know aren’t wired that way. They see what’s broken. They want to fix it. They want to drive real impact.
So the question becomes:
How do you actually do that from where you are?
Here’s the mistake I see over and over.
Product leaders try to jump straight to business outcomes.
Revenue. Growth. ROI.
But they don’t control those directly.
So they get stuck.
The better approach is simpler and much more practical:
Start with what you can actually control.
I think about this in three clear layers. And when you get this right, something interesting happens. You naturally build your way into business impact.
This is the foundation. And it’s often overlooked.
Are we doing what we said we’d do?
Are we finishing work cleanly?
Are we staying focused, or constantly drifting?
If a plan is handed to you, you still control how effectively it gets executed.
Teams that finish what they start, hit timelines, and reduce thrash stand out quickly.
Reliability is credibility.
This is where you start shaping impact, even if you don’t own the top-level strategy.
Are you:
This is what strong product management looks like in practice.
Even in constrained environments, you can model what good decision-making looks like.
And over time, that starts to influence the system.
If you want to go deeper on this shift, I wrote more about it here: From Velocity to Value.
Now you layer in measurable signals.
Engagement. Retention. Usage. Behavior.
These are metrics you fully control.
You don’t need direct access to revenue to start proving value.
And this is where things start to click.
Because when you combine:
You now have a story.
A measurable one.
Here’s where it gets interesting.
When you consistently measure effort, output, and product behavior, you can start connecting dots.
You can show:
Now it starts sounding different.
Now it starts sounding like business language.
And once you connect that with inputs from other teams like sales, marketing, and customer success…
You start building something powerful.
A real cross-functional scorecard.
This is exactly the gap most organizations struggle with today, and why outcome tracking is still so inconsistent. I break that down more here: Are We Really Tracking Outcomes?.
When you do this well:
And that’s when things change.
That’s when you get pulled into strategic conversations.
Not because you asked for a seat.
But because you earned it.
There’s something important to understand here.
This isn’t easy anywhere.
I’ve spoken to around a thousand product leaders over the last couple of years.
I have yet to see an organization where this is fully clean and working end-to-end.
It’s messy everywhere.
Even with all the focus on AI, faster execution, and smarter tooling, most teams are still struggling with the fundamentals. As highlighted in Product School’s 2026 trends, the shift toward outcome-based work is happening—but the infrastructure and clarity to support it are still catching up.
So if this feels hard, it’s because it is.
Product leadership is inherently messy.
But that doesn’t mean you’re stuck.
If there’s one thing to take away, it’s this:
Stop waiting for permission to drive business outcomes.
You won’t get it upfront.
Instead:
Then connect those dots outward.
That’s how you move from output to impact.
That’s how you build credibility.
And that’s how you eventually step into the role everyone is already expecting you to play.
At Iteright, this is exactly the pattern we help teams build—starting from execution and working up to outcome visibility across the business. Not as theory, but as an operating system.
Everyone talks about owning outcomes like it’s a switch you flip.
It’s not.
It’s a progression.
And it starts a lot lower than people think.
So the real question is:
What are you doing today with the things you actually control?
Because that’s where this whole shift begins.