Why Confidence Doesn’t Travel

Ever notice how you can deliver a flawless presentation at work… yet freeze when asked to tell a simple story in a social setting?

In this episode we explore a hidden truth: confidence doesn’t automatically transfer between situations.

You’ll learn why confidence doesn’t automatically transfer between situations and why that’s not a weakness but a roadmap for growth.

Through Tom’s story, a seasoned engineer who thrives in technical presentations but struggles in social storytelling, we explore the real reasons confidence stalls when the context changes:

• different threat profiles
• shifting social roles
• mismatched evidence
• uneven stakes

From there we introduce the confidence cycle:

Attempt → Experience → Reflect → Extract Evidence → Expand.

This simple loop allows confidence to grow in any domain.

You’ll also learn how confident people build transferable assets such as:

• pressure tolerance strategies
• recovery rituals after setbacks
• the identity of someone who builds confidence deliberately

Instead of trying to improve everything at once, we outline a practical roadmap:

Pick one domain for six months.
Run ten low-stakes attempts each month.
Keep a simple evidence log.
Maintain existing skills with minimum practice.

By the end of the episode you’ll have a clear way to grow confidence where it matters most right now.

Transcript

Why Confidence Fails To Transfer

Tom’s Story: Tech Pro, Social Beginner

Five Reasons Confidence Is Domain Specific

What Actually Transfers Across Domains

Entering New Domains Without Overwhelm

Serial Not Parallel: A Better Plan

Choosing And Tracking Your Domains

Timelines And A Five-Year Example

Key Takeaways And Next Challenge

Teaser For Confidence Crashes

SPEAKER_00 0:11

Let's talk about confidence. Episode 8: Confidence Across Life Domains, Transfer and Application. Welcome back to Let's Talk About Confidence. I'm John Emmalsh and over the past seven episodes, we've explored confidence in specific domains, sales confidence, leadership confidence, team confidence, and even confidence under pressure. But here's a question I get asked constantly. If I build confidence in one area of my life, will it transfer to others? And the answer is a wee bit more nuanced than most people expect. And understanding this nuance makes a massive difference in how you approach building confidence across your life. Today we're talking about what transfers and what doesn't, and how to build confidence in multiple areas without overwhelming yourself. Because here's what I've observed people often build strong confidence in one domain, say their professional expertise, their sport, their creative work, and assume that confidence will automatically show up everywhere else. Then they're confused and frustrated when it doesn't. The executive who's confident leading a company, but terrified of social situations. The athlete who's confident on the field, but struggles with public speaking. Or the engineer who's confident technically, but lacks confidence in relationships. This isn't unusual. This is how confidence actually works. Let me tell you about Tom's story. Tom was a senior software engineer, twenty years in the field, deeply confident in his technical domain. Give him a complex system to architect, he'd handle it calmly. Ask him to debug production issues under pressure, he'd execute that flawlessly. Put him in front of a technical audience, he'd explain concepts clearly. Then his wife asked him to speak at her company's charity event. Not technical. Just share their family story with volunteering. Just five minutes, informal audience. Tom froze, he couldn't do it. The confidence he had in technical contexts was completely absent. Even though he'd spoke to multiple audiences before about his technical expertise. He was confused. I can present technical content to hundreds of people. Why can't I speak at a small charity event? And here's why. This pattern's universal. Over the years I've seen the pattern thousands of times. It could be the surgeon that was confident in the operating theatre, terrified of public speaking. The teacher confident in the classroom, struggling with romantic relationships, the CEO who runs a 500-person company but can't set boundaries with her teenage daughter. Every single person has domains where confidence is high and domains where confidence is low. And this isn't inconsistency, it's just how confidence actually works. Confidence is domain specific. So why is confidence domain specific? Let's look at the reasons. Reason one, confidence is evidence based. We've talked about this before. Tom had 20 years of evidence, I can explain technical concepts clearly. He'd absolutely zero evidence, I can share personal stories in a social setting. Different evidence bases, different confidence levels, and you can't transfer evidence from one domain to another. Reason too is different domains activate different threat responses. Technical presenting activates certain concerns, will explain it clearly, can answer technical questions. Personal storytelling activates completely different concerns. Will people judge me personally? Will I be too emotional? Tom has evidence he can handle the first set of concerns, but no evidence for the second one. Reason three, skills don't equal confidence. Tom has got strong presentation skills. He knows how to structure content, use slides, use PowerPoint, engage audiences. Those skills exist. But skills without domain specific evidence don't produce confidence. You could teach someone every technical aspect of rock climbing. Would they feel confident in their first real climb? No. Confidence requires accumulated evidence through actual experience. Reason four is social context creates different pressures. In professional sense, Tom is an expert. His role provides authority and he's got expectations and they're clear. In personal storytelling, Tom is just Tom. There's no institutional authority. So there's a different level of vulnerability. Reason five, stakes feel different. Tom can fail technically, and it's professional, it's fixable. Personal storytelling feels like it exposes who he is. Failure feels more threatening to his identity. The research is clear confidence is not a general personality trait, it's a collection of domain-specific beliefs built through domain-specific evidence. So let's look at what transfers and what doesn't. Confidence itself doesn't transfer across domains, but some things do. So what transfers is a thing called meta-knowledge. Tom knows from technical presenting that confidence comes from repetition. Early attempts feel awkward, progress is invisible at first, and the middle bit is brutal but necessary. That meta-knowledge transfers, that bit transfers. It prevents him from misinterpreting difficulty as evidence he can't do it. The confidence cycle transfers. The process, have an attempt, have an experience of doing it, period of reflection, gather the evidence. As you've got the evidence, you increase capability, you have a bigger attempt. Works identically in any domain. The cycle transfers, the evidence doesn't. Tolerance for the boring middle bit. Tom's pushed through tedium in one domain. He's got evidence that pushing through works. Not confidence in the new domain, but confidence in the process. He knows he's going to have to go through that bit, and he knows he's going to want to give up, but he's going to push through because he knows that's how you learn it. Pressure tolerance strategies. So that physical preparation, recovery techniques, reframing pressure is challenged, not threat. These strategies work across domains. Identity as someone who builds confidence. Tom's built his confidence in multiple domains. He's evidence of his meta-capability. I can build confidence when I apply the process. That identity supports attempting new domains. The evidence doesn't transfer. Tom's 20 years of technical presenting evidence doesn't transfer to personal storytelling. Zero percent that evidence must be built from scratch. The feeling of confidence. Tom feels confident, presenting technical content. That feeling won't show up when he attempts personal storytelling. He'll feel exactly like a beginner because in that domain, he is. He's got no evidence. The capability. Tom can present technically content smoothly. That smooth execution won't show up initially. He'll stumble, you'll feel awkward. Different domain, different capability level. The practical implication is this. When entering a new confidence domain, expect to feel like a beginner. Early attempts to be awkward, and there's going to be a middle bit that will appear. But know this: the process works, the confidence cycle applies. You've done it before in other domains. And use a strategic framework for building confidence across multiple domains. Principle one is serial, not parallel. Most people try to build confidence multiple domains simultaneously. Work confidence, social confidence, creative confidence, physical confidence, all at once. This usually fails. You're managing four boring middle bits simultaneously. A better approach is serial development. Pick one of the domains as your primary focus. Build your foundation confidence there first. Then add a second domain. Tom approached it like this. In months one through six, he's personal storytelling confidence was his primary focus. He had 10 attempts per month. So he was practicing it, talking in front of others, talking in front of family, but he was practicing it so he could see how he started, how he continued, and how he finished. Months seven through twelve, he added social confidence. So he'd do five personal storytelling attempts per month, and five social confidence attempts per month. So he's building it and he's maintaining it. This prevents overwhelm while still progressing. Principle two is choose domains strategically. Don't pick domains randomly. Choose based on which domain would have would improve my life most right now. Which domain provides foundation for others you want to build later. And which domains are close enough that peripheral skills will transfer. Principle three is use the same process in every domain. The confidence cycle works identically across domains. Use it systematically in each one of them. Principle four is maintain while building. Once you've built foundation confidence in a domain, you don't need intense practice to maintain it. You need minimum viable practice. Tom's maintenance for technical presenting, he would do one presentation a month, probably down from weekly when he was building it. This maintains his neural pathways while freeing up capacity to build new domains. Principle five is leverage, what transfers. Before his first personal storytelling attempt, Trump tells himself I know the first attempts will be awkward. I've been through this before in technical presenting. It's not evidence I can't do it, it's evidence on building capability. That meta-knowledge makes the difficulty tolerable. Principle six, track across domains. Keep separate evidence logs for each domain. This prevents confusion and maintains clarity. Based on working with thousands of people over the years, here are the six major life domains where most people want confidence. Professional domain, your work, your career, your technical expertise. Number one. Number two is leadership domain, managing, influencing, delegating, handling conflict. Number three is your social domain, having conversations and relationships, networking. Number four is your creative domain. It could be expression or innovation or art or writing. And number five is physical domain. Your sport, fitness, physical challenges. With number six, the personal domain, all about your values, difficult life decisions, your identity. And most people want confidence in three to four of these domains. Building all six to high levels just takes time and that's fine. You don't need high confidence in all domains simultaneously. You need that strategic development over time. A realistic timeline for this would be foundation confidence, one domain, somewhere around the six-month mark. Foundation confidence in three domains might take you a bit longer, could be within a year, could be two years. Everybody's different, but it's the process is the same. Application level confidence when you know it and you can execute it under pressure, that might take you a couple of years. Tom's got a five-year plan. Year one, he's going to do the personal storytelling confidence. He's going to build a foundation in that. Year two, he's going for social confidence, and he's got personal storytelling, so he'll still do it, but he'll be applying it as opposed to building it. Year three, romantic confidence, building a foundation of that. Social confidence again he'll be applying, he'll still be keeping the neural pathways open. And then he's years four to five, he'll deepen application level confidence across all three domains. So he'll be able to be storytelling, social confidence, romantic confidence, you'll be at a high level on all of those, and he can manage them under pressure as well. That's what he's aiming to get to. Five years sounds like a long time, but Tom's only 35. Five years will be 40. The time will pass anyway. The question is whether he'll have built confidence across domains or still be wishing he had. Confidence is domain specific. You can have high confidence one area and low confidence another. This isn't inconsistent, it's just how confidence works. Confidence itself doesn't transfer across domains, but your meta-knowledge of confidence does. The confidence cycle process, pressure tolerance strategies, and identity as someone who builds confidence. These do transfer. Building confidence across multiple domains requires serial development, strategic domain selection. Choose the ones that you want to apply first. The same process in each domain, but remember to track them separately so you can see the evidence as it builds. Timelines, typically foundation confidence in three domains, might take you a year, might be two years, and it's of serial development. But everybody's different, everybody applies themselves differently to it. Again, this might seem long, but the alternative is wishing you had confidence without building it. Building confidence can take your entire life, but you'll get there. But you gotta start. So here's your challenge. Assess what domain do you want confidence in most? Which one have you already got? Which ones do you want to develop? And pick one. What one would most improve your life right now? And then start by applying a confidence cycle. Ten attempts this month, make them low stack low stakes and track them. Don't try to build confidence in four domains simultaneously. You will fall over. It's too much. Pick one, build your foundation, then add another. In the next episode, our final episode, we're talking about what happens when confidence crashes. When you've built confidence and then something happens that undermines it. How to protect your confidence, how to rebuild it when it's damaged. That's what we'll talk about next time. But for now, remember this confidence is domain specific. You can't borrow it from one domain to use another, but you can use the same process to build it in any domain. One domain at a time, one attempt at a time, one piece of evidence at a time. That's how confidence is built across life domains. I'm John M. Walsh. This is Let's Talk About Confidence, and I'll see you in episode nine.