Why Confidence Collapses After Promotion

Promotions can feel like a reward and a reset button at the same time. One day you’re the go-to expert; the next you’re leading experts — and the habits that made you successful suddenly stop working.

In this episode, we unpack why the expert-to-leader transition is so destabilising, and how to replace anxiety with evidence.

Using Kate’s story — a top structural engineer promoted into leadership — we identify three forces that make this leap brutal: confidence that doesn’t transfer, success behaviours that backfire, and zero transition time. From there, we surface five confidence gaps that stall new managers: delegation, difficult conversations, decisions under uncertainty, saying “I don’t know,” and trusting the team.

You’ll then hear a practical six-month framework for rebuilding leadership confidence through deliberate reps: low-stakes delegation, honest feedback, 80% decisions, visible uncertainty, and hands-off ownership — all tracked through an evidence log that turns fear into facts.

By the end, you’ll have a clear blueprint for converting theory into behaviour and behaviour into results — and a way to recognise what “normal struggle” looks like as confidence rebuilds.

If you lead experts, coach new managers, or are navigating this transition yourself, this episode will give you calm, clarity, and a path forward.

Transcript

Why Technical Confidence Doesn’t Transfer

Kate’s Promotion And Pain Point

The Three Colliding Forces

Five Leadership Confidence Gaps

Six-Month Evidence-Building Framework

Kate’s Results And Turnaround

Phases Of Building Confidence

Assess, Practice, And Support New Leaders

Closing And Next Topic Preview

SPEAKER_00 0:11

Let's talk about confidence. Episode 7, Leadership Confidence, the technical expert to leader transition. Welcome back to Let's Talk About Confidence. I'm John M. Malsh and today we're talking about one of the most challenging confidence transitions I see. It's that subject matter or technical expert to leader. Over the years I've been lucky enough to work with thousands of experts who became managers, engineers, accountants, scientists, IT professionals, finance specialists, all brilliant people, competent in their technical domain, promoted because they were excellent at their technical work. And then they struggle. Not because they're incapable, but because technical confidence and leadership confidence are two completely different things. Here's what makes the transition brutal. You've spent years building confidence in your technical domain, thousands of problems solved, deep expertise and recognition from your peers. Then you become a leader, and everything resets to zero. You're in a new domain with new challenges, the behaviors that made you successful technically, now actively sabotage your leadership, and no one prepared you for this. I want to talk about Kate's story. Kate was the best structural engineer on the team. She's a brilliant technical mind. She solved problems others couldn't even see, and clients asked for her specifically. So naturally, when a team leader position opened, she got promoted. Six months later she was miserable. The team was underperforming, and everybody was confused about what went wrong. Kate had technical confidence, but she had zero leadership confidence, and no one prepared her for this. They assumed her technical competence would transfer to leadership, and it didn't. The transition from expert to leader creates what I call the perfect storm. There's three forces that collide. Force number one is a competence without confidence. As a technical expert, Kate built confidence over the years through thousands of problems solved. Then she became a leader, and everything resets to zero. Imagine you're an accomplished pianist with 10,000 hours of practice, then someone says, Hey great, you're now the conductor. You don't have conductor confidence just because you've been a pianist and you've had confidence in that. That's what happens when technical experts become leaders. It's a different instrument, no practice and no confidence. Researchers call this domain-specific confidence, and it doesn't transfer automatically. It has to be rebuilt. Force two is the behaviours that made you successful now hold you back. Kate's technical success came from solving problems herself. High personal standards and independence and deep focus. These same behaviors sabotage leadership, solving problems herself, micromanagement. The team members don't develop. High personal standards, bottleneck, nothing's ever good enough to delegate. Independence, it's like isolation and she's not building relationships. And the deep focus, it's missing the people issues and not seeing the team dynamics. The behavior that built technical confidence actively undermines your leadership effectiveness. Force three is there's no time to build confidence. Most organizations give technical experts zero transition time. Friday, you're the best engineer. Monday, you're leading engineers, good luck. No apprenticeship, no low stakes practice, no gradual progression. Research shows that 58% of new managers receive no management training before taking on the role, and about 60% of first-time managers fail within the first 24 months. And it's not because they're incompetent, it's because they're competent in the wrong domain. There's five confidence gaps, and leadership requires five specific types of confidence. Technical experts typically have none of these when they start. Gap one is delegation. Delegation confidence is evidence you can hand work to others and it'll get done adequately. Not perfectly, adequately. Why experts lack this is they've had ten years of evidence that doing it themselves produces better results and it's faster. They've got zero evidence that delegating produces acceptable results. Kate's got a complex technical problem, she could solve it in three hours. Her team member could probably solve it in eight hours with some mistakes. The leadership behaviour is delegate it. The confidence gap says, but I know I can do it better and faster, and what if they mess up? We haven't got time for that. What happens? Kate solves it herself again, the team member doesn't develop, and Kate gets overwhelmed. Gap two is the difficult conversations. Difficult conversation confidence is evidence you can address underperformance without destroying a relationship. Why experts lack this? Because technical work involves problems, not people. They've spent years building confidence solving technical problems, and zero years navigating interpersonal difficulty. Team member consistently missing deadlines impacts the whole team. The leadership behavior, have a direct conversation. The confidence gap. What if they get defensive? What if they quit? So what happens? Kate drops hints, hopes he'll improve, but the problem just continues. Gap three is decisions under uncertainty. Decision confidence is evidence you can decide without certainty and adjust if it's wrong. And why experts lack this is technical decisions have right answers. You gather data until you're certain. Leadership decisions don't have right answers. You decide with incomplete information. Client requesting a scope change, incomplete information, there's no clear right answer. The leadership behaviour, make the call and adjust it if you need it. The confidence gap, but I don't have enough data. Shouldn't we analyse this more? What happens? Kate gathers more data, schedulings, delays decisions, client gets frustrated. Gap four, not having all the answers. I don't know confidence is evidence. You could admit uncertainty without undermining your authority. And again why experts like this is technical credibility comes from having answers. They've built their career in being the smartest person in the room, technically. Team member asks Kate about organizational politics. Kate's no idea. The leadership behaviour, I don't know, but let's figure it out together. The confidence gap, if I admit I don't know, they won't respect me. What happens? Kate fakes an answer or deflects. Team member doesn't get help. Kate feels like a fraud. Gap five is trust in the team. Trust confidence is evidence the team can succeed without your constant involvement. Why experts like this? Their confidence is based on their own capability. They know evidence the team is capable. Kate assigns work but then hovers, checks work multiple times, redoes parts she's not satisfied with, their leadership behaviours give ownership and trust the team to deliver. The confidence gap, if I don't oversee it closely, it won't get done right. What happens? Team members feel micromanaged, they lose motivation, and they stop taking the initiative. These aren't skill gaps. Kate knows theoretically how to delegate, how to have difficult conversations, how to make decisions, how to say I don't know and trust. She's been through management training, she's read the books, but understanding the concepts doesn't give you the confidence to execute them under pressure. They're confidence gaps, not knowledge gaps. And confidence gaps are only closed through one method only: accumulated evidence through repeated practice. Building the leadership confidence, we're going to look at a six-month framework. Again, people go through different phases, but building that confidence requires the same process you've used to build your technical confidence. Systematic practice accumulates evidence. So month one would look like building delegation confidence. Start small, delegate one straightforward task. Nothing on the critical path and something that's low stakes. The goal is ten delegations attempted this month. Track it. Did you delegate? Not did they do it perfectly. Just track the action. After ten delegations, you've got ten pieces of evidence. Delegated ten tasks, eight were completed adequately. Nothing's perfect. Two needed rework, but they weren't disasters. That's delegation confidence beginning. Month two might be build difficult conversation confidence. Start small, give one piece of developmental feedback, not performance management, not high stakes. The goal could be five feedback conversations this month and track it. Did you have the conversations? Not did they change immediately. After five conversations, nobody collapsed, all relationships survived. Two people actually thanked me for the honesty. That's difficult conversation confidence beginning. Month three build decision making confidence. Again, start small. Make one decision with 80% information, not 100%, something with manageable consequences if it's wrong. The goal is ten decisions this month. Track it. Did you decide within 24 hours? And after 10 decisions, seven worked really well. Two needed adjustment, and one was flat wrong. But recoverable. I dec I learned to decide and iterate. That's decision making confidence beginning. Month four build I don't know confidence. Next time you don't know something, say I don't know. Let me find out the answer. Let's figure it out together. The goal is five I don't know moments this month. Track did you admit not knowing? After five moments, people still respected me. Three people specifically appreciated the honesty. That's I don't know confidence beginning. Month five is build the trust and the team confidence. Start small. Give one team member ownership of a project. Not your most critical project, moderate stakes, remember. Don't hover, check in weekly, not daily. The goal for this is three hands-off ownership projects this month. Track it, did you avoid micromanaging? After three projects, all three were completed. Not exactly how I'd have done them, but adequately. One case was actually better than my approach. That's trust confidence beginning. And month six, the progressive challenge. Now increase the difficulty in each domain, delegate more complex tasks, have more difficult conversations, make bigger decisions, and trust the team with higher stakes. It's the same process, same tracking, just higher stakes. In that first year, by month 12, you'll have followed this framework. You'll have something like, say, 60 delegations logged, 30 difficult conversations, 80 decisions under uncertainty, 20 I don't know moments, 15 hands-off projects. That's accumulated evidence across all five leadership confidence domains. Now you have leadership confidence, not because you read about leadership, because you have evidence you can execute leadership behaviours under real conditions. Kate implemented this framework starting in month seven of her leadership role. Month seven through eight, twenty five delegations, our evidence log, team delivered adequately, twenty-two out of twenty-five times. Months nine through ten, fifteen developmental and performance conversations, our evidence log read no one quit. Relationships actually improved through honesty. She weren't expecting that. Months 11 through 12, 40 decisions with 70 to 80% information, so a fair amount of uncertainty. The evidence log 28 worked well, 8 needed adjustment, 4 were wrong but recoverable. The result is by 18 months for Kate, the team performance improved dramatically. Kate working 45 hour weeks, not 60, and the team members felt like they were developing rapidly. The big shift from faking leadership confidence to having evidence-based leadership confidence. Let me be honest about what this journey looks like. The timing will vary, the numbers will change, but the pattern's consistent. It starts with the foundation phase. Everything feels effortful. Each delegation requires conscious thought. You question whether you cut out for leadership, and that's normal. You're building new neural pathways. Remember that. You can't see them, but you're building them. The struggle phase, this is a leadership's middle bit where you're practicing consistently, but behaviors aren't getting noticeably easier. You will want to quit. Don't quit, do not quit. This is where your leadership confidence is actually built. Then you move into the emergence phase, you'll see small shifts become noticeable. Delegating might feel slightly more natural because the evidence in your logs starts to matter. The foundation confidence phase, you can execute basic leadership behaviours consistently without overwhelming anxiety. Not effortless yet, but accessible under normal conditions. The application phase, you're adapting your leadership approach to different contexts. The team trusts you as a leader, and you trust yourself. How long does it take? It varies. But the pattern's consistent. You'll move through these phases if you practice systematically. Experts struggle as leaders not because they're incompetent, because they're competent in the wrong domain. They've got deep technical confidence, they've zero leadership confidence. And no one teaches them that leadership confidence is built the same way technical confidence was through systematic practice that accumulates evidence. If you're a new leader, assess this. Which of the five confidence gaps is causing me the most difficulty at the moment? Pick one. Just one. And this month practice that behavior ten times. Small, low stakes, attract them, build evidence. If you're leading someone transitioning from technical expert to leader, recognise they don't need more management training on concepts. They need systematic confidence built through practice. Give them permission to be beginners, create low stakes practice opportunities and celebrate attempts, not just outcomes. The next episode we'll be talking about confidence across life domains. How does confidence in one area relate to confidence in another? Does it transfer? We'll talk about that next time. But for now, remember this leadership confidence isn't about charisma or natural leadership ability. It's about systematic practice, building evidence in five critical domains, one attempt at a time, one piece of evidence at a time, one domain at a time. That's how technical experts become confident leaders. I'm John M. Walsh. This is Let's Talk About Confidence, and I'll see you in episode eight.