The Two-Year Badge: Why You Overstay a Role You've Outgrown

You knew within the first year. Maybe less. The mission that got you in the door had shifted, or the role had narrowed into something smaller than what you signed up for, or the culture just wasn't what it was when you joined. You noticed. And you stayed anyway.

Sometimes it's the mission, you're hoping it comes back, that the thing that made you say yes in the first place will resurface if you just wait it out. Sometimes, it's the belief that the situation will improve on its own, that the current friction is temporary. And sometimes it's more subtle: if I leave now, it looks bad on my CV. I need to hit two years. Three, if I want the next title to make sense. Different stories, same move.

Whatever the reason you're telling yourself, you're not staying for what's actually in front of you. You're staying for a version of this that only exists later, one where it worked out, or looked right, or made sense in hindsight.

It feels like a strategic call. It's actually a transfer of power. You're handing the decision to a future version of you, the one explaining this job in an interview eighteen months from now, instead of making the decision as the person who's actually living it today. Present-you, with full information about how misaligned this has become, gets overruled by a hypothetical future-you who needs the timeline to look clean. Meanwhile, the plan backfires on its own terms.

In my work with operators, I see this pattern all the time. Once someone is staying for the optic rather than the work, they check out. Slowly at first. Showing up, doing the job, but not fully in it. That shift is visible. Performance dips. They get passed over for the stretch project, then the promotion, because the manager one desk over can tell they've stopped fighting for the role. Bitterness sets in, because now they're contributing less and getting less back, and neither is a mystery to them. And often it ends in exactly the kind of exit they were trying to prevent. A departure that reads as someone who burned out or lost their edge, rather than someone who made a clean, timely call.

There's also a cost that's harder to point to on a timeline: the year or two spent inside a role that had already stopped teaching them anything. Time that could have gone somewhere else, spent instead on protecting a narrative about the past instead of building toward what's next.

The way through isn't a bigger vision of the future. It's a sharper, more honest look at the present.

When I work through this with an operator, we don't start by imagining the exit interview or the next CV line. We build an honest description of where they are right now. The actual culture, the actual scope of the role, what they're learning this quarter versus what they thought they'd be learning, what they actually need next. Then we hand the decision to the person standing in that present context. Not future-them, walking backward from a story they'd like to be able to tell. Present-them, walking forward from what's true today.

That question is uncomfortable in a way the CV-timeline question never is, because it can't hide behind a plan. It just asks: given everything you know right now, is this still where you'd choose to be? If the honest answer is no, the two-year mark doesn't change that. It just delays it, and adds interest.

If you're an operator sitting somewhere that stopped being right a while ago, the badge you're protecting isn't as durable as it feels. The version of you living it now knows more about whether it's working than the version of you explaining it later ever will.

If this feels like your situation, schedule a free clarity call to talk it through.