A CPO in one of our sessions shared a story that made me laugh. And cringe a little.

His company had just launched a new version of its product. Marketing did its job. Sales pitched it. Customers bought it.

Then Accounting called in a panic. They couldn’t process a single order.

The problem? Nobody had created the SKU or updated the order system.

The company had built a product customers wanted to buy but couldn’t actually pay for!

As absurd as that sounds, if you’ve been in product leadership long enough, you probably have a version of this story. Maybe it wasn’t a missing SKU. But something equally painful. A launch that couldn’t be sold. A feature nobody adopted. A product that looked great in demos but never moved the business.

Following that billing disaster, the CPO instituted a new rule: Product Management had to own the design of the entire process all the way until the cash register actually rang.

Now contrast that with a senior product director from another one of our sessions. When tasked with hitting an ambitious corporate growth target, her peers immediately defaulted to the standard product playbook: launch more features to acquire more customers.

But she knew her company’s revenue numbers cold. She knew they had a $250 million renewal base. After running the numbers, she proved that a modest 3.6% uplift in renewals would hit the same growth target with far less cost, risk, and effort than chasing new logos.

Instead of spinning up three new feature teams, she aligned the organization around protecting the economics of the customers they already had.

Same function. Same discipline. Radically different outcomes.

The difference wasn’t empowerment or better process. One product leader understood how the company made money. The other didn’t.

And that’s rapidly becoming the diving line between product leaders who get invited into strategic conversations and those who are asked for another roadmap update.

Sit in a room with product leaders long enough, and you hear a familiar chorus of frustrations:

“We’re treated like a feature factory.”
“Our roadmap changes every quarter.”
“Sales won’t sell what we built.”
“Leadership says we’re aligned, then changes direction two weeks later.”
“My PMs don’t understand why priorities keep shifting.”

These problems aren’t new. They’ve been around for decades. Yet, every time these symptoms appear, our industry prescribes the same old medicine:

“We need a better process.”
“If only people followed the roadmap.”
“We need to host a stakeholder alignment workshop.”
“If only our leadership had ‘product sense.’”

How’s that worked out for us?

After 30+ years in this field, I’m convinced that process isn’t the problem. Nor is finding better ways to get stakeholders to follow our idealistic product practices.

If your roadmap is being ignored, it’s not because you’re a bad product manager. It’s because traditional product management education has failed you

For the past fifteen years, the dominant narrative, the conferences, the podcasts, and the self-appointed “gurus” have treated product management as an advanced extension of engineering. They trained you endlessly on the mechanics of delivery: discovery, agile ceremonies, prioritization frameworks, and product operating models.

Those skills are fine for building software, but they’re not good enough for running a business. By focusing purely on execution, the Product craft has volunteered to sit on the cost center side of the company ledger. And when executives view you strictly as an extension of engineering — a cost center — you shouldn't be surprised when they decide how your capital gets spent.

Here are the four core systemic lies the product gurus taught us:

We’ve spent the last decade trying to force the C-suite to care about user journeys and technical merit. But executives don’t fund features. They fund improvements to the scoreboard. Growth. Retention. Margin. Cash flow.

Outside of the kitchen, nobody cares how the meal gets cooked. They want an exciting menu, confidence in their choice, and a great experience.

When we act like the chef who insists on explaining how sausage gets made while the restaurant owner only cares whether customers keep coming back, we shouldn’t wonder why we don’t get to set the menu.

The traditional playbook implies our responsibility ends when the code hits production. Ship the feature. Move to next. But that’s not how business works.

In reality, a company’s revenue architecture spans the entire customer relationship—from initial awareness to mutual commitment through to retention and account expansion. And Product Management needs to demonstrate ownership of this revenue engine.

Because traditional PM training never taught us to map features directly to this commercial lifecycle, product leaders pay an exhausting “translation tax” — spending half their week frantically trying to explain why technical items matter to commercial and executive teams.

This failure to see the full revenue architecture is one of the chief reasons why product teams are reduced to being feature factories.

The traditional narrative has taught PMs to complain about a lack of empowerment and to blame leadership. But empowerment is earned, not given because you have a certificate and a title. It’s earned when you can prove that you can act as a fiduciary steward of R&D capital.

The product gurus exhort you to be strategic, but they’ve taught you to be a tactical manager. Listen closely in your next product meeting. What’s the overriding question? Is it:

“What should we build next?”

Or is it:

“Which bets produce the best risk-adjusted return?”

That framing changes everything.

When you fail to package your backlog items into explicit Fundable Units and Investable Bets, your roadmap appears as just a list of costs and deliverables. And you’ll remain trapped in the cycle of reactive, feature-factory chaos.

Despite dozens of frameworks, emotional debates continue, phantom priorities persist, and zombie projects refuse to die.

Why?

Because the product gurus taught us how to prioritize work, but not how to make business decisions.

We were taught RICE scores and capacity allocation. We weren’t taught:

Those are business decisions. Investment decisions. And they need to be made before the work begins.

Without these predefined economic boundaries, prioritization defaults to political leverage rather than business logic.

As one Product VP put it in one of our training sessions:

So, how do we break out of this feature factory? Where do we start?

We start with the company’s money journey.

In plain English: how does your company actually make money?

It sounds obvious. But ask ten product leaders this question and you’ll be surprised how quickly the conversation turns to features, customers, or, at best, pricing plans.

A product leader in our training shared a painful example. His team had built a great product. Customers loved it in demos and testing. The technology worked. But it was a commercial failure.

The problem wasn’t poor discovery or market validation. The problem was more simple:

The new product flew directly in the face of the Account Managers’ compensation. They simply made more money selling more of the existing products.

So despite all the hard work, the new product never stood a chance.

This is what happens when product decisions are disconnected from the revenue engine.

What exactly do I mean by the revenue engine? It’s how money moves through your business, from awareness and acquisition all the way through onboarding, retention, and expansion.

Traditional PM training has taught you to be very good at mapping user journeys. Business operators are experts in mapping money journeys. They understand:

These aren’t just finance questions. They’re product questions. And once you see your product through this lens, everything changes.

Remember: Executive leaders and boards don’t manage products. They manage business value.

You don’t just defend your backlog based on user empathy or moving a metric. You prove that your roadmap directly maps to the financial valuation drivers the ELT cares about.

When you understand the revenue architecture, you can map where a feature lives on the customer’s revenue journey. You can articulate whether a new initiative is an acquisition driver or a retention play, making the financial rationale instantly clear to stakeholders. An initiative can literally be articulated in a one-sentence economic rationale — e.g., “If this Activation Engine initiative works, customers move past the impact threshold, unlocking $3M in expansion ARR.”

Instead of hosting agonizing meetings to convince siloed departments to support your roadmap, you show them exactly where your work and theirs plugs into the revenue model. One product leader in our training session commented how he’s now bringing this visual approach to his roadmap reviews and executive QBRs to show stakeholders exactly where an initiative fits into the whole picture.

This mapping enables product leaders to showcase how product management’s responsibilities actually span the entire commercial journey. It’s not just building a tech stack and features. It’s powering a revenue engine that dictates how the business acquires, retains, and expands its customer base.

One product executive in our training shared a story that perfectly captures why the traditional approaches to stakeholder alignment that we’ve been taught doesn’t work.

He gathered the executive team into a room to prioritize company initiatives — a classic PM exercise. The idea was simple: discuss the options, vote, and align.

It failed miserably.

The execs weren’t trying to be difficult. Quite the opposite. They openly admitted they didn’t have enough context to make good decisions outside their own domains.

And why would they? The CRO understood sales. The CFO understood finance. The CTO understood technology. Each executive was an expert in their slice of the pie.

Product Management was the only function expected to understand the whole pie.

Our product leader changed tactics. He mapped initiatives to the company’s revenue architecture. His second round of conversation was night-and-day different. Instead of debating features, everyone could see how investments affected acquisition, retention, and growth. Alignment became easier because everyone could finally see the same picture.

Another CPO asked his team to conduct a brutal audit of every single feature delivered over the previous twelve months. The findings were shocking: 75% of their shipped work had generated zero measurable business impact.

Their roadmap was littered with Orphans — initiatives that sounded great in a discovery session but had no clear ties to corporate targets.

He shifted his teams to reframe every initiative as a Fundable Unit mapped to the corporate scoreboard. If it couldn’t be mapped, it was marked as a an Orphan and discarded.

This allowed them to reclaim not just massive amounts of engineering capacity, but significant R&D investment and redirect it toward high-leverage business bets.

Sometimes the fastest way to create value isn’t building something new. It’s having the discipline to kill work that never should have started.

One product leader shared this story.

His company had historically grown through acquisition. Naturally, the roadmap had reflected that strategy — product work focused on winning new customers. Then the CEO changed the strategy. The company would now prioritize retention and expansion.

Overnight, the economics of the business had changed. Recognizing this shift, the product leader quickly reoriented the roadmap toward retention and expansion initiatives.

He warned the executive team that the Sales team might push back on the reduced volume of acquisition features. The CEO and CFO had no hesitation supporting this decision. Why? Because the roadmap was fully aligned with how the company intended to make money.

The good news is that this isn’t some mystical skill reserved for people with MBAs or finance junkies. It’s a practical muscle. And like any muscle, it can be built and toned.

Here are six ways to start building it this week:

No need to take a finance course. Start by searching for terms like “Net Recurring Revenue,” “gross margin,” and “EBITDA”. There are a ton of great resources online that will explain it like you’re a 5th grader. (That’s how I learned.)

You don’t have to parse the financial models alone. Partner with your VP of Finance or FP&A team. Ask them to help you translate your product outcomes into language that immediately makes sense to the CFO. Use this partnership to learn the company’s specific mechanics regarding pull-through revenue.

Sit down with sales leadership and read their compensation structures. If you build a phenomenal product that requires sales cycles that conflict with how an account executive retires their quarterly quota, your product will be completely ignored

Work hand-in-hand with Sales to establish booking projections based on actual market willingness to pay. Ensure you explicitly understand the vital accounting difference between a booking (a signed contract) and revenue recognition (when the cash actually hits the bank over time) to build a revenue waterfall that can withstand scrutiny. (I have an entire article on these terms here.)

Don’t let your PMs sit entirely isolated behind Jira boards. Ask for them to join customer Quarterly Business Reviews (QBRs). This allows product teams to hear directly about the pain of revenue churn and the realities of customer retention straight from the clients.

When presenting tough roadmap choices to the ELT, always present three clear investment scenarios. Document the holistic cost of each path, including development effort, go-to-market costs, and the clear opportunity costs of what must stop as a result and the delay of not pursuing the opportunity.

Most importantly, force the room to explicitly accept both the upside and the downside of an investment option before a single line of code is written. Securing agreement on negative trade-offs upfront is the only way to stop stakeholders from changing the strategy when things get difficult mid-cycle.

Over the past year, Mike Smart and I have been working with product leaders to help them connect product strategy, roadmaps, and investments directly to business outcomes.

That’s why we created the Business Fluency Masterclass for Product Leaders, a live cohort-based workshop designed for Directors, VPs, and Heads of Product.

If today’s article resonated with you, take a look:

The next cohort begins in July and space is limited.

Product teams map user journeys.

Business leaders map money journeys.

The future belongs to leaders who can do both.

That’s it for today.

Have a joyful week, and, if you can, make it joyful for someone else too.

cheers,
shardul

Shardul Mehta
I ❤️ product managers.

​Follow me on LinkedIn