Managing Up: How CTOs and CPOs Build Trust with Their CEO

What Your CEO Actually Needs From You.

Managing up is the skill most CTOs and CPOs never got taught. Your good at building teams, shipping product, and navigating technical complexity. The relationship with your CEO is a different kind of problem, and quietly, it’s where some of the most capable technical leaders I coach and advise come unstuck.

For CTOs and CPOs, managing up to the CEO is often the leadership skill they were least prepared for. The problem rarely looks like a problem at first. You’re delivering. Your team is shipping. The CEO seems satisfied. And then, often suddenly, something shifts. You find yourself out of sync. Decisions begin to happen without your input, with your CEO working around or beneath your role to move things forward. Your strategic proposals don’t land the way you expected. The CEO seems to be operating from assumptions about your team that aren’t accurate, and you’re not sure how that happened.

What I’ve observed, across a lot of these relationships, is that the breakdown rarely starts with a single incident. It accumulates through a pattern of missed expectations, ones the CTO or CPO didn’t even know existed.

Why Managing Up to the CEO Is Hard for CTOs and CPOs

The CTO and CPO roles sit in a uniquely difficult position when it comes to managing up. Unlike a CFO or CMO, whose domains are reasonably legible to most CEOs, your world, whether that’s engineering architecture, technical debt, or product strategy, is opaque in ways that matter. The CEO can’t easily assess whether your team is performing well, whether the risks you’re describing are serious, or whether the timeline you’ve committed to is realistic.

That opacity creates a relationship that depends almost entirely on trust. And trust, in this context, relies on a very specific kind of communication: the ability to translate what’s happening in your world into language that connects to what the CEO cares about most.

Most CTOs and CPOs are never taught how to do that translation well. So they default to what they know: status updates, technical briefings, roadmap reviews. These feel thorough, but they often miss the point entirely.

Five Patterns That Erode the Relationship

These are the patterns I see most consistently when CTOs and CPOs struggle with managing up to their CEO:

01
The Translation Failure
You’re reporting on what your team is doing rather than what it means. Your CEO is left to connect the dots between “we’re refactoring the data layer” and what that implies for the product roadmap, the Q3 targets, or the board presentation. When they draw the wrong conclusions, it’s not because they’re not smart. It’s because the translation was your job, and it didn’t happen.
02
The Optimism Trap
The instinct to fix a problem before raising it feels responsible. To a CEO, it looks like concealment. When risk surfaces late, it’s almost always more expensive to address, and the CEO’s trust takes a hit that has nothing to do with the problem itself and everything to do with the timing of when they found out. They needed to know earlier, even without a solution in hand.
03
The Commitment Trap
You’re asked “when will it be done?” in a planning meeting. You give a number under pressure. That number becomes a commitment the CEO holds, often for much longer than you intended, and the CEO cites it in board conversations you weren’t part of. The skill isn’t refusing to answer. It’s giving a confident, bounded answer that reflects genuine uncertainty without sounding evasive.
04
The Reactive Cadence
You communicate upward when something goes wrong, when a decision is needed, or when a 1:1 is scheduled. Your CEO builds their mental model of your work from these irregular, often high-stakes interactions. You’re not managing the relationship. You’re responding to it. And a mental model formed from crises and deadlines will always look worse than the reality.
05
The Invisible Constraints
You know exactly why a decision made eighteen months ago is limiting your options today. You know where the technical debt lives and what it will cost to address. Your CEO doesn’t. And if you haven’t proactively shared that context, you’ll find yourself defending decisions that seem inexplicable from the outside, often at the worst possible moment.

The Common Thread

None of these patterns stem from incompetence or bad intent. They develop because most CTOs and CPOs are never given a map for managing up. The encouraging thing is that all five are addressable, not through dramatic behaviour change, but through more deliberate communication habits applied consistently.

What Strong Managing Up Looks Like for CTOs and CPOs

The CTOs and CPOs who excel at managing up to their CEO aren’t necessarily the ones doing the best technical work. They’re the ones who’ve developed a specific set of communication habits that make their work legible, their risks visible, and their judgment trustworthy.

🎯
Lead with the decision, not the status
Every briefing with your CEO should start with one of two things: the decision you need them to make, or the business implication of what you’re sharing. Not the technical detail, not the team update, not the feature list. If you can’t articulate the decision or implication, ask yourself whether this meeting is necessary. The CEO’s job is to make good decisions, and your job is to make that easy.
“If your CEO has to ask ‘so what does that mean for us?’ after your update, the translation didn’t happen.”
⚠️
Surface risk before you have a solution
The rule I coach: if you know about a meaningful risk, your CEO should know within 24 hours, even if you don’t yet know how you’re going to address it. “I don’t know yet, but here’s what I’m doing to find out” is a legitimate update. “I was waiting until I had an answer” is not. CEOs can absorb uncertainty. What erodes trust is the feeling that you withheld information. It’s worth being honest about why CTOs and CPOs wait: the instinct often has a fear component, specifically fear of appearing unprepared, or of alarming the CEO unnecessarily. Recognizing and working through that instinct is part of what it means to lead with real courage. We explore this at length in our Courage to Lead series.
📣
Own the narrative before it owns you
Your CEO is forming a view of your organization from many sources: your direct conversations, what other executives say, what the board asks about, what they read. If you’re not actively shaping that narrative, others shape it for you. A brief weekly written update, two or three tight paragraphs, gives you a consistent stake in how your CEO understands your team’s work. It doesn’t need to be long. It needs to be regular.
🔄
Build a consistent rhythm
The strongest CTO/CPO-CEO relationships I’ve seen are built on predictable, structured cadences: a weekly written update, a monthly strategic conversation focused on direction rather than status, and a thoughtful contribution to the quarterly business review. The rhythm itself builds trust. When the CEO knows what to expect and when, your relationship becomes a source of stability rather than a variable they have to monitor.
🧭
Understand your CEO’s actual priorities
What are your CEO’s three biggest concerns right now? What did they promise the board last quarter? What keeps them up at night? Your job is to make the connection between your team’s work and those things visible and explicit, not to wait for the CEO to draw the line themselves. This is particularly important as agentic development changes what engineering teams can deliver, and the CEO needs to understand that shift in terms of business opportunity, not technical capability.

The Underlying Principle

Across all five habits, there’s a consistent thread. The CTO or CPO who manages up well isn’t trying to impress their CEO. They’re trying to make the CEO’s job easier. That shift in intent changes almost everything about how you communicate upward.

Your CEO will never fully understand your world. But you can fully understand theirs. That asymmetry, when you lean into it, is where the strongest CTO/CPO-CEO relationships take root.

A Note on Timelines and Commitments

The timeline question deserves its own attention because it’s where managing up most often breaks down for CTOs and CPOs. “When will it be done?” is one of the most loaded questions a CEO can ask, and almost nobody answers it well.

The wrong answer is false precision: a specific date given under pressure that becomes an anchor in the CEO’s mind, surfaces in board conversations, and lingers long after you’ve forgotten you ever said it. Evasion is no better: “it depends,” “we’re still scoping it,” or an answer so hedged it communicates nothing.

The right answer is confident uncertainty. Something like: “Based on what we know today, we’re targeting the end of Q2. The biggest risk to that is X, and here’s how we’re managing it. I’ll give you an updated view in three weeks when we know more.” This gives the CEO what they actually need: a planning horizon, the key risk, and a date when they’ll have better information. It also models the kind of thinking that builds credibility over time.

The same principle applies to scope. When a CEO asks “can we add this feature?” the answer almost always involves a trade-off. The CTO or CPO who says “yes, and here’s what moves” is far more useful than the one who says “it’s complicated” or, worse, says yes and quietly absorbs the cost into the team.

Questions to Sit With

If you’re a CTO or CPO thinking honestly about managing up to your CEO, these are worth working through:

  • If your CEO had to describe to the board what your team accomplished last quarter, what would they say? Is that what you would say? If there’s a gap, that’s a communication gap, not a performance gap.
  • When did you last raise a meaningful risk to your CEO before you had a plan to address it? If you struggle to find an example, consider what that pattern is costing you in terms of trust.
  • Do you have a consistent, self-initiated cadence for the CEO relationship, or does most of your upward communication happen reactively, when something is needed or something has gone wrong?
  • Does your CEO understand the key constraints your team is operating under, such as the architectural decisions, the accumulated technical debt, and the hiring gaps, or would those feel like surprises if they came up in a board conversation?
  • What does your CEO actually care most about right now? Not what they say in 1:1s, but the things driving their decisions. How explicitly does your work connect to those things in the way you communicate it?

A Final Thought

Managing up well doesn’t mean being political. It doesn’t mean softening hard truths or packaging bad news attractively. It means developing the discipline to communicate your world in terms that are useful to the person you’re communicating with. And it takes real courage to do it consistently: to raise the uncomfortable thing early, to push back on the unrealistic expectation, to say “I don’t know yet” to someone you want to inspire confidence in. If that’s a dimension you want to explore further, our Courage to Lead series goes deep on exactly that.

Your CEO is making decisions about the whole business, often with incomplete information and real time pressure. The more you can make your piece of the business legible to them, the better those decisions get. That’s good for them, good for your team, and ultimately good for you.

The CTOs and CPOs who build strong upward relationships aren’t the ones who have the smoothest delivery or the most polished presentations. They’re the ones who understand that their job doesn’t stop at the boundary of their own organization, and who invest in the relationship with the same seriousness they bring to everything else.

Ready to talk about CTO coaching with Leigh?

Book a 30-minute introductory call to explore whether coaching is right for you.

Book a meeting with Leigh →

Leigh Newsome - CTO Coach

Leigh Newsome

Partner, Hoola Hoop · CTO & CPO Coach

Leigh Newsome is a Partner at Hoola Hoop and a CTO & CPO coach with 25 years of experience scaling product and engineering teams. He has worked with a wide range of startups and global enterprises, including Avid, Digidesign, WPP, and Kantar/Millward Brown, and successfully led TargetSpot (backed by Union Square Ventures, Bain Capital Ventures, and CBS) through its acquisition to Radionomy Group (Vivendi). When he’s not coaching CTOs, you’ll find him teaching digital audio to graduate students at NYU, building audio and signal processing applications, or flying fixed-wing aircraft, but never all three at once.

Share this:

CTO Coaching: A Guide for Leaders

I’ve spent 25 years scaling product and engineering teams, and one thing I’ve learned is that the hardest part of being a CTO is not about technology. For most CTOs and engineering leaders I know and have worked with, it’s not technical competence that holds them back. It’s the leadership aspects of the job that challenges them. The role demands that you set technical vision, build and scale engineering teams, navigate AI adoption, manage board and investor relationships, and drive product strategy all at once.

That’s exactly why I do what I do. And it’s what CTO coaching is for.

What is CTO Coaching?

CTO coaching is a structured working relationship between a technology executive and an experienced coach, designed to help the CTO grow as a leader, make better decisions, and perform more effectively in their role.

It’s very different from consulting. A consultant gives you answers. As a CTO coach, I help you to develop the skills, self-awareness, and judgment to find better answers yourself.

My approach is grounded in 25 years of hands-on experience as a technology and product executive — having served in CTO, CPTO, and CEO roles across a range of growth-stage companies. What I value most about the team I work with at Hoola Hoop is that every partner and coach brings that same perspective. We’re all former operators who have navigated exactly the challenges our clients face. Not theorists. Practitioners. The guidance is concrete because the experience is real.

Who Needs CTO Coaching?

In my experience, CTO coaching is highly valuable at multiple career stages, but it tends to be incredibly impactful in a few specific situations.

01
The Transition to CTO
The first is the transition from engineer or VP of Engineering to CTO. This is one of the hardest professional shifts in tech, and I see most leaders struggle with it. The skills that made you a great engineer such as technical problem-solving, individual execution are not the same skills that make a highly impactful CTO. Coaching helps accelerate that transition, grow your leadership and avoid common pitfalls.
02
Company Growth
The second is company growth. When a startup scales from 20 to 200 people, the CTO’s job changes dramatically. What worked at one stage breaks at the next. I’ve been through those inflection points myself, CTO coaching provides a sounding board for navigating those points in real time.
03
Friction & Conflict
The third is when you are experiencing friction with the CEO, the product team, the board, or your own engineering organization. These dynamics are rarely just technical. As a CTO Coach, I help you understand what’s really going on and how to address it.

Areas CTO Coaching Addresses

Effective CTO coaching covers both the technical leadership dimension and the human side of the role. In my work with technology leaders, these are some areas that come up consistently:

🎯
Technical Strategy & Vision
Helping CTOs articulate a clear technical roadmap that aligns with business goals, make sound architecture decisions, and communicate technical trade-offs to non-technical stakeholders in a way that builds trust.
👥
Building & Scaling Engineering Teams
Hiring, developing, and retaining strong technical talent. I work with CTOs on how to build a high-performance culture, develop technical managers, and structure their engineering organization for scale.
🤖
AI Adoption & Innovation
Today’s CTOs are under significant pressure to integrate AI into their products and processes. I help you think through AI strategy clearly — what to build, what to buy, and how to lead your teams through the change.
🎤
Executive Presence & Influence
CTOs frequently need to advocate for technical investments to a CEO, board, or investors who may not have a technical background. CTO coaching builds the communication skills and executive presence to do this effectively.
🤝
Cross-functional Leadership
The relationship between product and engineering is one of the most important — and most frequently strained — dynamics in a growth-stage company. CTO coaching helps leaders build stronger working relationships across the C-suite.
🏛️
Managing Up & Board Relationships
As companies scale, CTOs increasingly interact with boards and investors. I prepare technology leaders for these conversations and help them navigate the dynamics involved, including the ones nobody warns you about.

What Makes A Good CTO Coach?

Not all coaches are created equal. Here’s what I’d tell any leader looking for a CTO coach:

  • Real operating experience in technology leadership First and most importantly, look for a coach with real operating experience in technology leadership. A coach who has never scaled an engineering team, managed technical debt under growth pressure, or navigated a difficult CTO-CEO dynamic will struggle to give you relevant, credible guidance. I’ve spent decades doing exactly that, and it’s the foundation of every coaching relationship I have.
  • Someone who asks great questions, not just dispenses advice Second, look for someone who asks good questions rather than just dispensing advice. The best coaching unlocks your own thinking. A coach who just tells you what to do creates dependency, you want someone who builds your capacity to think through hard problems independently.
  • Honest and willing to challenge you Third, look for a CTO coach who will be honest with you and challenge you. As a CTO, you often don’t get candid feedback from your teams or peers. A good CTO coach will tell you what you need to hear, not just what you want to hear.

What to Expect from CTO Coaching

My coaching engagements typically involve regular one-on-one sessions usually weekly or bi-weekly, focused on whatever is most pressing for you at that moment and on the goals we have set together. Sessions are confidential, which creates the space for the kind of honest conversation that’s hard to have with a direct report, peer, or investor.

I often start with an interview-based 360 review speaking directly with your peers, direct reports, and CEO. This helps get an honest, multi-perspective picture of where you are excelling and where the real development opportunities lie. Then we define 3 to 5 goals to work on. This gives our CTO coaching sessions a grounded starting point rather than relying solely on self-assessment.

From there, coaching sessions evolve to address real-time issues as they arise such as team performance challenges, a board presentation, technology decisions, a team restructure, or a conflict with the CPO or CEO. I also facilitate CTO leadership roundtables, bringing together technology leaders from across our client base and portfolio to share experiences, challenge each other’s thinking, and learn from peers who are navigating similar inflection points. Many CTOs find these peer sessions as valuable as the one-on-one coaching itself.

A great CTO coach is the trusted advisor you can call when you’re facing tough decisions and need someone in your corner who has seen it before.

Ready to talk about CTO coaching with Leigh?

Book a 30-minute introductory call to explore whether coaching is right for you.

Book a meeting with Leigh →
Leigh Newsome - CTO Coach

Leigh Newsome

Partner, Hoola Hoop · CTO Coach

Leigh Newsome is a Partner at Hoola Hoop and a CTO coach with 25 years of experience scaling product and engineering teams. He has worked with a wide range of startups and global enterprises, including Avid, Digidesign, WPP, and Kantar/Millward Brown, and successfully led TargetSpot through its acquisition to Radionomy Group (Vivendi). When he’s not coaching CTOs, you’ll find him teaching digital audio to graduate students at NYU, building audio and signal processing applications, or flying fixed-wing aircraft — but never all three at once.

Share this:
Let’s Talk

Thank you for your interest in Hoola Hoop’s approach to executive coaching.

We’re excited to help you unlock your and your organization’s full potential. Please share a few details about yourself and your coaching needs. Let’s start this transformative journey together.

    *Required fields