What It Feels Like to Never Know If You’re Doing Enough

There was a time when finishing a task meant something settled inside me — like closing a loop and setting it down. But over time, that sensation dissolved. I’d complete something and then wait, somewhere in the background of my thoughts, for the next judgment on whether it was enough, whether it was good enough, whether it even met the silent standards that had been applied in similar moments before.

This didn’t arrive with a single moment of failure or critique. It arrived as a small shift, almost imperceptible: I finished something, and then instead of relief I felt… pause. Like I was waiting for a response that didn’t quite arrive. Like someone was silently checking whether what I had done was sufficient.

I didn’t realize this shift until I found myself reconsidering work I’d already delivered, wondering whether it should have been different, even when no one had given any indication that it was inadequate. The doubt wasn’t rooted in feedback — it was rooted in the habitual anticipation of it.

This experience ties back to something I wrote about in why I always feel behind no matter how much I do. There, the sensation of being behind was about completion never feeling complete. Here, the sensation of doing enough was about never knowing whether I met an invisible threshold that always seemed just out of reach.

Sometimes it felt like I was waiting for someone to say the words I hadn’t heard: *Yes, this is sufficient.* But those words never came. Instead, there was a quiet space after each task — a lingering question mark hovering over the outcome rather than a period of conclusion.

Workdays started to feel like a revolving door of tasks I was constantly entering but never leaving. I’d finish something and instead of moving on with a sense of closure, I’d feel the lingering pressure of uncertainty: Had I done enough? Was I interpreting the requirement correctly? Would someone later tell me to revise something I thought was done?

It became a pattern more than a problem. Almost like a calibration error in how I experienced completion. I wasn’t missing tasks. I wasn’t ignoring goals. I just never felt like I’d truly met them.

In conversations, I found myself qualifying nearly every statement. Not because anyone asked me to, but because I had internalized that nothing was truly fixed until someone explicitly stated it was. ”Here’s what I did — but let me know if this needs adjustment.” “Here’s what I finished — but I can revise anything if needed.” That phrasing became habitual, almost automatic.

This habit wasn’t about politeness. It was about uncertainty. I wasn’t sure whether what I’d done aligned with unstated expectations, so I built in disclaimers as a kind of safety net. This pattern reminded me of the quiet tension I noticed in how unspoken expectations made my job feel unsafe. There too, the absence of clear standards made everything feel like a guess rather than a task.

I began assessing my work before anyone else saw it — not to improve it necessarily, but to anticipate potential gaps. Even when the requirements were clear, I’d double-check them, wondering if there was an underlying criterion I had missed. The more I checked, the less confident I felt that “enough” was even definable in that context.

There were times I’d finish a project and then feel strangely uneasy, as if the lack of immediate acknowledgment meant something was wrong. Which it usually didn’t. No one had said anything negative. But the absence of explicit affirmation became something my mind tried to fill with possibilities of insufficiency.

Even when someone did say something positive, I often caught myself discounting it internally, thinking it was just momentary encouragement rather than a genuine assessment of sufficiency. Praise didn’t land as confirmation — it landed as a wave that passed over, leaving the uncertainty underneath unchanged.

In meetings, I’d feel this uncertainty subtly pull at my attention. When someone asked for an update, I’d respond with detail, but part of my mind was already evaluating whether the update sounded sufficient, whether it was framed the right way, whether it left room for later correction. The work was done, objectively. But the internal experience was provisional.

This made deadlines strange. Instead of meaning something definitive, they became mere checkpoints on a path I felt I was still navigating internally. Completing a task didn’t signal arrival. It signaled transition to the next question: *Is this good enough?* That question hung in every space where closure ought to have been.

This wasn’t about validation from others. It was about the internal echo of completion that I never learned to feel. The evidence of finishing something existed — the task was marked done, the document was sent, the feedback loop closed. But inwardly, there was no match between what I did and what I felt I needed to feel in order for it to feel sufficient.

And so I worked in a state of quiet ambiguity — never behind in specific tasks, but never forward in the internal sense of adequacy either. The more I completed, the more I began to realize that my experience wasn’t tied to what I actually did. It was tied to how the mind interpreted those actions.

In conversations outside of work, I noticed this pattern too. I’d describe something I’d finished and still feel as if I needed to justify it. Not to others — to myself. It was a strange internal echo chamber where completion never felt like closure, only preparation for another round of uncertainty.

Occasionally, I wondered whether this sensation was tied to a broader pattern — something like perfectionism or over-interpretation of expectations. But it didn’t feel anchored in fear of error. It felt anchored in absence of certainty — like the threshold of “enough” had been erased without my consent.

And so I kept pushing forward, doing the work, completing tasks, and moving on to the next. Externally, everything looked functional. Inwardly, nothing ever landed as truly sufficient.