A simple explanation
The paper has been ready, by any honest reading, for at least four months. You have done another reread. You have softened one paragraph and sharpened another. You have asked a colleague to look at it; they responded two months ago and said it was good. The cover letter is half-drafted. The journal is chosen. Nothing in the manuscript has materially improved in eight weeks, and you have not submitted it.
This is publication anxiety. Not the paper. The way the paper stays on your laptop while your career, quietly, does not move.
An everyday example
A Friday afternoon. You open the file, scroll to the discussion section, change three words, save, and close it. The action took ninety seconds. You feel, for those ninety seconds, like a researcher doing research. You also feel, fainter and underneath, the small private knowledge that you have just performed work on a paper that needed sending in March. You make tea. You think about working on it more on Sunday. You will not.
The same paper has been near-submitted for nineteen weeks. In that time, two papers in adjacent labs have appeared on the same question. Yours was earlier in conception. The field is now reading their version.
How do I know when a manuscript is ready to send?
You do not know with certainty. You know with sober judgement. The Meaning System is asking for a deposit, and the deposit cannot be delivered while the paper is on your hard drive. Submission is the closure event. The System, defending the work from imagined rejection, has accepted a substitute — I am still working on it — that feels like care but functions as deferral.
The honest threshold is rarely perfect. It is good enough that further work has stopped producing real improvement. Most submitted papers in your field were in approximately that state when they went out. Yours probably reached it months ago. The way to know is not another rereading. It is to ask one trusted colleague: is this ready, and what would you change with one more week if you had to send it then? If their list is short and you already know most of it, the paper is ready.
The behavioral loop
A loop with long pauses and a daily small tax:
- Drafting — the paper takes shape. The System deposits cleanly through draft completion.
- Internal review — co-authors, lab-mates, advisor pass. Real improvements land. The deposit continues.
- Polishing phase — revisions produce diminishing returns. Each pass changes fewer things and changes them less.
- Submission stall — the cover letter is started. The journal is chosen. The submit button is not pressed.
- Substitute work — small touch-ups, references re-checked, figures reformatted. The activity feels like progress.
- External pressure — an advisor asks, a deadline approaches, a competing paper appears. The System briefly spikes; the paper is opened; it is not sent.
- Residue accumulates — the paper begins to feel stale to its own author. New ideas arrive that cannot land on a project still officially open.
- Eventual submission or abandonment — either the paper goes out months late, or it joins the file of things that almost were.
Emotional drivers
- A specific dread of the desk-rejection email, often more vivid in rehearsal than the actual email would be in arrival.
- A diffuse worry about being scooped, layered with the knowledge that scooping is more likely the longer the paper sits.
- An imposter signal that the manuscript will be read by smarter people who will see what you missed.
- A protective pride in the work that confuses I care about this with I will not let it leave my hands.
What your nervous system does
A low-grade, persistent activation that spikes briefly at each submission moment and then resets when the moment passes. The System is reading the submission as an exposure event — the paper, until sent, exists inside a controlled relational field; sent, it enters a field of strangers with judgment. The body's response is proportionate to the construal, not to the actual stakes. A desk-rejection from a journal does not threaten safety, belonging, or worth in any structural sense, but the system reads the prospect that way.
The unusual feature is the way the activation never produces clean discharge. Most pre-event activations spike, the event happens, the system resets. Publication anxiety lacks the event — the submission keeps not occurring — so the activation runs at low volume for months, occasionally spiking, never resolving.
The DojoWell interpretation
Publication anxiety is a clean false progress pattern. Revision activity feels like care for the work and registers, in the moment, as productivity. The MDT equation reads otherwise. Effort term: real but increasingly low-yield. Deposit term: near-zero, because the work cannot integrate while it remains private. Residue term: compounding — the paper sours, the field moves, the writer's relationship to the manuscript turns from pride to faint shame.
The substitution is unusually convincing because the substitute looks identical to the original. The original ask of the Meaning System was deliver this contribution to the field. The substitute is keep working on this contribution. The verbs differ by one tense and the world is full of voices that endorse the substitute — take your time, get it right, don't rush. Some of that endorsement is real. Most of it, applied to a paper that has been ready for months, becomes cover for deferral.
This is one of the few patterns where the resolution is precisely the feared event. The paper has to leave your hands. Submission deposits even when the result is revise and resubmit — which is the most likely outcome at most journals — because the system finally registers that the contribution has been offered. The desk-rejection deposits too: less satisfying, equally closure-producing. The only outcome that does not deposit is the one currently in progress, which is not sending the paper at all.
How do I stop polishing a paper that should already be out?
You set a submission horizon and treat further revision as the cost rather than the work.
Three moves:
- Set a date and tell one person. Two weeks from today. The person who knows is not a coach; they are a witness. The System needs the social structure to accept the closure.
- Use the two weeks to address one specific list, then stop. Not make it better. A specific list of three to five changes, written before you start. When the list is done, the paper is done.
- Send the paper the morning of the date, not the evening. Evening sends become next-morning sends. Morning sends become sent. The System gets less time to reopen the question.
Practical steps
- Stop reading the manuscript top to bottom. You have done it enough. Further reads produce diminishing returns and increasing dread.
- Decide once which journal, not three times. The journal choice is its own substitute. Pick one credible target; if it desk-rejects, you will pick the next. The cascade is structural; you do not need to optimise it now.
- Draft the cover letter as the first task, not the last. Reverse the order. Writing the cover letter clarifies whether the paper is ready more honestly than another rereading does.
- **Ask one co-author or trusted colleague: *what would you change with one more week?*** If their list is short and known, you are ready. If it is long and surprising, the paper genuinely needs more work — but it usually will not be long.
- Plan what you do the day you submit. Do not skip the closure. A walk, a coffee, a real moment of that one is out of my hands now. The System needs to register the deposit; closure rituals help it do so.
Reflection questions
- How long has this manuscript been in one more pass mode? What has changed in the last month of revision?
- Who is the imagined reviewer in your head, and what is your actual relationship to the version of them who exists?
- What is the worst plausible outcome of submission, and what would you do the day after it happened?
- Which other papers and ideas are currently parked behind this one, waiting for its closure to free your attention?
Frequently Asked Questions
Is fear of rejection holding back my career?
If you have one or more manuscripts that have been near-submission for over three months, almost certainly yes — at least in part. Career momentum in academic fields is measured in submitted-and-cited work, not in privately-polished work. The fear is real; the question is whether you are letting it shape your output. Naming it as the variable, rather than the manuscript's quality, often produces motion.
What do I do when my advisor wants more revisions but I want to submit?
Distinguish two cases. If the requested revisions are specific and substantive, do them. If they are vague — let it sit, look at it again next week — ask explicitly: what specifically would you change before submission? Often the advisor has not formed a concrete list and the request is itself a deferral. A specific list is workable; a vague request can be respectfully named and pushed back on with a proposed submission date.
How is publication anxiety different from perfectionism?
Perfectionism is the broader pattern — a worth-coupling to flawlessness. Publication anxiety is a specific application: the manuscript becomes the object the perfectionism organises around. The difference matters because perfectionism resists generic be less perfectionistic interventions, whereas publication anxiety often responds to a concrete submission horizon. Address the specific instance first; the broader pattern, if present, is the next layer.
What if I genuinely think the paper is not good enough?
Sometimes the paper is genuinely not ready, and the anxiety is doing its job. The diagnostic is whether your concerns are specific and shareable. If you can write a three-line list of what is wrong, address those things. If your concern is diffuse — something is off, it's not strong enough — and a trusted colleague disagrees, the concern is more likely the substitution than a real signal. Specific worry is information; diffuse worry, in this context, is usually the loop.
How does this connect to Meaning Density?
Publication anxiety is the canonical false progress signature. Revision activity registers as productive work — the System logs it as effort toward the contribution — while the deposit term stays at zero because the contribution requires submission to integrate. Residue accumulates as a paper that sours and a field that moves. The equation only resolves at the submission event. Density rises sharply once the work leaves the writer's hands, regardless of whether the first journal accepts it.