There’s an assumption baked into how most people think about career readiness: that when you’re actually prepared for a bigger role, it will feel like it. The promotion will land, and something will settle—a sense of fit, of ease, of having arrived at a place that matches your capability. For a lot of genuinely capable, well-prepared people, that settling never quite comes, and the absence of it gets misread as evidence that the readiness itself was wrong. It usually isn’t. Readiness and comfort are simply not the same measurement, and expecting the first to produce the second sets up a disappointment that has nothing to do with actual capability.
Readiness is a claim about capability: you have the judgment, the experience, and the skill the role requires. Comfort is a claim about familiarity: this feels like something you’ve done before, in a form your nervous system already recognizes as safe. A genuinely new level of responsibility, by definition, involves stakes, visibility, and complexity you haven’t personally navigated yet—which means comfort, in the full sense, isn’t actually available yet, no matter how ready you are. It has to be built through the experience of doing the role, not verified in advance of taking it. Waiting to feel comfortable before believing you’re ready is waiting for a signal that structurally cannot arrive until after the fact.
When Discomfort Gets Misread as Unreadiness
This distinction matters because of what happens when it’s missed. A leader who equates discomfort with unreadiness starts treating every uneasy moment in a new role as disconfirming evidence—proof that maybe they weren’t actually prepared, that the promotion was premature, that the unease is a signal to pull back rather than a normal feature of operating at a genuinely new altitude. That reaction is understandable and it’s also exactly backwards. Discomfort in a new, larger role isn’t a sign of the wrong decision. It’s frequently the most reliable evidence available that the scope actually increased—that you’re doing something you haven’t fully done before, which is the entire point of the promotion in the first place.
Competence and Comfort Develop on Different Timelines
The version of this that shows up most often in senior leaders isn’t dramatic. It’s a low-grade, persistent sense of not quite having caught up to the role—a feeling that everyone else in the room is operating with more ease, more certainty, more natural authority, even months or years into a position that, by every external measure, is going well. That feeling can coexist for a surprisingly long time with genuinely strong performance, because comfort and competence develop on different timelines. Competence can arrive quickly, driven by preparation and transferable judgment. Comfort—the felt sense of this being normal, of belonging in the room without effort—often lags well behind it, sometimes by years, and there’s no shortcut that closes the gap faster than time and accumulated reps actually operating at the new level.
Comfort is a lagging indicator. It tells you almost nothing about whether you’re doing the job well right now.
Treat Discomfort as a Description, Not a Verdict
The more useful reframe, when the discomfort shows up, is to stop treating it as a question about your readiness and start treating it as a description of what the role currently requires: more tolerance for ambiguity than you’re used to carrying, more decisions made with less certainty than felt comfortable at the last level, more visibility on outcomes you can’t fully control. None of that is a verdict on whether you belong there. It’s simply what operating at a genuinely bigger scope feels like from the inside, for almost everyone, at almost every real step up—including the people in the room who look, from the outside, like they’ve never doubted themselves for a moment.
This doesn’t mean discomfort should always be dismissed or pushed through blindly—there’s a real difference between the productive discomfort of growing into scope and a genuine mismatch between a person and a role, and that distinction deserves honest examination, not automatic reassurance. But the way to tell the difference isn’t by checking whether the feeling of ease has arrived yet. It’s by checking whether your judgment is actually holding up under the new conditions—whether the decisions you’re making, uncomfortable as they may feel, are sound ones. Comfort is a lagging indicator. It tells you almost nothing about whether you’re doing the job well right now, only whether you’ve been doing it long enough to stop noticing the effort.
If you’re in a role that’s going well by every measure except how it feels, that gap is worth examining directly rather than treating as a quiet verdict on your fit. Explore coaching services.
Frequently asked questions
Does being ready for a role mean you’ll feel comfortable in it?
No. Readiness is about capability—judgment, experience, skill. Comfort is about familiarity. A genuinely bigger role involves stakes and complexity you haven’t fully navigated yet, so comfort can’t arrive before you’ve done the job.
Is discomfort in a new role a sign I wasn’t ready?
Usually not. Discomfort is often evidence the scope actually increased. Competence can arrive quickly; the felt sense of belonging often lags months or years. Treat unease as a description of new altitude, not a verdict on fit.
How do I tell productive discomfort from a real role mismatch?
Don’t wait for ease to arrive. Check whether your judgment is holding up—whether the decisions you’re making, uncomfortable as they feel, are sound. Comfort is a lagging indicator; it says little about whether you’re doing the job well right now.