I noticed it when finishing something no longer changed how the day felt.
Nothing ever signaled that I was done.
This wasn’t poor time management—it was work without natural closure.
Early on, productivity felt directional.
You worked toward something and then crossed it off.
Completion used to mean something.
Before, tasks resolved into milestones.
During the PhD, tasks dissolved into ongoing processes.
Eventually, productivity stopped feeling cumulative.
The work never ended because it was designed to remain open.
The fear of not producing enough made stopping feel irresponsible.
I noticed how often finishing one thing immediately revealed three more.
Revisions, new ideas, future outputs waiting in the background.
Instead of relief, completion created momentum pressure.
Productivity became a treadmill.
This wasn’t drive—it was continuity without recovery.
Publishing without closure reinforced the sense that output was never sufficient.
What made it exhausting was the absence of permission to pause.
There was always another task justified by future need.
Even rest felt provisional, like a delay rather than a reset.
I was always supposed to be moving.
Endless productivity isn’t sustainable—it’s destabilizing.
Academic burnout grew out of never reaching a stopping point.
Why does academic work never feel finished?
Because projects are iterative and future-oriented, with few true endpoints built into the structure.
Is constant productivity expected in academia?
Often, yes. Ongoing output is treated as normal rather than exceptional.
Does this mean I’m working inefficiently?
No. It usually means the work itself resists clean completion.
Productivity didn’t feel endless because I was slow—it felt endless because there was nowhere to stop.
