The moment I knew something had changed was embarrassingly mundane.
I was sitting in a meeting — the kind where a complex problem needed a decision — and I realised I wasn’t the most knowledgeable person in the room. Not even close. My team had deeper expertise on the specifics than I did. They had better data. They’d been closer to the details for weeks.
And for the first time, that didn’t bother me.
For years, being the expert was my identity. In sales, in marketing, in e-commerce, in procurement — I built my career by knowing more than the people around me. Being the person with the answer. The one others turned to when things got complicated.
Then I moved into leadership roles. First smaller teams, then larger ones — eventually managing large teams at Apple, building systems across multi-billion euro portfolios at ThyssenKrupp, teaching strategy at ESB Business School, leading proejcts in procurement at Thales Group.
And somewhere along the way, the thing that had always made me valuable — my expertise — became the thing that was holding me back.
This guide is about that transition. Not the version you read in leadership books, where the shift happens cleanly in a chapter or two. The real version. The one where you lose confidence before you find it again. Where you have to let go of what defined you before you can discover what replaces it. Where the path from expert to executive isn’t a promotion — it’s a transformation.
I’ve been writing about different aspects of this journey for months now. This guide brings those threads together into one place. It’s for anyone who’s in the middle of this shift, approaching it, or trying to help others through it.
The identity shift nobody warns you about
The hardest part of becoming a leader isn’t learning new skills. It’s letting go of old ones.
When you’re an expert, your value is clear. You know things. You solve problems. You have answers that other people don’t. There’s a directness to it that’s deeply satisfying — someone brings you a challenge, you work through it, you deliver a result. The feedback loop is tight and the validation is constant.
Leadership breaks that loop.
Suddenly, your job isn’t to have the answer. It’s to build a team that finds answers without you. Your value isn’t in what you know — it’s in what you enable. And that shift, which sounds simple when you describe it, feels profoundly disorienting when you’re living it.
I remember the period after my first major leadership transition. I kept jumping into technical discussions I should have stayed out of. I’d review work that my team could have handled. I’d feel restless in meetings where my role was to listen rather than solve. Not because I didn’t understand the new role intellectually — I did. But because my identity was still anchored to being the person with expertise, and I didn’t yet know who I was without that.
What I’ve come to understand is that this is normal. Not a weakness. Not a failure of adaptation. A predictable response to losing the source of confidence that built your career.
The experts who make this transition successfully don’t eliminate their expertise. They learn to hold it differently — as context rather than currency. They develop a new kind of confidence that comes from building others up rather than being the smartest person in the room.
I’ve written about this transition in much more depth — the stages of it, the emotional weight of it, and what actually helps — in the mid-career pivot: from expert to leader without losing yourself. If you’re in the middle of this shift right now, I think it will feel familiar.
Building leaders on your team, not just managing tasks
Here’s a question that took me longer to confront than I’d like to admit: what happens to my team when I leave?
For a long time, I measured my value as a leader by what my team accomplished while I was leading them. Targets hit. Projects delivered. Problems solved. And those things matter. But they’re not the real measure.
The real measure is what happens when you’re not there.
If a team falls apart when the leader leaves, the leader wasn’t building leaders. They were building dependency. And dependency, however productive it looks in the short term, is a failure of leadership development.
The shift I had to make — and it was genuinely difficult — was from managing tasks to developing people. From making sure the work got done to making sure the people doing the work were growing through it. From solving problems for my team to creating the conditions where they learned to solve problems themselves.
This doesn’t mean stepping back entirely. It means being deliberate about which problems you solve and which ones you let your team struggle with — productively. It means giving people responsibilities that stretch them before they feel fully ready, and being present enough to support them without taking over. It means having honest conversations about potential that sometimes include uncomfortable truths about gaps.
The best leaders I’ve worked under did this for me. They saw capability I didn’t see in myself. They put me in situations that forced me to grow. They tolerated my mistakes when the learning was more valuable than the perfection.
I try to do the same. I don’t always succeed. But the intention shapes everything about how I lead.
I’ve written about this in detail — the framework, the practical challenges, the moments where it works and the moments where it doesn’t — in building leaders, not just managing tasks. If you’re managing a team right now and wondering whether you’re developing people or just directing them, that article might clarify things.
Leading through uncertainty and chaos
Nobody teaches you this in business school.
They teach you frameworks. Models. Case studies where the data is clean and the answer is findable if you analyse long enough. And those tools are valuable — I’ve used them throughout my career.
But the moments that actually define your leadership aren’t the ones where you have enough information. They’re the ones where you don’t.
A key supplier shuts down unexpectedly and you have seventy-two hours to find an alternative. A reorganisation is announced and your team is looking at you for clarity you don’t have yet. A market shifts and the strategy you spent three months building is suddenly outdated. A crisis hits and there’s no playbook, no precedent, and no time to wait for certainty.
These are the moments that test what you’re made of. Not your intelligence. Not your experience. Your capacity to decide and act when the ground isn’t stable.
What I’ve learned — through supply chain crises, organisational upheavals, and the kind of situations where you have to commit to a direction at maybe 70% certainty — is that the leaders who navigate chaos well share a few things. They communicate what they know and what they don’t, without pretending either category is different than it is. They make decisions at the speed the situation requires, not the speed that feels comfortable. They create pockets of stability for their teams even when everything around them is moving. And they adjust without shame when new information changes the picture.
The leaders who struggle in chaos are often the ones who were most successful in stable environments. Because stability rewards analysis, thoroughness, and certainty. Chaos rewards judgment, speed, and the ability to act on incomplete information without losing your team’s trust.
I’ve built a practical framework for this — how to make decisions under uncertainty, how to communicate when you’re not sure, and how to turn crisis from a threat into something that actually builds your team’s capability — in leading through chaos. If you lead in any environment where uncertainty is the norm rather than the exception, I think it’s worth reading.
Influence without authority: the skill that defines modern leadership
This one matters more than most people realise.
The higher you go in an organisation, the less your formal authority explains your actual impact. Directors report to VPs. VPs report to C-suite. Everyone reports to someone. And the work that matters most — the cross-functional initiatives, the strategic shifts, the changes that require multiple teams to align — none of that respects the org chart.
In procurement, I learned this early because procurement never has enough formal authority. You depend on engineering, legal, finance, operations, and leadership to deliver on what you’re responsible for. You learn to influence or you learn to be frustrated.
But this isn’t a procurement problem. It’s a leadership reality.
The executives I most admire — the ones who shape their organisations rather than just managing their function — are all exceptional at moving things without formal power. They build coalitions. They frame ideas in terms that different stakeholders can rally behind. They know when to push and when to let an idea marinate. They invest in relationships long before they need them.
This skill is learnable. I’ve seen people develop it who didn’t start with any natural talent for it. What it requires is genuine curiosity about other people’s perspectives, the discipline to frame your ideas in their terms rather than yours, and enough patience to build credibility over time rather than demanding it upfront.
I’ve written a detailed playbook — seven strategies, with the practical mechanics of each — in influence without authority. If you’re in a role where your responsibility exceeds your formal power — and most leadership roles are exactly that — this might be the most useful thing I can point you toward.
Building a legacy that outlasts your role
I want to share something I’ve been thinking about a lot lately.
At some point in your career — and it’s different for everyone — you start asking a different kind of question. Not “how do I advance?” but “what am I building that will last?” Not “what’s my next move?” but “what will I be remembered for?”
It’s a subtle shift. But it changes how you lead.
When I look back at the leaders who shaped me most, I don’t remember their strategies. I don’t remember their quarterly results. I remember the moments where they saw something in me I couldn’t see. Where they gave me a chance I hadn’t earned yet. Where they told me an uncomfortable truth that I needed to hear, delivered with enough care that I could actually receive it.
That’s legacy. Not the projects you delivered. The people you changed.
The challenge is that legacy-building doesn’t feel productive in the moment. Investing an hour in a development conversation with someone on your team doesn’t produce measurable output. Mentoring someone in another department doesn’t show up on your performance review. Building systems and processes that outlast your tenure means putting energy into things you won’t get credit for.
It requires a kind of generosity that the corporate environment doesn’t always reward. But I’ve come to believe it’s the most important work a leader does.
The leaders who build lasting legacy share something: they think in longer time horizons than their current role requires. They invest in people and systems that will keep working after they’ve moved on. And they’re comfortable with the fact that the best measure of their leadership might not be visible until years after they’ve left.
I’ve written about how to think about legacy deliberately — without turning it into a performance or a vanity project — in leading legacy: what you’ll be remembered for. It’s a more reflective piece than the others in this guide. But I think it might be the one that matters most in the long run.
Surviving the AI era as a leader
I almost didn’t include this section. It felt like it belonged in a different guide — the one about AI leadership that I’ve written separately.
But I kept coming back to it, because the leaders in the middle of the expert-to-executive transition right now are doing it in the hardest possible environment. AI isn’t just changing what organisations need from their leaders. It’s directly challenging the expertise that many mid-career professionals built their identity around.
If your career was built on analytical skill, AI does analysis faster than you ever will. If your value was knowing where to find information, AI democratises access to everything. If your competitive advantage was experience-based pattern recognition, AI is learning those patterns from datasets you could never process.
This is an identity threat layered on top of the identity shift I described at the beginning of this guide. You’re already trying to let go of being the expert. And now the world is telling you that expertise itself is being commoditised.
The result, for a lot of leaders, is exhaustion. 71% of leaders report heightened stress from AI transformation. That’s not a statistic — it’s a signal that something systemic is happening to the people responsible for leading organisations through this moment.
What I’ve found is that the leaders who sustain aren’t the ones who try to out-learn the technology. They’re the ones who lean into the capabilities that AI makes more valuable, not less. Emotional intelligence. The ability to sit with someone who’s scared and help them find a way forward. The judgment to know when the data is right but the decision is wrong. The wisdom to slow down when the technology is pushing everyone to speed up.
I’ve written about both sides of this. Leadership burnout in the AI era covers the exhaustion — where it comes from, how to recognise it, and what recovery actually looks like. And emotional intelligence as AI’s counterweight explores the capabilities that appreciate in value as AI capabilities expand — and how to develop them deliberately.
If you’re in the middle of a leadership transition and the AI dimension is making everything harder, those two pieces together might help you see what’s happening more clearly. And more importantly, what to do about it.
The leadership development practices that actually work
I want to end this guide with something practical. Not theory. Not frameworks. The things I’ve actually done — and seen others do — that made a genuine difference in developing as a leader.
Reflective practice. This is the one I resisted longest and now consider most important. Spending time — even fifteen minutes a week — deliberately thinking about what happened, why you responded the way you did, and what you’d do differently. Not self-criticism. Genuine reflection. I keep a simple journal. Most weeks it’s boring. Some weeks it surfaces something I wouldn’t have seen otherwise. Those weeks make the practice worth it.
Peer networks. Leadership is isolating. The higher you go, the fewer people you can be fully honest with inside your organisation. Peer networks — whether formal groups, trusted colleagues in other companies, or mentoring relationships — give you a space to think out loud without consequence. Some of the most important realisations I’ve had about my own leadership came from conversations with people who had no stake in my decisions but genuine interest in my development.
Feedback loops. Not annual 360 reviews. Ongoing, informal feedback from people you trust to be honest. I ask my team directly: what should I keep doing? What should I stop? What am I not seeing? Not everyone is comfortable answering honestly. But the ones who do give me the most valuable information I receive about my own leadership.
Reading widely. Not just leadership books — though some are genuinely useful. History. Psychology. Biography. Philosophy. Fiction. The leaders I admire most are broadly curious people. They draw connections from unexpected places. They bring perspectives that surprise their teams because they’re informed by more than just business thinking.
Teaching. I taught as an adjunct lecturer at ESB Business School for several years, and I can tell you that nothing clarifies your thinking like having to explain it to someone else. You discover what you actually understand and what you only thought you understood. You don’t need a classroom for this — mentoring, presenting, writing, or simply explaining your reasoning to your team all serve the same function.
Physical recovery. This sounds like it doesn’t belong here. It does. The leaders who sustain over decades are the ones who take care of themselves physically. Sleep. Exercise. Time away from work. Not as productivity hacks. As non-negotiable practices that make everything else possible. I learned this one the hard way, by ignoring it until my body forced the conversation.
Discomfort as a signal. This is perhaps the most important practice of all. Learning to treat discomfort not as something to avoid but as information. When a conversation makes you uncomfortable, that’s usually where the growth is. When a decision feels hard, that’s usually the decision that matters. When you’re tempted to avoid something, that’s usually the thing you most need to face.
None of these are revolutionary. None of them require special access or expensive programmes. They require consistency, honesty, and the willingness to keep developing even when you’ve reached a level where nobody expects you to.
The leaders who grow throughout their careers aren’t the ones with the most talent. They’re the ones who never stop treating their own development as seriously as they treat their team’s.
Where this all connects
This guide maps the journey. The individual articles go deep on each part of it.
If you’re at the beginning of the shift from expert to leader, start with the mid-career pivot. If you’re already leading and wondering whether you’re developing people or just managing them, building leaders, not just managing tasks will sharpen that question.
For the moments that test you most, leading through chaos offers a decision framework for uncertainty. For the influence challenge that never fully resolves, the influence without authority playbook gives you practical strategies.
For the longer arc — what you’re building that will outlast any single role — leading legacy is the most reflective thing I’ve written. And for the AI dimension that’s making all of this harder right now, leadership burnout in the AI era and emotional intelligence as AI’s counterweight address the exhaustion and the capability shift from different angles.
And if you’ve been doing the work without the title — managing the team, making the decisions, but still waiting for the recognition — [the economics of being almost promoted](/blog/the-economics-of-being-almost-promoted/) explores why that pattern exists and what it really costs.
The journey from expert to executive isn’t a single transition. It’s a series of them — each one uncomfortable, each one necessary, each one revealing something about what kind of leader you’re becoming.
I’m still on this journey myself. What I’ve written here isn’t from the other side of it. It’s from the middle. And I suspect the middle is where the most useful perspective lives — close enough to remember what the transition feels like, far enough along to see some patterns.
If any of this resonates, I’d be glad to hear about it. The conversation matters as much as the content.