The Alignment Tax: What a Real C-Level Relationship Looks Like
And how it sets the temperature for the entire organization.
By Stephanie Leue | Inside Product Org
The relationship between a CPO and a CTO (or CRO / CMO / CSO / CXO) sets the temperature for the entire organization.
Not the strategy. Not the roadmap. Not the org design.
The relationship.
When it works, everything downstream moves faster. Teams get clear signals. Decisions stick. Conflict gets resolved in the right room instead of spreading through the org like a slow fire.
When it doesn’t work — even when it looks like it does from the outside — everything slows down. Teams pick up the mixed signals. They protect themselves. They stop taking risks. And six months later you look up and realize nothing has really moved, and you’re not entirely sure why.
I’ve lived both versions.
In two different companies, with two different CTOs. And the contrast between them taught me more about leadership than almost anything else in my career.
The Real One: A Crisis That Built Something Lasting
The first company was under pressure. We had lost revenue and needed to build a new product - fast.
The CTO wanted to do it properly. And I understood why. Years of accumulated technical debt, outdated components, systems that had been patched together rather than built with intention. His instinct was: if we’re touching this, we do it right. Build it scalable. Fix what’s broken while we’re in there. Touch it once and never again.
I knew we couldn’t afford to build for months. But I didn’t have enough technical depth to make a solid counter-argument. So instead of pushing back clearly, I let things drift. We were both moving, but nothing was actually moving. The teams were doing what I can only describe as fake work - activity without progress, effort without direction.
And the pressure kept building.
PMs complained they were too slow. Designers complained. Engineers complained that PMs weren’t giving clear direction. PMs complained that engineers weren’t moving fast enough. Everyone was bringing their frustrations to their respective 1:1s - mine and the CTO’s - and we were both listening, both nodding, both quietly protecting our own people. (so we both paid the Therapy Tax I wrote about in Part Two of this series)
That was the problem. We had made it a team problem when it was actually our problem.
At some point we both recognized it. I don’t remember exactly who said it first, but the conversation went something like: this isn’t about the engineers or the PMs. This is about us. The mixed signals we’re sending. The misalignment we haven’t addressed. The decisions we haven’t made together.
What followed were some of the most intense, honest conversations I’ve had in my career. Behind closed doors. No audience. No performance. Just two leaders who both cared about the company, the product, and the people - and who finally stopped dancing around the real disagreement.
We figured it out. We aligned on an approach. And we walked out of those conversations with one clear message between us.
The team unblocked almost immediately. The product launched. It became a success.
But the real outcome wasn’t the product. It was what we built between us. After that crisis, every future conflict was easier. We knew we could stay connected even in hard moments. We knew we both wanted the same thing. The trust we built in that room lasted well beyond our time at that company.
We’re still in touch today, even though we’ve both moved on.
That’s what real alignment feels like. It’s not the absence of conflict. It’s the ability to go through conflict and come out stronger on the other side.
The Fake One: Polite, Slow, and Damaging
The second story looked nothing like a conflict. That was the problem.
We had restructured the team and introduced more modern roles. A previous PO role was replaced by a newly hired PM. Design moved closer into the product trio. It looked like progress - and in some ways it was.
But the team had difficult history. For over a year they had tried to build a product that never really landed. Resource constraints, shifting priorities, unclear direction. The wounds were still there, even after the structure changed. Even after they finally launched - with delay, but they launched.
The team was afraid. They had succeeded once, but they didn’t trust that it would last. The PM wanted to push forward with new ideas. The engineers wanted to build for stability, to protect what they had, to not risk friction with the commercial side of the business. Everyone was being careful. Nobody was being honest about why.
And underneath it all, the CTO and I were doing exactly the same thing.
When we introduced the new structure, I felt we were aligned. We had talked it through. We had agreed. But looking back, I think the CTO never fully bought into the direction. Whether he disagreed but didn’t want to say it, or whether he just wasn’t willing to have the hard conversation - I genuinely don’t know. What I do know is that over time, the alignment we thought we had started to show cracks.
Not in anything he said directly. In the spaces between what he said. In the mixed signals his team was picking up. In the mood between us that shifted gradually from open to guarded. In the conversations that got shorter and less candid. In the dissatisfaction that was always there but never quite named.
And here’s the most uncomfortable part: I didn’t name it either.
We both saw it. We both felt it. And we both kept trying to quietly manage around it instead of addressing it directly. The same way the team was managing around their fear of failure. The same pattern, two levels up.
It never got resolved. Not really. We got through it in the way you get through things when you’re both too busy and too polite to have the conversation that actually needs to happen. Functional on the surface. Hollow underneath.
The Alignment Tax compounds silently. You don’t always feel it in the moment. You feel it six months later when you realize how little has actually changed.
What the Difference Actually Comes Down To
Looking at these two experiences side by side, the difference isn’t personality. It isn’t chemistry. It isn’t even whether the CTO was good at their job — both were.
The difference is what happened when things got hard.
In the first company, we leaned into the discomfort. We had the conversation we didn’t want to have. We were honest about the misalignment instead of managing around it. And that honesty - however uncomfortable - created something real between us.
In the second company, we avoided it. We stayed polite. We protected our teams instead of addressing the real issue between us. And that politeness - however well-intentioned - created something hollow.
Real alignment isn’t about agreeing on everything. It’s about being able to disagree productively. It’s about knowing that the relationship is strong enough to survive a hard conversation. It’s about trusting that you both want the same outcome even when you’re in conflict about how to get there.
Fake alignment is what happens when the relationship is too fragile for honesty. When politeness becomes a substitute for trust. When you both sense the problem but neither of you wants to be the one who names it.
The Alignment Tax and What It Costs Your Team
Here is what I didn’t fully appreciate until I had seen both versions:
The CPO-CTO relationship doesn’t stay between the CPO and the CTO.
It flows down.
When we were misaligned in the first company and finally fixed it, the team unblocked almost overnight. Not because we had solved a technical problem or a process problem. Because we had solved our problem — and stopped sending mixed signals into the org.
When we drifted apart in the second company and never fixed it, the team absorbed that drift. They saw it in the inconsistency between our messages. They felt it in the lack of clear direction. They responded to it by protecting themselves, moving slowly, avoiding risk.
Your team sets their temperature based on yours.
If you and your CTO are truly aligned - honest behind closed doors, united in front of the team - your org will move with more confidence and speed than any process redesign can create.
If your alignment is fake - polite in meetings, misaligned everywhere else - your team will feel it before you admit it to yourself.
How to Know If Your Alignment Is Real
Here are the questions I now ask myself when I’m assessing a CPO-CTO relationship - my own or someone else’s:
Can you have the hard conversation? Not the comfortable one. The one where you genuinely disagree and both of you know it. If that conversation keeps getting postponed, that’s a signal.
Do you present a united front - even when it’s hard? Real alignment means the team never has to guess which of you to listen to. If your respective teams are getting different signals, the alignment isn’t real yet.
Do you protect each other or protect your own teams? This is the most honest test. When conflict bubbles up from below, the first instinct of a strong CPO-CTO partnership is to look at each other and ask: what are we doing that’s causing this? The first instinct of fake alignment is to defend your own people.
Are the hard conversations getting harder or easier over time? In a real relationship, they get easier. You build a shared language. You trust each other’s intentions. In a fake one, they get harder - or they stop happening altogether.
If You Suspect Your Alignment Is Fake Right Now
The moment you stop having hard conversations, you start paying the Alignment Tax.
Not tomorrow. Now. Every week you let the discomfort sit without naming it, the tax gets a little higher. The team absorbs a little more of the mixed signal. The trust erodes a little further.
The fix is not a new process or a new structure. It’s a conversation.
The one you’ve been avoiding.
Go have it behind closed doors, without an audience, without performance. Be honest about what you’re sensing. Ask directly whether the alignment you think you have is actually real. It will be uncomfortable. It might be the most uncomfortable conversation you’ve had in months.
It will also be the most valuable one.
Because the alternative - staying polite, protecting your teams, letting the slow fire burn - costs far more than the conversation ever will.
The relationship between a CPO and a CTO sets the temperature for the entire organization.
Make sure yours is real.
Ready to upgrade your Operating System?
🎓 Live cohort in June - The CPO Intensive: Fix the System. Lead with Confidence. Four weeks, real work, real leaders. Join here (Paid subscribers get 25% off )
💼 Follow me on LinkedIn for daily insights
This article is part four of my series about the four leadership taxes.
Part One: My Product Operating Model
Part Two: The Therapy Tax
Part Three: The Trust Tax
Part Four: The Alignment Tax
The “protecting your teams instead of addressing the real issue between you” test is the most honest diagnostic in here and the one most people fail without realising it.
The instinct to protect your own people feels like good leadership in the moment. It reads as loyalty, as advocacy, as someone in your corner. What it actually does is redirect a leadership problem into a team problem and then wonder why the team keeps having the same issues.
The second story is more common than most leaders admit because fake alignment is comfortable and real alignment is expensive. The polite version lets both parties feel like the relationship is fine. The conversation that would fix it requires one person to go first, which means accepting that naming the problem might make them the problem.
Most people wait for the other person to go first. That’s how the slow fire burns.
Great article. Perhaps one lens through which to view this is that the C-level is a team in and of itself, and as a team, it is susceptible to the 5 dysfunctions, like every other team. Fear of conflict, and a lack of trust seem to be lurking here.