The Four Leadership Taxes You Pay

How I Shift From Reactive Execution to Proactive Product Leadership

If you read the standard product management books, product leadership sounds like conducting a perfectly orchestrated symphony. But if you’ve actually been in the trenches, you know the reality: it’s loud, it’s messy, and most days, it feels like you’re taking fire from all directions.

Over my years in product leadership, I’ve realized that surviving—and ultimately transforming—an organization requires more than just knowing the right frameworks. It requires a Product Leadership Operating System: a clear compass to navigate the competing dynamics and perspectives that define our role.

In this article I outline the core perspectives you need to master, if you want to move your team from a reactive feature factory to a proactive powerhouse.

1. The View Upwards: The CEO, the Board, and the Pressure to Deliver

In many companies today, the spotlight is glaringly focused on EBITDA, revenue generation, and efficiency. CEOs are under immense pressure to stand in front of the Board and look both visionary and capable of ruthless execution.

This leads to a massive focus on Product because our impact often lags by weeks or months. Meanwhile, Sales and Marketing are waving short-term wins and immediate proof points. Customer Success is actively scaling and driving efficiency using AI. If your Growth teams report to Marketing instead of Product, you have even fewer data points to prove your contribution to the bottom line. I call this the product credibility gap (read more here).

Master Product Leadership in the Age of AI is the core of my upcoming course, The Product Leader’s OS. I’ll show you how to turn ‘theory’ into ‘commercial proof.’

Join my Free Lightning Session on Maven on April 1st at 5pm CET. Access here.

Imagine this setup in the boardroom: The sales leader lists revenue by signed contracts and prospects, the CMO shares how the 15% uplift from campaigns results in immediate revenue and celebrates at the same time quick wins from their growth teams.

And then, there’s you - the Chief Product Officer. You present visions, maybe prototypes, and eventually OKRs. You walk through roadmaps and celebrate releases. You tell future-oriented stories that feel distant next to the other leaders’ presentations.

This dynamic creates a subtle trap, especially in organizations where Product isn’t yet at the core. It is agonizingly hard to build trust when your value shows up as “theory” or “long-term bets,” while everyone else is showing “short-term wins.” Now add sprinkles of re-platforming, tech debt, and harmonization to the equation, and it’s guaranteed you lost your C-Level peers.

Many leaders pour their energy into transforming the org toward “modern product” practices, only to face (often unspoken) skepticism: “Where’s the proof?”

You have to learn to balance these priorities. You cannot just be a product purist; you have to become fiercely commercial.

2. The View Sideways: The CPO & CTO Dynamic

The relationship between the CTO and CPO is the heartbeat of the product and engineering org. If you don’t have the hard, uncomfortable conversations behind closed doors, you will communicate mixed signals to your respective teams. This trickles down, creating massive friction and killing efficiency.

The classic friction points:

• Undefined roles and accountabilities.

• The eternal battle: Tech Debt vs. Innovation.

• The toxic habit of “protecting my own people.”

• Translating a product vision into a viable tech architecture.

The balance between “building a scalable platform” and “just shipping it to learn” is incredibly fragile. Ultimately, as Product Leaders, we are the ones who have to explain to the CEO and the Board why things take so long. We speak the language of business, while the CTO speaks the language of security, compliance, and migrations. You have to align, or you both lose.

Investing in the relationship will pay off in all directions.

• If you’re sitting in different meetings, speaking the same language, people will bypass neither of you to get their feature requests on your team’s table.

• Communicating with your team feels authentic and builds trust if it’s clear that the two of you are best work buddies.

• Your C-Level will question your decisions less often because it feels like you balance technical excellence and innovation from within your team.

3. The View Downwards: From Therapy to Coaching

One common dysfunction in a product org is that PMs feel totally lost. They lack a clear strategy, get bombarded with requests from all sides, and then consume podcasts and books about “perfect” product companies, only to feel like backlog administrators. Desperate to shield their engineers from shifting priorities, they struggle to push back and at the same time they make the leader feel like it’s in their hands to fix it.

This often results in 1:1s turning into therapy hours, not coaching sessions. And amidst all this firefighting, you have zero time to actually work on the organization, not even talking about finding time to work on strategy and vision.

One first step to make a change in this area is to take the time to evaluate your PMs. Who is just complaining, and who brings solutions? Who is obsessed with process, and who has a natural intuition for people? Who is ready for leadership, and who can act as a change agent?

As a next step, shift the dynamic: Move the conversations strictly from psychotherapy back to coaching. Know your team’s strengths, delegate accordingly, and turn transformation into a team effort.

But there is more that you can do.

If you feel like your entire org is drained, it’s a warning sign you can’t ignore. The noise is too loud, the stress has become unmanageable. First aid: be the Sh**-Umbrella: Protect your team by absorbing the chaos from everywhere so your team can focus.Tell them that you step into that space now and that they can pull you into any discussion and any topic, and that this is not escalation, but protection.

If you don’t talk about why you step in, you might either be labeled a micromanager or people will try to solve everything themselves to not seem to be weak in front of you and risk a promotion.

Telling them why you do it, how it helps, but also that this is not a permanent way of working, will help you to fully understand what’s going on, where the noise is coming from, and how to streamline efforts again so your Product Org can focus on delivering value again.

4. The View Forward: Vision, Strategy, and Measurement

When you are caught in the crossfire of political alignments, stakeholder management, and organizational design, it is terrifyingly easy to forget your primary mandate: building a valuable product supporting a sustainable business.

Your CEO wants to see a visionary. Your PMs need a North Star so they can confidently say “no” to the noise. If you don’t define the playground, your stakeholders will define it for you—and that is when the chaos takes over.

To make your Product Operating System actually drive transformation, you need to anchor it in three things:

• The Vision : This isn’t a fluffy statement on a slide deck. Your product vision needs to be a compelling, vivid picture of the future that excites the Board and gives your engineers a reason to care. It is the ultimate antidote to the “we are just implementing requirements” mindset you see in frustrated PMs.

• The Strategy: Strategy is sacrifice. It is the painful, deliberate act of choosing what you will not do. How do we win in this market? Which customer segments are we ignoring? If your strategy doesn’t make someone in Sales or Marketing slightly uncomfortable because their pet project got cut, it is not a strategy—it is a wishlist.

• The Measurement: A vision without metrics is just a hallucination. Remember how we talked about the pressure to be commercial? This is where you prove it. You need a rigorous framework (like OKRs or KPIs) that connects lagging commercial metrics (Revenue, NRR, CAC) with the leading product indicators your teams can actually influence (Activation rate, Time to Value, Feature Adoption).

When you have a crystal-clear vision, a ruthless strategy, and hard metrics, you no longer have to defend your roadmap feature by feature. You elevate the conversation from “When will this button be ready?” to “Are we moving the right commercial levers?”

5. The View on the Product & the Org: Architecting for Impact

As I mentioned earlier: “CEOs are under immense pressure to stand in front of the Board and look both visionary and capable of ruthless execution.” Guess what? That exact same expectation rolls right downhill to you. You are required to be a visionary leader leveraging the latest technology, a coach upskilling your PMs and designers, an analyst diving deep into data to find the next big growth lever, and a diplomat managing upwards. The cognitive load is massive.

You cannot hustle or “hero-PM” your way out of this. The one and only way to make it work is to constantly review and optimize your product organization’s setup. You have to stop just managing the work and start architecting the system.

A true Product Leadership Operating System requires you to look critically at your organizational design across three non-negotiable pillars:

People

It’s not just about filling seats; it’s about having the right people, with the right skills and the right motivation, in the exact right roles.

On top of that it is also important to review if you have all roles reporting to you you need to build great products and create the impact for the customer and the business you aim to achieve. A few roles usually missing:

• Product Marketing (to bridge the gap to GTM)

• Growth (to drive acquisition and retention)

• Product Operations (to optimize the system itself)

• Analytics & Data (knowing exactly when you need Data Engineers vs. Data Scientists)

Processes

• Are your processes serving the team, or slowing them down? A healthy operating system requires clear accountabilities and a ruthless elimination of friction. Your processes need to be documented but lightweight, efficient, and critically: measurable. If a process doesn’t help you make better decisions or ship faster, it’s just bureaucracy.

Performance

• This is the ultimate output of your system. Are you actually working with (mostly) high-performing teams? Are you drastically reducing your Time to Value? If your org setup isn’t directly resulting in faster, higher-quality commercial impact, your system is failing.

The Ultimate Stress Test: Shadow Engineering

Here is where your People, Process, and Performance setup gets tested in the real world: How do you handle “shadow engineering”?

What happens when Marketing or Sales gets tired of waiting for your roadmap, decides your Time to Value is too slow, and starts hiring their own developers to build on your platform? If your system is weak, this turns into a fragmented, chaotic mess of technical debt. But if you have a rock-solid product vision, efficient processes, and strong organizational guardrails, you can actually channel that commercial pressure into tangible value.

6. The Psychological Reality: Self-Confidence & Your Circle of Influence

Let’s talk about the part of product leadership no one puts in the job description: it is incredibly lonely.

When you are a PM, you can vent to your peers. When you step into Product Leadership, that luxury vanishes. You can’t take your insecurities or existential product questions to your CEO—they hired you to be the one with the answers. You can’t complain to your executive peers, and you certainly cannot bleed your doubts onto your direct reports.

You have to figure it out mostly by yourself. Yes, executive coaching, external communities, and reading help immensely, but at the end of the day, the burden of leadership remains a solitary endeavor.

Because of this isolation, you have to actively and intentionally work on your self-confidence. You must project conviction when you speak up in the boardroom, in executive meetings, and in front of your team. Why? Because the corporate ecosystem is pragmatic and sometimes ruthless. If your peers or direct reports sense chronic hesitation—if they don’t trust your direction or perceive you as weak—they won’t just ignore you. Some of them will bypass you, step over your authority, and actively maneuver to take your seat.

Earning Your Influence

This brings us to your circle of influence, which is your ultimate shield and lever.

The biggest mistake a new Product Leader can make is walking through the door on day one and immediately preaching about “empowerment,” “alignment,” and “continuous discovery.” If you haven’t delivered anything yet, your circle of influence is zero.

Relationship building is everything, and it starts with humility and commercial respect. Go in with the assumption that Sales and Marketing actually know what they are doing.

How do you build the trust required to secure your position? Deliver first, transform later. Sometimes you have to quietly and “secretly” fix the underlying processes while publicly delivering hard, commercial results upward. That is how you prove your competence, build unshakable confidence, and buy yourself the political capital to make the massive, systemic changes the organization actually needs.

Bringing It All Together: Why It’s an Operating System, Not a Checklist

Sustainable transformation doesn’t happen by accident, and it certainly doesn’t happen by treating these perspectives in isolation. I call this a Product Leadership Operating System for a very specific reason: the components are entirely interdependent. You cannot run a highly functional organization if one of your core background processes keeps crashing.

If you perfectly manage the view upwards (aligning with the CEO and Board) but your relationship sideways (with your CTO) is toxic, you will promise the world but ship nothing. If you have a brilliant, visionary strategy (the view forward) but neglect your organizational design (people and process), your strategy will slowly die in a bloated backlog. And if you have all the perfect frameworks in the world but lack the self-confidence to hold your ground (the inward view), someone else in the C-suite will inevitably take the wheel.

One cannot survive without the other.

Diagnosing Your Operating System

So, how healthy is your current setup? Take a hard, honest look at your day-to-day reality and assess where your system is showing signs of failure:

• The Upward Diagnostic: Are you constantly defending the existence and ROI of your product team, or does the CEO treat you as a strategic partner to drive revenue?

• The Downward Diagnostic: Are your 1:1s with PMs focused on strategic coaching and growth, or are they still exhausting therapy sessions about shifting requirements and burnout?

• The Sideways Diagnostic: When things get tense, do you and your CTO argue through your respective teams, or do you hash it out behind closed doors and present a united front?

• The Forward Diagnostic: Can every person in your product org clearly articulate exactly how their current sprint impacts the company’s commercial goals?

• The Inward Diagnostic: When a strong-willed executive (like a CRO or CMO) challenges your roadmap, do you fold under the pressure, or do you hold your ground with conviction and commercial data?

Wherever you winced while reading those questions—that is the bug in your operating system. That is where you are leaking trust, efficiency, or influence. Fix that specific mechanism first before you try to scale further.

Mastering this delicate, interconnected balance isn’t easy, and it certainly isn’t always fun. But it is exactly what separates good PMs from great, resilient Product Leaders.

---

This is the work I do with CPOs and VPs of Product.

If your 1:1s have started to feel more like therapy than leadership, that is usually a signal that one of the four taxes is running quietly in the background. The assessment takes five minutes and tells you which one.

---

If you want to work through a specific situation with someone who tells you the truth, a Power Hour is the right next step. (Paid offering)

---

This article is an addition to my six-part series on the Leadership Taxes that drain product leaders silently over time.

If you missed the earlier articles you can find them here:

• Part One: My Product Operating Model

• Part Two: The Therapy Tax

• Part Three: The Trust Tax

• Part Four: The Alignment Tax

• Part Five: The Confidence Tax

• Part Six: How the Taxes show up in your Roadmap