The feeling passes, the work stays stopped

What the term describes, and what it does not

Rejection sensitive dysphoria names an intense, physically felt reaction to rejection, criticism, or the perception of either, at an intensity well beyond what the event seems to warrant. It is discussed most often alongside ADHD and emotional regulation, and people who recognise it usually recognise it instantly, which is a large part of why the phrase spread.

It is a descriptive term rather than a clinical diagnosis. Nobody is diagnosed with it, there is no test for it, and the people who write about it most seriously are careful to say so. That is worth knowing before you go looking, because it explains why the sources disagree with each other more than they would about something formal.

This page stays on one narrow question: what a spike does to work that was in progress, and how to restart that work. The emotional side, whether any of this applies to you, and anything to do with assessment or treatment are questions for a qualified professional, and they are genuinely better answered by one than by an app or an article.

The task does not resume because it never had a next action

Here is the sequence almost everybody describes. A comment lands. The reaction is enormous and takes the rest of the day. By the following morning the feeling has receded to something manageable. The document is still open, you still intend to finish it, and days go by in which you do not open it.

The instinctive explanation is that the fear is still there, quietly. Sometimes that is true. But there is a simpler thing happening underneath it, and it explains the cases where you genuinely are not afraid of the work any more and still cannot get into it.

Before the spike, the task was a noun. Finish the deck. Fix the function. Reply to the email. A noun has no visible first move, which is already enough to stall a start on an ordinary day. The spike did not change the size or shape of the task at all. It simply added a cost to touching it. So you return to exactly the same undefined lump you were already struggling to start, now with a weight attached, and the result is what it always was, only more so.

That is the useful part, because it means the restart problem is the familiar one. What you need is a defined physical first move, which is the same thing the task paralysis guide is about, and the spike is a multiplier rather than a new category of obstacle.

A spike attaches to a specific thing, and it matters which

Avoidance after a rejection is rarely general. It has an object, and naming the object is what makes it possible to work around, because you can usually keep working on everything the object is not.

• The artefact. The actual document, file, or piece of work the comment was about. You can often work on the same project happily as long as you do not open that file, which is a strong signal that this is the shape you have.
• The channel. The inbox, the message thread, the review tool where it arrived. The tell here is that unrelated work also stalls when it requires opening the same app, and that a notification badge is enough to ruin an hour.
• The person. A specific reviewer, manager or client. Everything they might see slows down, including work they have not asked about, because each step is now being pre-judged against their reaction rather than against the task.
• The category. Rarer and heavier: not this document but this kind of work, permanently. Worth naming when it happens, because at that size it is no longer a scheduling problem and it is one of the things worth taking to someone qualified.

Restart on something the criticism did not touch

The instinct is to go straight back to the exact thing that was criticised, fix it properly, and prove the criticism wrong. That is the hardest possible re-entry point, and it fails for a reason that has nothing to do with courage: the spike has made that specific object expensive to touch, and you have chosen it as your first move.

Pick almost anything else in the same piece of work instead. Rename a file. Fix a typo two pages away from the paragraph in question. Write the heading of the next section. The requirement is that it is physically visible, takes under a minute, and is not the sentence somebody objected to. Momentum inside the work is what makes the criticised part approachable again, and it almost never runs in the other direction.

This is the specific job the task breaker on this site does: it takes the noun you are frozen in front of and hands back a sequence of steps small enough that one of them is startable right now. The value on a day like this is not that the steps are clever. It is that the list was produced by something other than the mind currently holding the spike.

Separate the work from the audience while you restart

A spike converts work into performance. Every sentence is now being written and simultaneously judged by an imagined version of the person who commented, which roughly doubles the cost of each one and slows everything to a crawl.

The workable move is to produce a version that person will not see. A scratch file, a rough pass, notes rather than prose, anything explicitly labelled as not the real thing. This is not self deception. It genuinely removes the reviewer from the loop for the duration of the pass, and the work that comes out can be tidied afterwards with a much calmer head.

The same logic explains why working alongside another person helps so much here, even when they know nothing about the task. Their presence replaces the imagined audience with a real and indifferent one, which is the whole mechanism the body doubling guide covers.

Reply and resume are two different tasks

A critical message usually creates two jobs at once, and merging them is what turns a bad afternoon into a lost fortnight. One job is answering the person. The other is the work itself. Held together, neither moves: you cannot reply until you have fixed it, and you cannot face fixing it until the reply is off your chest.

Split them and do the reply first, deliberately short. An acknowledgement that names what you will do and when is enough, and it does not require the work to be done or the feeling to be resolved. What that buys is the end of the open loop, and the open loop is doing much of the ongoing damage.

Then treat the work as an ordinary stalled task, because at that point that is all it is. Time also distorts here in the usual way: a day of not touching something reads internally as a much longer neglect than it was, which the time blindness guide covers, and that inflated sense of how long it has been is itself a reason people avoid returning.

What this page is not

This is a page about restarting work, written by a company that makes a focus app, and that is the entire scope of it. It is not a diagnosis, not treatment, and not an assessment of whether the term applies to you. Anyone for whom rejection reliably costs days at a time, or whose reaction extends into hopelessness, is describing something worth taking to a professional rather than to an article, and that remains true regardless of how well the mechanics above fit.

Focable is deliberately narrow in the same way. It turns one task into steps small enough to begin, which addresses the stalled work and nothing about the feeling. That limit is worth being clear about, because a tool that claimed to address both would be lying about one of them.

Try it now

• task breaker

Questions