The Incomplete Script

Reflections on burnout, disillusionment, and questioning the stories we were told

A publication of first-person essays naming what work feels like — without hero framing. These are lived reflections, not advice.

Empty office conference table with notebook, papers, and laptop in a subdued modern workplace

How I Got Tired of Covering for Incompetence





At first, covering for others felt supportive — now it feels like absorbing avoidable pressure.

I used to think covering for others was part of being a good coworker. If someone missed a detail, I’d catch it. If someone misunderstood a requirement, I’d reinterpret it for them. If someone struggled to meet a deadline, I’d help make it happen without anyone noticing the gap. And for a long time, that felt normal — even generous.

But there came a point when that pattern stopped feeling like generosity and began feeling like obligation: a quiet assumption that *if someone can’t do it well, I will*. Not because I was asked explicitly, but because over time I learned that no one else *would* do it well unless I did. That realization didn’t arrive in a dramatic moment — it crept in through countless small shifts in my internal experience of responsibility and workload.

There were times when I covered for someone’s mistake or misunderstanding and everything turned out fine. The work was delivered. The problem didn’t become visible. I told myself that was the point of teamwork — to support each other and ensure things didn’t break. But what I didn’t notice at first was how often this pattern repeated itself without acknowledgment of the underlying cause.

This experience connects to something I described in what it’s like when you’re always cleaning up other people’s mistakes. Covering for incompetence isn’t just about fixing errors. It’s about absorbing the emotional and logistical cost of issues that others either didn’t anticipate or didn’t address themselves.

At first, I took pride in being able to step in where needed. I valued the smooth outcome that came from quietly absorbing a gap. But as this became a recurring pattern, something subtle began to shift inside me: I started to notice a kind of weariness that wasn’t tied to the volume of tasks, but to the *implicit erosion of boundaries* around what I was expected to handle.

There were moments when covering for others became so habitual that I scarcely noticed I was doing it until I felt the internal fatigue afterward — that quiet sense of having given energy not just to the work itself, but to compensating for an avoidable gap in someone else’s contribution. It wasn’t anger. It wasn’t impatience. It was a kind of internal depletion that I didn’t initially recognize as meaningful because it wasn’t dramatic.

What made it difficult to see at first was how normalized the behavior felt. When you’re in the rhythm of stepping in to solve problems, stepping in to clarify misunderstandings, stepping in to meet expectations that others haven’t met, it feels like part of being a responsible team member. It feels like being dependable. And being dependable *is* valuable. But there’s a difference between being dependable and being the default safety net for others who habitually don’t carry their portion of responsibility.

This difference shifted my internal sense of participation in work. I began to notice that covering for incompetence wasn’t just extra effort — it was extra effort *without contextual support*. No one ever said, “Please fill this gap because it’s yours.” Instead, it was assumed. Gaps were left unattended, and I stepped into them because I saw them and could address them. The absence of explicit direction made the cost feel quietly personal — as if the responsibility to compensate was something I’d borne by default rather than by design.

And there’s a quality to that kind of pattern that doesn’t feel dramatic or explosive. It feels like constant, low‑grade tension: the feeling that no matter how much you complete, there’s always another gap waiting because someone else didn’t handle theirs. That pattern eventually reshapes your experience of what it means to be a contributor — not in terms of how competent you are, but in terms of how necessary it feels to *fix rather than build.*

Over time, I began to notice subtle internal questions before doing tasks: *Am I actually advancing this project? Or am I just patching someone else’s omission?* The question itself didn’t feel accusatory. It felt exploratory, like trying to understand why I was doing the work and whether it actually belonged to the work or to the unseen consequences of someone else’s lack of preparation.

Eventually, I saw that this pattern didn’t just affect my workload. It affected how I felt when tasks were completed. When I finished something that required covering for someone else’s gap, the sense of relief wasn’t the same as when I completed something I owned. The relief was wrapped in the quiet awareness that I was once again the one making sure something didn’t fall apart — without it being anyone’s responsibility to *make sure it worked in the first place.*

Covering for incompetence doesn’t feel like teamwork — it feels like carrying the weight of what others would rather not face.

That shift changed how I experienced work. I didn’t stop being helpful. I didn’t stop caring about outcomes. But I became more aware of how much of my mental energy was tied up not in advancing the work itself, but in compensating for the parts of it that others let slip. And that’s a quiet form of drain, because it doesn’t announce itself as additional tasks. It feels like *extra cognitive and emotional space* taken up by consequences that ought to have been avoided or addressed by someone else.

At first I didn’t talk about this to others. It didn’t feel like a complaint. It felt like observation — something internal I was noticing about how I experienced certain tasks differently from others. It wasn’t that I didn’t value being capable. It was that I began to see how often my capability was invoked not for building something forward, but for repairing what had already faltered.

It subtly changed my relationship to contribution. Instead of feeling like part of a forward motion, I started to feel like part of a *maintenance cycle* — constantly attending to the cracks that never seem to get fixed on their own. That’s not work refusing to move ahead. It’s work that has no buffer for the consequences of error or oversight.

And while you can operate in that space for a long time, it slowly reshapes how you understand presence, engagement, and responsibility. You begin to see that covering for others isn’t just extra labor. It’s a kind of *interstitial work* that sits between what was planned and what was actually executed, between what was promised and what was delivered — and no one else seems to hold that space except you.

This isn’t about judging others. It’s about noticing what it feels like to be the one habitually holding the gaps that others leave behind. It’s a soft kind of exhaustion, not dramatic or overwhelming, but persistent and quietly cumulative: the experience of smoothing the unseen edges so the work appears seamless to everyone else.

That’s how I got tired of covering for incompetence — not because I couldn’t do it, but because I began to notice how much of my internal space it was taking up without ever being acknowledged as real work in the first place.

Covering for incompetence doesn’t feel like support — it feels like absorbing responsibility that was never meant to be yours.

Leave a Reply

Your email address will not be published. Required fields are marked *