My working view is that to succeed as a C-level executive, you have to give up control of the skills that got you here. The job changes overnight: you were made CFO, COO or CHRO because you were brilliant at your function, and now you are rewarded for making the whole organisation work without you standing over it.
I coach and advise executives at exactly this moment. Most advice on the subject is a list of nouns: leadership, communication, change management, technical depth, relationship-building. All true, and none of it names the mechanism. My position is that success in the C-suite is not about acquiring more skills. It is about the posture you take towards the skills you already have.
| What got you promoted | What the C-suite rewards |
|---|---|
| Being the smartest person on your subject | Building a team whose judgement is better than yours |
| Having the answer ready and moving fast | Withholding your view long enough for others to give theirs |
| Personal output: what I delivered, decided and fixed | Whether the team operates at full capacity without you in the room |
| Technical depth across your function | A short list of calls only you should make, and trust in everything else |
| Detail as proof of command | Judgement about what to leave out |
Why the standard advice on how to succeed as a C-level executive misses the point
Nobody fails as an executive because they did not know that communication mattered. They fail because they kept operating the way they operated two levels down: hands on the work, answers ready, decisions fast. That behaviour was a strength. At the top of the organisation it becomes the thing suffocating the team. McKinsey's CEO Excellence research, which looked across more than 20 years of data on 7,800 CEOs from 3,500 public companies (McKinsey, CEO Excellence), offers a useful corrective. Its authors observe that the best CEOs are ordinarily excellent in a few areas, able in all others and challenged in none, and that they have yet to meet one who excels at every one of the 18 responsibilities they catalogued (McKinsey, 2019). The aim is not to be good at everything. It is to choose where your own attention is irreplaceable.
The authority trap
I call the first thing to unlearn the authority trap. The more senior you become, the more your presence in a room closes down the thinking of everyone else in it. Say your view first in a strategy session and the room tends to converge on it within minutes, whether or not it was the best one. The research on power points the same way. In experiments by Galinsky and colleagues, people primed with high power were less likely to take another person's perspective and less accurate at reading other people's emotions (Galinsky et al., 2006). Detert and Edmondson found that employees hold widely shared, taken-for-granted beliefs about when and why speaking up at work is risky or inappropriate, and that these beliefs help explain workplace silence (Detert and Edmondson, 2011).
Put the two findings together and you have the trap. You become less good at hearing the room precisely as the room becomes less willing to tell you. Real C-suite capability is learning to withhold your own voice on purpose, so the organisation's collective judgement gets a chance to surface. A practical version: speak last in your own leadership meetings, ask for the strongest objection before you state a preference, and record who disagreed with you this month. Withholding is not withdrawing. A leader who goes quiet and disengages produces the opposite result.
Change management is what trust makes possible
Change management is usually taught as a technique: a framework, a communication cadence, a stakeholder map. I think that gets the order wrong. Change management is what happens when an executive has built enough credibility that people will follow a direction they do not yet fully understand. If you need a framework to carry the organisation through a transition, the framework is compensating for a trust deficit that should have been closed months earlier.
The executives who handle organisational change well tend to have earned the credibility before the change is announced. Those who struggle reach for a framework in the moment of crisis, as if a slide deck could create relationship capital retroactively. Trust is built in small, repeated moments of keeping your word and hearing bad news well, which is the territory of my piece on teams that stop being honest. It is a slow asset and a leader's most useful one in a hard quarter.
Communication at the top is the discipline of subtraction
Board-ready communication is not about being more articulate. It is about being willing to say less. The common mistake is to try to demonstrate command of the detail when the board needs to see command of the judgement. Detail reassures the person presenting it and exhausts the person receiving it. The skill is the discipline of deciding what to leave out, in public, and living with the discomfort of not having said everything you know. If your board relationship needs work, managing up when your board demands the impossible goes further.
The effect increases outside the organisation. Internally, people have context and forgive imprecision. With shareholders, regulators and journalists you get a sentence before they have formed a view of your competence. The executives who communicate well externally have usually practised deciding in advance what they will not say, rather than improvising restraint in the moment.
Leadership at this level is mostly removal
I am sceptical of inspirational leadership as a category, at least as it is usually taught. Inspiration is a by-product. What separates strong C-suite leaders from weak ones is less romantic: the strong ones keep removing obstacles other people cannot remove for themselves. A political stalemate, a resourcing fight, a decision stuck between two peers who will not budge. The weaker ones add value at the exact layer where the organisation needed them to get out of the way.
Humility in this setting is a practical prerequisite rather than a personality trait. You cannot see what is blocking your team while you are still convinced your own read of the situation is correct by default. The executives who keep growing treat their certainty as a hypothesis to test against what the team tells them, often not in words but in what they avoid raising with you.
Stop measuring your own output
A common failure mode in strong executives who plateau at VP or SVP level is that they keep measuring their own contribution: what did I deliver, decide and fix. That instinct built their career and now caps it. A C-suite leader's currency is the quality of the leadership team underneath them, and whether that team can run at full capacity without the executive in the room.
Picture a week that an executive describes as finally productive because they personally closed a deal, settled an escalation and rewrote a proposal a direct report had drafted. Treat this as an illustration rather than a client story. Each intervention felt like leadership at the time. Each also told a capable adult that their work could not stand alone, and made them a little less likely to bring their best thinking next time. Before stepping into someone else's work, ask what it costs the relationship if you are right and what it costs if you are wrong. Being right and rewriting costs you almost nothing today and costs their initiative for months. Being wrong and letting their version stand costs a slightly worse outcome now and builds a leader who takes the next risk without waiting for permission.
This is uncomfortable because your personal excellence stops being the metric. You can be the most capable person in the building and still fail the job if the people who report to you cannot function without checking in first. If your team cannot make a decision correctly in your absence, the job is not yet done, however indispensable that makes you feel.
Technical depth has a shelf life
Executives worry, correctly, about losing technical credibility as they rise. The answer is not to keep learning everything at the depth you had in your functional role. That is impossible, and the executives I see trying it end up exhausted. The skill is knowing which technical judgements you personally need to keep and which to delegate completely, then trusting the delegation. McKinsey reports that executives spend nearly 40 per cent of their time on decisions and judge much of it poorly used (McKinsey, 2023). Spending it on calls someone else could own is expensive.
A direct test: name the three decisions in your function that, if delegated badly, would damage the business within a quarter. Most executives cannot answer at once, and that is the tell. If you cannot name your three, you do not have a delegation strategy. You have a habit of intervening wherever you feel anxious. In a 2022 McKinsey discussion of its CEO Excellence research, one of the authors recalled a chief executive with 23 years in the role who said 15 of his decisions in that time really mattered, and only he as CEO could make them (McKinsey, 2022). The number is small on purpose. Most of the job is making sure the other decisions are made well by someone else.
- Withholding, not withdrawing: Does the executive deliberately hold back their view in early discussion so the team's judgement surfaces, or do they simply go quiet? The two look alike and produce opposite results.
- Trust before crisis: Has the executive built enough credibility that a change mandate lands as direction people will follow, rather than a case 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 one already made for them?
- What they chose not to say: In board or external communication, is there evidence the executive cut material they understood, rather than running out of time?
- Delegation with retained judgement: Has the executive named the few calls only they should make, and handed everything else off with no shadow reviewing and no second-guessing?
The first two quarters in a new C-suite role
If you have just been appointed, or you are about to be, the early months set the posture. I would spend them on five things, in roughly this order.
- Listen before you decide: Meet your direct reports and their teams, and ask what they avoid raising with the previous leader. Record the answers without reacting.
- Write down who decides what: Put decision rights on one page, agree it with your peers and revise it quarterly. The Decision Bottleneck Challenge is a fast way to see where decisions pile up.
- Name your three decisions: List the calls that only you should make. Delegate the rest openly and stop shadow-reviewing it.
- Test the team without you: Take a planned absence and watch what stalls. Treat the result as your development agenda, not as a verdict on the team.
- Plan your external voice: Decide what the board and key stakeholders will hear from you in the first 100 days, and what you will deliberately leave out.
A C-level view of success
The instincts that made you exceptional at every level below this one are, at best, neutral here, and at worst they work against the team you are meant to be developing. I have seen executives with every technical credential fail because they never made the shift, and executives with less polish succeed because they understood early that the job had changed from doing the work to building the conditions in which other people do it well.
This is why I find "leadership skills" an unhelpful frame for C-suite success. Skills are things you do. What decides the outcome is 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. Get the posture right and the change management, the board communication and the team performance become far more straightforward than any framework makes them look. If you want a second set of eyes on yours, apply to work with me, look at the CapabilityAI page, or start with the leadership assessments to see where your team stands without you. If strategy sits in your remit, what a chief strategy officer should own when AI becomes corporate strategy shows where that line falls.