McKinsey's research into product operating models found that organizations with mature product practices see 60% higher returns to shareholders than peers. The same research, however, identified the largest performance gap between top and bottom performers in backlog prioritization, funding, and how Product connects with commercial reality. That gap is where the empowerment narrative breaks down.

Most product organizations today run a version of what Marty Cagan described in Empowered: cross-functional squads, dedicated PMs, designers, and engineers, often with OKRs pinned to a Notion page. Cagan's argument was that teams given real problems, staffed with competent people, and held accountable for outcomes would outperform teams handed feature lists.

What most companies took from it: give teams autonomy, get out of the way, good things will follow. The accountability half disappeared.

What does the autonomy gap look like in practice?

Walk into a mid-stage SaaS company or an enterprise product org that has run a "transformation" recently and the pattern repeats:

• Squads spend weeks debating what to work on
• OKRs measure activity (experiments run, features shipped) rather than business impact
• Sprint reviews skip revenue, retention, and margin
• When executives ask what a team is doing, the answer is process, not business case

PMs feel squeezed between teams that want to explore interesting problems and stakeholders who want delivery dates. Nobody owns the connection between what gets built and what the business needs. This is empowerment without accountability — the dominant operating model in a surprising number of product organizations today.

Why does business fluency change decision rights?

Most PMs understand the product, the user, and the technical constraints. Few can explain how their team's work affects gross margin, how pricing models create or constrain growth, or why a CFO cares about the ratio of expansion revenue to new logo acquisition. Rich Mironov has documented this for years: PMs talk features, executives think money. When the two languages don't translate, product teams lose credibility regardless of how strong the discovery work is.

This language gap explains why so many "empowered" teams find their autonomy clawed back. Leadership can't see the connection between the team's work and the business. The rational executive response is to get closer: more check-ins, more roadmap commitments, more status updates. PMs read this as micromanagement. It is actually a trust problem product has the power to solve.

Itamar Gilad's Confidence Meter framework makes the dynamic visible. Teams score each idea from "self-conviction" to "validated by experiments." When product teams present ideas to leadership with real confidence scores attached, the conversation shifts from negotiating for permission to negotiating for resources to go after a specific outcome.

How does product earn trust rather than demand it?

Compare two presentations of the same discovery work.

Version A: "We validated a customer pain point around onboarding. We'd like to pursue a solution." Leadership nods, then asks when the Sales-requested integration ships.

Version B: "Enterprise churn is 18% higher for customers who don't complete onboarding in the first 14 days. We found three friction points. Resolving the top two could move 14-day completion from 62% to 80%, roughly $1.2M in retained ARR over four quarters. Here's what we need to test in six weeks."

Same discovery. Different framing. The second team gets resources, because they spoke in the language the organization is accountable for.

What infrastructure makes outcome accountability work at scale?

McKinsey's research on more than 1,700 product teams found that "ways of working" — the practices connecting team activity to strategic goals — is the single most important driver of business performance. Structure, talent, and technology all matter, but the practices matter more.

The choice of tooling becomes consequential here. When teams manage work in delivery tools like Jira, the organizing unit is the ticket. The ticket carries no strategic context; it doesn't know why it exists in relation to a business outcome. If that artifact represents the team's work, decision-making anchors in output.

Outcome-based roadmapping organizes work around the business outcomes being pursued rather than the features being built. The Now-Next-Later format sorts work by time horizon and ties each initiative to a strategic goal, without committing to fixed dates that become promises the moment a Gantt chart enters the room. A strategic hub connecting goals, initiatives, and experiments sits upstream of delivery tools like Jira, Linear, and Shortcut.

What happens when product signs up for outcomes?

Shreyas Doshi's distinction between optics, execution, and impact is useful here. Many teams optimize at the optics level — running discovery, presenting at sprint reviews, maintaining a roadmap. Fewer operate at the execution level, shipping well-crafted work consistently. Fewer still operate at the impact level, where work measurably moves a business outcome.

When outcomes are clear, coaching has a focal point. A product leader can ask: how does what you learned this week change your approach to hitting this number? That is a development conversation, not a status check.

Product analytics tools (Amplitude, Mixpanel) tell you what is happening in the product. The strategic layer, where outcomes and goals live, tells you why it matters and what to do about it. When the two layers connect, accountability becomes a shared practice rather than a top-down demand.

Gilad's evidence-guided approach offers a practical model: teams assess confidence behind each idea, run progressively more rigorous tests as investment increases, and adjust based on what the evidence shows. When a team proposes a hypothesis, tests it, measures the result, and adjusts, the conversation shifts from "did you hit the target?" to "what did you learn, and what's the next best bet?"

What changes for product leadership?

Jeff Gothelf and Josh Seiden coined "outcome-focused management" to describe the shift: stop measuring success by what gets shipped, start measuring it by the change in customer behavior shipping produces. Most organizations never make that shift. It requires the product function to understand the business well enough to own those outcomes, and the rest of the organization to trust that product can deliver on them. Most companies skipped that part.

The product teams that will matter most over the next decade are the ones that stop asking for empowerment and start asking for accountability. They will sign up for outcomes, build the measurement infrastructure to track them, communicate in the language of the business, and earn trust by delivering results that matter. Empowerment will follow, because it has to. You cannot hold a team accountable for an outcome and then refuse to let them figure out how to get there.