Your C-suite does not care about your product framework.

I know that sounds harsh.

But I learned it the hard way.

The first time I walked into an exec room, I came prepared to talk all about the things I thought mattered — the things the product experts told me mattered:

Discovery cycles. Features. Prioritization. Delivery velocity.

I knew my stuff.

The execs listened quietly. Then they said something vaguely polite like, “Thanks for all the work.” And sent me on my way.

Then they made all the decisions about my roadmap without me in the room.

This happened again. And again. And again.

For a long time, I thought the answer was to get better at product management.

Maybe I needed a better framework. More data. More “product sense.”

I was wrong.

The problem wasn’t my product skills. It was my business skills.

I was speaking product language to people who were thinking about the business. They were thinking about revenue, growth, margins, retention, and value. I was talking about discovery, features, and delivery.

And when you keep talking about the work while everyone else is talking about the business, it’s hard to be seen as a business leader.

You become the person who manages the roadmap. Who keeps the team busy. Who reports on delivery.

In other words, an operator. A mouthpiece for engineering.

Not a strategic leader.

That was the glass ceiling I had to break.

And I eventually learned something that changed how I thought about product leadership:

If you want a real seat at the table, you have to stop acting like a roadmap manager and start acting like a portfolio manager.

That means learning to connect product decisions to financial outcomes. It means moving beyond product speak. It means becoming fluent in the language of the business.

I recently saw a great example of what this looks like in practice.

Her name is Linda.

Linda has more than 12 years of hands-on product management experience. Smart and ambitious, she successfully climbed into a VP PM role.

Like many top-tier product leaders (especially outside of Silicon Valley), she came from a non-traditional background. She started her career with a degree in health fitness, spent five years as a personal trainer, transitioned into structured settlements, and fought her way into healthcare IT, eventually making the transition into product management.

She never went to business school or learned finance. So when terms like EBITDA, Gross Retention Rate, and Net Retention Rate started flying around executive meetings, she was left trying to decode them on her own with late-night Google searches.

Be honest: You’ve probably done the same.

Google can tell you what EBITDA or NRR means. But knowing the definition is not the same as knowing what those numbers mean for your product, your roadmap, or your next product proposal.

That’s where Linda had a gap.

Despite over 12 years of product experience, her lack of formal commercial training created a persistent utility gap in her communication with the C-suite.

She knew Product. But she didn’t have the business language to connect her product work to the things executives and boards care about most:

Revenue.
Profit.
Growth.
Value.

This is the biggest gap in product management: Business Fluency. (Not AI.)

When product people aren’t sure how to talk about the business, they tend to retreat into the things they know best:

Features.
Roadmaps.
User stories.
Dates.
Velocity.
Maybe even OKRs.

It’s comfortable territory.

But the problem is:

Traditional product language often sounds like this:

Feature delivery
Roadmap updates
Prioritization frameworks
Backlog management
Feature and project trade-offs
Velocity

Those things may matter at the execution level. But they mean absolutely nothing at the strategic level — i.e., at the ELT level.

The ELT is thinking about:

ARR and NRR
Margin and EBITDA
Go-to-market
Category dominance
Return profiles
Valuation

This is where product leaders get stuck.

Over the last 15 years, product management has become intimately tied to engineering. And engineering is often seen by the business as its biggest cost center.

If you only talk about what you’re building and how you’re building it, you’re reinforcing that view.

You become the person who “manages the work.” Who “keeps engineering busy.” Who reports on delivery. Who “acts as the glue” (whatever that means).

That’s not the role most of us want.

To move from engineering support to business leadership, you need to connect product decisions to the numbers and goals that matter to the people who own the P&L.

In other words, you need to move from the tactical roadmap to the executive scoreboard.

Linda got a chance to put this into practice. She was invited to present at her company’s mid-year executive leadership summit in Chicago.

Normally, Linda would have presented a standard roadmap focusing on features, discovery milestones, plans, and dates. By her own admission, she knew this would miss the mark.

The ELT needed to understand how the product work connected to the company’s larger strategy.

So, with three separate executive presentations ahead of her, including her product roadmap, Linda reframed the entire story.

She moved away from the traditional PM frameworks and feature-heavy roadmaps. Instead, she focused on investable bets tied directly to the company scoreboard.

She used three core Business Fluency frameworks:

Instead of building a roadmap around what they wanted to ship or what customers were requesting in isolation, she mapped every initiative directly to the company’s scoreboard of core business targets.

That on shift changed the question changed from:

“What should we build?”

to:

“Which business goal are we trying to move?”

That’s a very different conversation.

Linda stopped pitching individual features. Instead, she translated each one into a Fundable Unit — a clear business opportunity that showed the expected commercial impact.

This one change shifted her entire presentation from selling features to selling business opportunities.

Linda also recognized something every product leader eventually has to face:

A company cannot fund 50 different initiatives.

There’s only so much money, time, and talent to go around.

So instead of scoring or force-ranking a long list of things the team wanted to do, she presented Investable Bets.

Each bet was a capital investment option with:

Now the roadmap was transformed from a to-do list into a portfolio of business bets.

Before stepping into the room, Linda previewed the presentation with her boss, the CPO. His reaction was immediate:

Then she presented to the ELT.

And it was a home run. (She hit a six, if, like me, you’re a cricket fan.)

Instead of getting bogged down in debates over dates and scope, the executives were nodding along.

There was zero lost in translation because Linda was speaking fluent commercial business language.

She also achieved several important results:

The win wasn’t just in the meeting. There was a powerful halo effect in how the company viewed Linda and her product function. Her new level of influence turned her into a trailblazer at the company, and she’s now leading the charge for FY27 strategic planning.

And she did this with a very lean team: one product manager and a couple of product owners, inside a broader product organization of 30 people.

Yet, that small team now has outsized strategic influence across flagship product lines.

That’s the power of Business Fluency.

It’s not about having the biggest team in the room.
It’s not about having the perfect product process.
It’s about helping the business make better decisions.

The team also took the new Business Fluency framework straight into FY27 planning. Every major initiative now starts with a clear business thesis before a single line of code gets prioritized.

That’s a fundamental shift.

Instead of starting with:

“What should we build?”

They start with:

“What business result are we trying to create, and why is this worth funding?”

And there was one more important outcome. By learning to work with executive metrics, Linda gained something that doesn’t show up on a spreadsheet:

Confidence.

She gained the confidence and permission to advocate for her portfolio. She no longer felt like she was guessing her way through executive conversations. She knew what she was talking about. And she knew why it mattered.

Linda’s story is a blueprint for product leaders. The path to executive influence is not paved with being better at product building.

It’s paved with better Business Fluency.

The gal isn’t to stop being good at product. It’s to add the missing layer that helps you move from product expertise to business influencer. To move from being a glorified support for engineering, a roadmap manager, to helping lead the business.

That shift is about more than vocabulary. It’s a mindset shift.

Linda captured this well during her transition:

That last part matters:

How is Product making an impact?

That’s the question you need to be ready to answer.

Not just with features or delivery dates.

But with business results.

If you’re still trying to develop your “product sense,” waiting for executives to develop a “product mindset,” or dreaming of the day when your organization will become “product-led,” you’ll be waiting forever.

There’s another path.

Stop defending features. Start driving business value.

And so does your impact.

As Linda discovered, when you speak the language of business, you stop feeling out of control and start helping to drive the business forward!

Most product leaders are taught how to build products.

Very few are taught how to think like business leaders.

That’s why so many roadmaps optimize for outputs instead of outcomes, and why so many product teams struggle to explain how their work will actually create any real value.

The Business Fluency for Product Leaders Masterclass is designed to close that gap.

Over two live days, Mike Smart and I will help you connect your product work to your company scoreboard, so you can move from managing engineering delivery to helping drive the business forward.

If that sounds like the next step in your growth as a product leader, we’d love to have you join us.

The next cohort is in October, just in time for the FY27 budget season, and seats are limited. Grab your now.

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