Capability vs. Availability: Why "I Can" Doesn't Mean "I Should"

You know how to do the job. That's not the question.

The question is whether you have the internal resources to do it right now - and whether doing it costs you something you can't afford to spend.

This is the difference between capability and availability.

Capability is your skill set. It's what you've proven you can do. It's the résumé, the track record, the evidence that you know how to deliver.

Availability is your current capacity. It's what you actually have to give today, this week, this month. It's the bandwidth that's left after you account for recovery, rest, and the energy it takes just to show up.

Burnout happens when you keep spending from availability based on capability. When you say yes because you can do it, not because you have the resources to do it. When "I know how to handle this" becomes the reason you take it on, even when your body is telling you to stop.

The capability trap

Here's what that looked like for me in IT:

Someone would escalate an issue. I knew how to fix it. I'd done it a hundred times. So I'd take it on - because capability said I could.

What I didn't account for: I was already running on fumes. I hadn't slept well in weeks. I was irritable, exhausted, and one more emergency away from breaking. But I said yes anyway, because capability doesn't ask about availability.

Capability is loud. It's confident. It says, "You've got this."

Availability is quieter. It's the tightness in your chest, the exhaustion that rest doesn't fix, the growing sense that you're running on reserves you don't actually have.

And if you're used to measuring yourself by capability - by what you can deliver, what you've proven, what you're known for - availability feels like weakness. Like you're failing. Like you should just push through.

But availability isn't weakness. It's information.

What availability actually means

Availability doesn't mean you're not capable anymore. It means your system is telling you it needs something before you take on more.

Maybe it's rest. Maybe it's space to think. Maybe it's time to process what you've already been through instead of adding the next thing.

Capability will tell you what you're able to do.

Availability tells you what you're able to do without breaking something that matters.

And if you're recovering from burnout, that distinction isn't optional. It's the whole point.

How to tell the difference

When someone asks you to take something on, here's the check:

Capability question: Can I do this? Do I know how?

Availability question: Do I have what it takes to do this well right now, without depleting something I can't afford to lose?

If the answer to the first question is yes and the second is no, that's not a failure. That's information. And honoring that information is how you stop capability from draining availability until there's nothing left.

What this looks like in practice

You might turn down a project you're perfectly qualified for because you know taking it on would cost you more than you have to spend.

You might ask for more time, even though you could technically deliver faster.

You might say, "I can do this, but not right now," and mean it without apology.

None of that means you're less capable. It means you're paying attention to what's actually available - and that's a skill most people don't develop until they've already burned out.

If you're recovering, you're learning to ask a different question. Not "can I do this?" but "do I have what I need to do this without breaking something I'm trying to rebuild?"

That's not weakness. That's wisdom.