I've coached C-suite executives for years, and I'll say the thing most guides won't: the skills that got you promoted to the C-suite are not the skills that keep you there. That's the trap. You were made CFO or COO because you were brilliant at your function. Then the job changes overnight — you're no longer rewarded for being the smartest person on your subject, you're rewarded for making the whole organisation work without you standing over it.
Most "how to succeed as an executive" content is a list of nouns — leadership, communication, change management — dressed up as insight. It isn't insight. It's a dictionary entry. Here's my actual position, built from sitting across the table from executives who were failing quietly, long before their board noticed: success in the C-suite is not about acquiring more skills. It's about giving up control of the ones you already have.
Why the standard advice misses the point
Ask any leadership content mill what a C-level executive needs and you'll get the same five words back: leadership, communication, change management, technical depth, relationship-building. All true. All useless on their own, because they describe outcomes, not the mechanism that produces them. Nobody fails as an executive because they didn't know communication mattered. They fail because they kept operating the way they operated two levels down — hands on the work, answers ready, decisions fast — and that exact behaviour, which used to be their strength, becomes the thing suffocating their team.
I call this the authority trap. The more senior you get, the more your presence in a room shuts down the thinking of everyone else in it. Say your view first in a strategy session and watch what happens: the room converges on your view within ninety seconds, whether or not it was the best one. That isn't leadership. That's gravity. Real C-suite capability is learning to withhold your own voice on purpose, so the organisation's collective judgement — which is usually better than any one person's, including yours — gets a chance to surface.
Change management is a symptom, not a skill
Change management gets treated as a technique you learn — a framework, a communication cadence, a stakeholder map. I think that's backwards. Change management is what happens automatically when an executive has built enough trust that people will follow direction they don't yet fully understand. If you need a change management framework to get your organisation through a transition, you're compensating for a trust deficit that should have been closed months earlier.
The executives I've watched succeed at organisational change didn't manage it — they'd already earned the credibility for it before the change was announced. The ones who struggle reach for a framework in the moment of crisis, as if a slide deck can retroactively build the relationship capital that was never invested. Boards like to hire external candidates for transformation mandates because an outsider arrives without the baggage of past decisions — but that's a substitute for trust, not a shortcut around needing it. The new CEO still has to earn it, just faster and under more scrutiny.
Communication: the discipline of subtraction
Board-ready communication isn't about being more articulate. It's about being willing to say less. Every executive I've coached who struggled with board presence had the same underlying issue: they were trying to demonstrate their command of the detail, when the board needed them to demonstrate command of the judgement. Detail is reassuring to the person presenting it and exhausting to the person receiving it. The skill isn't synthesis in the abstract sense people mean when they use that word — it's the discipline of deciding what to leave out, in public, and living with the discomfort of not having said everything you know.
This matters more the further outside your organisation you go. Internally, people already have context and will forgive imprecision. Externally — shareholders, regulators, journalists — you get one sentence before they've formed a judgement about your competence. The executives who communicate well externally are, almost without exception, the ones who have practised deciding in advance what they will not say, rather than improvising restraint in the moment.
Leadership is not inspiration — it's removal
I'm sceptical of "inspirational leadership" as a category, at least as it's usually taught. Inspiration is a byproduct, not a strategy. What I've actually seen separate strong C-suite leaders from weak ones is far less romantic: the strong ones are constantly removing obstacles other people can't remove for themselves — a political stalemate, a resourcing fight, a decision stuck between two peers who won't budge. The weak ones are adding value at the exact layer where the organisation needed them to get out of the way.
Humility, in this context, isn't a personality trait. It's a practical prerequisite. You cannot see what's blocking your team if you're still convinced your read of the situation is the correct one by default. The executives who keep growing are the ones who treat their own certainty as a hypothesis to be tested against what their team is actually telling them — often not in words, but in what they avoid raising with you.
Relationship building: stop measuring your own output
There's a specific failure mode I see in high-performing executives who plateau at VP or SVP and never quite make the leap to C-suite credibility: they keep measuring their own contribution. What did I deliver, what did I decide, what did I fix. That instinct is exactly what built their career, and it's exactly what caps it. A C-suite leader's currency isn't personal output — it's the quality of the leadership team underneath them, and whether that team can operate at full capacity without the exec in the room.
I've had this conversation, almost word for word, with three different executives across three different industries: they describe their week as "finally productive" because they personally closed a deal, resolved an escalation, or rewrote a proposal that a direct report had drafted. Every one of those interventions felt like leadership in the moment. None of them were. Each one was the executive quietly signalling to a capable adult that their work wasn't trusted to stand on its own — and each one made that person a little less likely to bring their best thinking forward next time, because why would they, if it's getting rewritten anyway.
The correction isn't complicated to describe, even though it's hard to live. Before you step into someone else's work, ask what it costs the relationship if you're right versus what it costs if you're wrong. Being right and rewriting their proposal costs you almost nothing today and costs you their initiative for months. Being wrong and letting their version stand costs you a slightly worse outcome today and builds a leader who'll take the next risk without waiting for permission. Most executives are optimising for the wrong side of that trade without realising it's a trade at all.
This is uncomfortable to hear because it means your personal excellence stops being the metric. You can be the most capable person in the building and still be failing at the job, if the people who report to you can't function without checking in with you first. I'd go further: if your team can't make a decision correctly in your absence, that's not evidence of your value. It's evidence you haven't done the job yet.
Technical depth has a shelf life — know what to keep
Executives worry, correctly, about losing technical credibility as they move up. But the answer isn't to keep learning everything at the same depth you did in your functional role — that's not possible and trying to do it is what causes the burnout stories you hear about senior leaders. The skill is knowing which technical judgements you personally need to retain the ability to make, and which ones you need to delegate entirely and trust the delegation. Get that split wrong in either direction and you either become a bottleneck or you become irrelevant to the decisions that matter.
I ask every executive I coach the same question when this comes up: name the three decisions in your function that, if delegated badly, would actually damage the business within a quarter. Most can't answer immediately, and that's the tell. If you can't name your three, you don't have a delegation strategy — you have a habit of intervening wherever you feel anxious, which is not the same thing and is far more expensive. The exercise forces a distinction between technical depth you need as a safeguard and technical depth you're keeping out of nostalgia for the work you used to be good at.
The nostalgia version is more common than anyone admits. Former CFOs who become CEOs often keep reviewing budget variances line by line long after they've hired a finance chief whose entire job is to own that. It isn't due diligence at that point — it's comfort-seeking, dressed up as rigour. Your finance chief reads the hesitation immediately: if the CEO doesn't trust my numbers without checking them personally, why would the board? Every unnecessary technical intervention from the top erodes the authority of the person you supposedly enabled.
The Private Architecture™ lens on C-suite readiness
- Withholding, not withdrawing: Does the executive deliberately hold back their own view in early discussion to let the team's judgement surface, or do they simply go quiet and disengage? The two look similar and produce opposite results.
- Trust before crisis: Has the executive built enough credibility with the organisation that a change mandate lands as direction people will follow, rather than a case that has to be argued from scratch under pressure?
- Team capability in their absence: Can the leadership team make a correct, defensible decision when the executive is out of the room — not just execute a decision already made for them?
- What they chose not to say: In board or external communication, is there evidence the executive deliberately cut material they understood, rather than simply running out of time to say it?
- Delegation with retained judgement: Has the executive identified the small number of technical calls only they should still make personally, and handed everything else off completely — no shadow reviewing, no second-guessing after the fact?
The distinction I want you to take from this
If you remember one thing from this, make it this: the C-suite doesn't reward you for being right more often than everyone else. It rewards you for building an organisation that's right more often than you are. That's a harder thing to accept than it sounds, because it means the instincts that made you exceptional at every level below this one are now, at best, neutral — and at worst, actively working against the team you're meant to be developing.
I've sat with executives who had every technical credential the job could ask for and still failed, because they never made that shift. And I've watched executives with far less obvious polish succeed, because they understood early that their job had changed from doing the work to building the conditions for other people to do it well without them. The former group kept optimising themselves. The latter group started optimising the system around them.
This is why I don't think "leadership skills" is a useful frame for C-suite success at all. Skills are things you do. What actually determines whether an executive succeeds at this level is something closer to a posture — a standing decision about how much of yourself you deploy into any given room, and how much space you deliberately leave for everyone else in it. Get that posture right and the change management, the board communication, the team performance — all of it — becomes far more straightforward than any framework makes it look. Get it wrong and no framework will save you.
Are you looking for executive leadership coaching? Turn to Stuart Andrews, offering leadership coaching to support executives and business leaders to drive successful initiatives while their teams consistently perform at the highest level. Schedule a discovery call or buy the book now!
Further reading: A CEO, a calendar, and three red items
Further reading: Private Architecture™