I cried for two minutes before work last month.

Not the kind of crying that builds - the kind that just happens. I was getting ready, and suddenly I wasn't. I was standing there, crying about all of it. The projects that weren't mine. The deadlines stacking up. The work I actually wanted to do happening in my "free time" because my official job kept expanding.

Two minutes. Then I stopped, got back to it, and went to work.

That's the thing about the capability trap. Your body tries to tell you something. You override it. And you keep going because you're good at this.

How competence becomes obligation

Here's how it works:

You see something being done badly. It's absurd to you - maybe because you've worked at companies with more mature processes, maybe because you just have a clearer sense of how things should function.

You speak up.

And here's where it gets you: you don't want to be the person who just complains without offering solutions. So you suggest a better way. You share what you know. You offer to help.

And now it's yours.

Not because anyone forced it on you. Because you're capable, and you care about outcomes, and you're proactive. That combination is a magnet for responsibility.

The pattern is simple:

Competence + caring + initiative = automatic ownership

You get known for stepping in. People start assuming you'll handle things. And you do, because you can.

This isn't just how it feels - it's how organizations actually function. When your skills are visible and your competence is proven, managers treat that visibility as a resource allocation signal. Your capability becomes the organization's informal staffing solution.

The mechanism is predictable: competence creates visibility, visibility creates requests, and the cycle compounds.

Why this feels good (at first)

Let's be honest: it works.

People need you. You're visible. You're the person with solutions. You're contributing to things that matter, often things with real impact on work you actually care about.

There's pride in that. Validation. Proof that you're capable. Excitement when new projects come your way.

Being necessary feels like success.

You're not just doing your job –⁠⁠⁠⁠⁠⁠ you're solving problems across teams, owning initiatives that matter, building things that didn't exist before. You're known. That visibility means something.

It feels like you're building toward something.

And you are. Just not what you thought.

The cost compounds slowly

You don't notice the shift at first. There's no single moment where it tips. It's just that somewhere along the way, the math stopped working.

You're doing two jobs. Maybe more. The work that's officially yours still has to get done. It still has deadlines.

Maybe you enjoy parts of your official role. Maybe you don't. Either way, there's only so many hours in the day, and the work you've absorbed doesn't disappear just because your job description didn't include it.

So it happens whenever you can fit it in. Early mornings. Evenings. Weekends.

And when a deadline comes - for any of it - something has to give.

The gym membership you're still paying for but haven't used in weeks. The meal prep you planned on Sunday that turned into takeout by Tuesday. The book on your nightstand that's been on the same page for a month. Sleep that leaves you functional but not actually rested.

You have the capacity for work or the capacity for life. Rarely both at the same time.

Here's what's particularly cruel: it's not the struggling employees who end up here. It’s the high performers - the capable, conscientious ones - who are at greatest risk. Not because they can't handle the work, but because the very traits that make them successful (high standards, emotional investment, reliability) are the same ones that make them vulnerable to depletion.

Researchers call it the "overcommitment trap." You take on more because saying no feels like admitting you can't handle it. You protect your reputation by absorbing work, which just signals that you have more capacity, which brings more work. Competence doesn't earn you ease - it earns you more responsibility.

You wake up early - not because you want to, but because your brain is already running through what you didn't do yesterday and what's coming today. The mental buzz doesn't stop. Even when you're technically off, you're not off.

There's a cost to the constant override, too. The gap between what you're actually feeling (exhausted, resentful, unsustainable) and what you're projecting (capable, reliable, fine) doesn't just disappear. That dissonance compounds quietly - your body keeps score even when you're ignoring it.

And there's a version of this thought that shows up eventually, in different forms:

What would happen if I just... stopped?

Followed quickly by: This can't be what the rest of my career looks like.

Why "just say no" doesn't work

You've heard the advice. Set boundaries. Learn to say no. Protect your time.

Great. Tried that. Now what?

Here's what happens when you don't step in:

The work either doesn't get done, or it gets done badly. Maybe that means a project fails. Maybe it means someone else struggles with something you could have handled easily. Maybe it means outcomes you care about suffer. Maybe it just sits there, unfinished, bothering you.

You care too much to watch things fall apart when you know you could fix them.

And here's the structural problem: the system that created this situation can't fix it by you saying no.

Maybe your manager agrees you should be doing different work, or higher-level work, but the promotion process moves slowly. Maybe the company is genuinely understaffed and there's no one else to hand things to. Maybe the culture rewards being responsive and visible, so declining requests feels like opting out of advancement.

Most boundary advice assumes your individual choices can override organizational dysfunction. But that boundary-setting only works when the system supports it - when managers respect limits, when workloads are actually reasonable, when declining work doesn't mean watching critical projects fail or colleagues struggle.

In understaffed, high-pressure environments where competent people are stretched across multiple roles, individual boundaries can't fix what's fundamentally a resourcing problem.

Whatever the specifics, the pattern is the same: the system needs you to keep absorbing things. And saying no doesn't change the system - it just makes you watch it strain under the weight you're no longer carrying.

The questions that actually matter

Let's do some math.

You've been visible for how long now? Two years? Three? You've been the reliable one, the person who steps in, the one with solutions. You've been known.

So: what has that actually gotten you?

Not what it might get you someday. What has it gotten you so far?

A promotion? A raise that reflects the three jobs you're doing? The authority to match the responsibility you've already absorbed? The ability to do work you love without also doing everything else that landed on you?

Or just... more work?

Here's the uncomfortable question: Is being indispensable the same as being valued?

Because right now, it looks like being indispensable has made you stuck. The very thing that was supposed to build your career has locked you in place. You can't be promoted –⁠⁠⁠⁠⁠⁠ who would do all the things you do? You can't slow down –⁠⁠⁠⁠⁠⁠ everything would fall apart. You can't leave –⁠⁠⁠⁠⁠⁠ you care too much about the outcomes.

Being necessary was supposed to be leverage. Instead, it's a cage.

And maybe the worst part: some of the extra work is stuff you'd actually want to do. Work that excites you. Work you'd happily take on –⁠⁠⁠⁠⁠⁠ if it came with the role and authority that matched. If you weren't also carrying everything else. If being good at it didn't just mean it's yours now, forever, on top of everything else.

So here's what I want you to sit with:

What would it look like if being good at something created options instead of obligations?

You've probably felt that before –⁠⁠⁠⁠⁠⁠ a job or project where being proactive felt energizing, not draining. Where you were still a high performer, but you weren't running on fumes. Where the difference wasn't your effort or your standards.

The difference was the system. Not you.

What actually changes this

Let's be clear about what this isn't: a willpower problem.

You have plenty of willpower. That's how you've kept going this long. You've been running on willpower, caffeine, and the faint hope that eventually it'll get better. Willpower isn't what's broken.

The system is.

And individual solutions can't fix structural problems. You can't boundary your way out of understaffing. You can't mindset-hack your way out of doing three jobs. You can't self-care your way out of a workload that was never designed to fit into working hours.

So here's what actually has to shift:

Time. Not "better time management." Actual time. Enough hours to do your real job well, during normal working hours, without everything else bleeding into your evenings and weekends. If the only way to meet expectations is to sacrifice sleep, exercise, and sanity, the expectations are wrong. Not you.

Authority. If you're already doing the work, you need the role that matches. Not "eventually." Not "when there's budget." Not as a reward for enduring another six months of an impossible situation. The promotion isn't a prize for surviving –⁠⁠⁠⁠⁠⁠ it's the correction for a scope that already expanded.

Clarity. What's actually yours versus what you've absorbed by default? Some of the extra work might genuinely excite you. But if you can't tell the difference between what you chose and what just landed on you, everything feels mandatory. That ambiguity is expensive.

Recovery. Built in before you break. Not earned by finishing everything first. Not a reward for hitting some imaginary milestone. Scheduled, protected, and non-negotiable –⁠⁠⁠⁠⁠⁠ because the current pattern is work-until-depletion, recover barely enough to function, repeat. That's not sustainability. That's slow collapse with extra steps.

None of this is abstract. These are specific conversations. Role redefinitions. Explicit tradeoffs. Responsibilities that get sunset instead of just piling up. Promotions tied to work you're already doing, not work you might do if you prove yourself for another year.

Hard conversations. But clearer than the alternative, which is: keep absorbing everything until something breaks.

The trap isn't about doing less

Here's the thing: you don't want to do less meaningful work. You want to do work that matters without sacrificing your entire life to it.

You want to be good at things without that competence becoming an open invitation. To contribute without being the person everyone assumes will step in –⁠⁠⁠⁠⁠⁠ not because you chose to, but because you can. To have your capability create options, not obligations.

The capability trap isn't about lowering your standards or caring less. It's about designing a life where being good at something doesn't mean you're required to do everything.

You stopped crying after two minutes and went to work.

Because that's what you do. Because you're good at this.

But here's the thing about being good at overriding yourself: it works. It works because the mechanism is invisible. Once you can see it, you can start to interrupt it.

Your competence is real. Your capacity is not infinite. One of those is a skill. The other is a structural fact.

Maybe it's time to stop treating the second one like a personal failing.

Discussion

or to participate

Keep Reading

No posts found