Guide

Rejection sensitivity and avoiding work: why it happens and what helps

Updated November 2026 · by Jerry Liu, Dayflow's founder

Often the task is not the problem. The possible verdict is. Lower the stakes before you start: draft on paper where nobody will see it, set a kitchen timer for ten minutes, and send a rough version to one friendly person first. A Mac app like Dayflow can show afterward where the avoided hours went, but it only records your screen. It does not coach, treat or block anything.

The email has been in drafts since Tuesday. Finishing it would take ten minutes. Every time you open it, you reread the first line, picture the reply, and close the tab. Since then you have cleared your downloads folder, answered every easy message, and tidied a spreadsheet nobody asked about. The email is still there, and now it is late, which somehow makes it heavier.

The task itself is not hard. You know how to write it. What you are avoiding is the moment after you send it, when someone reads it and decides what they think. The proposal, the pull request, the pitch, the message to a client who went quiet: each one carries a possible verdict, and the dread attaches to the verdict, not the work.

This guide covers why avoidance tends to cluster around work that will be judged, six things to try this week (most need nothing more than paper, a timer or a friend), and when it is worth talking to someone. Dayflow, the Mac app that publishes this blog, comes up once near the end, along with where it is the wrong pick.

The short version

Why do I avoid tasks that might get judged?

Most people know the feeling, even if they describe it differently. A few plain mechanisms tend to be at work.

The task carries two jobs. One job is doing the work. The other is finding out what someone thinks of it. Easy tasks with no audience only carry the first job, so they get done first. That is why the inbox gets cleared on the day the big draft is due.

Avoiding brings instant relief. Closing the tab feels better right away. The cost arrives later and spreads out, which makes it easy to choose the relief again and again. Nothing about this is a character flaw. It is how relief works.

Waiting makes the verdict bigger. On Monday the risk was “they might not like it.” By Thursday it is also “they will notice it is late.” Every day of avoidance adds a new thing to be judged for, so the task grows without changing.

Polishing becomes protection. If the work is perfect, nobody can criticize it. Since nothing is ever perfect, the polishing never ends, and the work never ships. Rereading a two-line message nine times is often this.

Vague tasks hide the scary part. “Work on the proposal” is a fog. Somewhere inside it is one specific moment you are dreading, like naming a price or admitting a delay. Until that moment is named, the whole task feels like it.

Many people describe a strong, fast reaction to criticism, sometimes called rejection sensitivity, where a short reply can feel like a judgment on them as a person rather than on one piece of work. Many people with ADHD describe this too. If that sounds familiar, the ideas below are still worth trying, and there is a section near the end about when to get more help. For the broader overlap between attention and putting things off, see ADHD and procrastination.

What is the verdict you’re actually avoiding?

What to do. Take a piece of paper and finish this sentence for the task you are dodging: “I’m afraid that when they see this, they will think…” Write the honest answer, even if it sounds dramatic. Then add a second line: “If that happened, what I would actually do next is…”

Illustration. A designer has been avoiding sending a homepage concept for four days. She writes: “I’m afraid they’ll think I don’t understand their brand.” Second line: “If that happened, I’d ask which parts feel off and do a second round, which is in the contract anyway.” The fear did not vanish, but it shrank from a cloud to a specific, survivable conversation.

How to tell after a week. Look at the tasks you wrote about. Did any of them move faster than similar tasks usually do? Also notice whether the feared reaction was ever the one you got. You are not trying to prove the fear wrong, just to make it concrete enough to plan around.

Can you do it where nobody will see it?

What to do. Split the task into a private version and a public version, and give yourself permission to make the private one bad. Write it on paper, or in a file literally named “rough - not for anyone.” The rule is that this version can never be sent as it is, which removes the audience from the room.

Illustration. A developer stuck on a code review response opens a plain text file and writes, in bullet points, every thing he wants to say, including the ones he would never say out loud. Ten minutes later he has the actual content. Turning it into a polite reply takes another five. The hard part was getting the words out, and the private file let him do that without anyone watching.

How to tell after a week. Count how many times you used a private draft and how many of those turned into something you sent. If the private drafts pile up and never ship, the next section is where the real block lives.

Who is the safest first reader?

What to do. Before the work goes to the person whose opinion scares you, send it to someone whose opinion does not. A friend, a peer, a partner. Ask a narrow question, like “is anything confusing in this?” instead of “is this good?” Narrow questions get narrow answers, which are easier to hear.

Illustration. A freelance writer dreads sending a pitch to an editor she admires. She sends it first to a friend with one question: “Does the first paragraph make you want to read the second?” The friend says yes and points out one clunky sentence. The writer fixes it and sends the pitch the same afternoon. The pitch did not need a lot of work. It needed one safe exposure before the real one.

How to tell after a week. Notice the gap between “first reader saw it” and “real reader saw it.” If that gap is short, this step is doing its job. If you start avoiding the friendly reader too, make the question even smaller, or try the timer below.

What if you only had to start for ten minutes?

What to do. Use an actual kitchen timer or a plain phone timer. Set it for ten minutes. The only commitment is to have the task open and be touching it when the timer runs. When it rings, you are allowed to stop. Often you will not want to, but stopping has to be a real option or the trick stops working.

This is a small version of timeboxing, and it works for a related reason: you are no longer agreeing to the whole frightening task, just to ten minutes of it.

Illustration. A manager has been avoiding a hard performance note for a team member. She sets a timer and only writes the first sentence and three bullet points. The timer rings. She keeps going for another twenty minutes, then stops for the day with a half-finished draft. The next day, starting is easier because the blank page is gone.

How to tell after a week. Track how many ten-minute starts you did and how many led to more than ten minutes. If most stop at exactly ten, that is still progress. If you are not starting the timer at all, the first step may still be too big. Shrink it further: “open the file and read the last line.” For more on getting past the very first move, see how to get started when you’re stuck.

Would it be easier with someone in the room?

What to do. Do the scary part next to another person. They do not need to help or even know what you are working on. They just need to be there, working on their own thing. Sit in a café with a friend, call a colleague and keep cameras on while you both work, or tell your partner “I’m sending this email in the next fifteen minutes” and do it at the kitchen table. This is often called body doubling.

Illustration. Two friends, both self-employed, agree to a one-hour video call every Wednesday morning. At the start each says the one thing they have been avoiding. At the end each says whether it got sent. One of them has been putting off raising a rate with a client for a month. It goes out in the second week. The friend never read it. Saying it out loud and knowing someone would ask was enough.

How to tell after a week. Compare the tasks you did with someone present to the ones you tried alone. If the accompanied ones moved and the solo ones did not, that is useful information, and it is worth making the arrangement regular.

What actually happened last time?

What to do. Keep a short log, on paper or in a note. When you finally send or submit something you were dreading, write three lines: what you feared, what actually happened, and how long it took for the feeling to fade. A simple daily work log template works if you prefer a structure.

Illustration. One entry might read: “Feared: client would say the timeline was unacceptable. Happened: client asked to move one milestone by a week. Feeling faded: about an hour.” After a few weeks the log becomes a small archive of evidence your nervous system can consult next time.

How to tell after a week. Read the entries back. You are not looking for proof that nothing bad ever happens. Some feedback will sting. You are looking at the gap between what you expected and what you got, and how quickly you recovered. If entries show that the dread lasted days while the actual conversation took minutes, that pattern is worth remembering on the next hard Tuesday.

If underestimating how long the dread will last is part of it, the time estimation test is a short exercise comparing your sense of time with a clock. It is not a diagnostic, just a way to notice your own pattern.

Where seeing your actual day helps

A lot of avoidance is invisible while it happens. At 5 p.m. you know the proposal did not move, but not where the afternoon went, and that gap tends to fill with the harshest story available. Reconstructing the day from memory on a bad day is rarely kind.

If you would rather see a record than rebuild one, that is what Dayflow does. It is a free, open-source Mac app, MIT licensed, for macOS 14 or later. It captures the screen at one frame every 10 seconds and has AI write the day into a readable timeline, so there is no timer to start and nothing to remember to log. Recordings and the timeline are stored on your Mac. Analysis can run with a local AI model so screenshots stay on-device, through your own cloud provider, or through the optional Dayflow Pro plan at $20 a month. The processing modes page explains what leaves your Mac in each case. You can export a date range as Markdown.

For avoidance, the value is noticing a pattern calmly. For example, you might see that the scary file was opened several times and closed within a minute each time. AI summaries can miss or misread work, so treat the timeline as a rough record, not a verdict. For a walk through reading a day this way, see where did my day go.

Dayflow publishes this article. Product details come from Dayflow’s own documentation for version 2.2.0, reviewed September 6, 2026.

Where Dayflow is the wrong pick

Be clear about what it is not.

When to get more help

This article is not medical advice. If avoidance is affecting your job, your sleep or your relationships, or if criticism tends to leave you feeling crushed for days, it is worth talking to a doctor or a licensed clinician. The same goes if you think ADHD, anxiety or depression might be part of the picture. They are the right people for diagnosis and treatment, and no app or article replaces that. If you ever have thoughts of harming yourself, contact your local emergency number or a crisis line right away.

The bottom line

When a task sits untouched for days, it is often not the work you are avoiding but the verdict that comes after it. That is a very human response, and it says nothing about whether you care or are capable. The things that tend to help are small and low-tech: name the specific fear, make a private version first, show it to the safest possible reader, start for ten minutes, work beside someone, and keep a record of what actually happened. Try one or two this week, not all six. If a clear view of where your hours went would help you notice the pattern without rebuilding it from memory, a screen record can do that, as long as you treat it as information and not a judgment.

Frequently asked questions

What is rejection sensitivity?

People use the phrase to describe a strong, fast emotional reaction to criticism or rejection, real or expected. A short reply from a manager can feel like a judgment on your whole worth, not just one piece of work. It is a description of an experience, not something you can diagnose from an article. If it is shaping your work or relationships, a doctor or licensed clinician is the right person to talk to.

Is avoiding tasks the same as being lazy?

Usually not. Laziness implies you do not care. Avoidance around judged work tends to happen because you care a lot about how it will land. The avoided task often stays on your mind all day, which is tiring in its own way. Treating it as a fear problem rather than a character problem points you toward things that actually help, like shrinking the first step and lowering the stakes.

Why do I procrastinate more on work that someone will review?

Work that will be reviewed carries two jobs: doing the thing, and finding out what someone thinks of it. Easy tasks with no audience do not carry that second job, so they feel lighter and get done first. Every day the reviewed task waits, it gains a new risk of being judged for lateness too, which can make starting even harder.

How do I start a task when I'm afraid of criticism?

Separate doing from showing. Start a version nobody will see, on paper or in a file named something like rough, and set a timer for ten minutes. Write down the specific reaction you fear, then decide who the safest first reader is. Small, private starts tend to be easier than trying to produce the finished, reviewable version in one sitting.

Is rejection sensitivity related to ADHD?

Many people with ADHD describe intense reactions to criticism and say it affects how they approach work. Plenty of people without ADHD describe it too. An article cannot tell you whether ADHD is part of your picture. If you suspect it is, a doctor or licensed clinician can assess it properly and talk through options that fit you.

How do I stop rereading an email before I send it?

Give the reread a limit. Decide on two passes, one for facts and one for tone, then send. If you are still stuck, read it aloud once and ask whether a friendly colleague would find anything wrong. Many people find that the extra rereads do not change the email much. They just delay the moment of being seen.

Can an automatic time tracker help with avoidance?

It can help you see the pattern, not fix it. A record of what was on your screen shows when the avoided file was open and what replaced it, without relying on memory at the end of a rough day. That can make avoidance easier to talk about calmly. It does not reduce the fear itself, and for some people seeing the record adds pressure, in which case skip it.

Can Dayflow block distracting sites while I'm avoiding a task?

No. Dayflow does not block websites or apps. It records what happened and writes a timeline afterward. If what you need is a hard barrier in the moment, a dedicated website blocker is the better pick. Some people use both: a blocker during the work session and a record afterward to see what happened.

Does Dayflow work on Windows or iPhone?

No. Dayflow is a Mac app and needs macOS 14 or later. It also sees only your Mac's screen, so time on your phone, on paper or in conversation does not show up. If most of your avoidance happens on another device, a paper log or a tool built for that device will serve you better.

Is Dayflow free?

Yes. Dayflow costs $0 and is MIT licensed, so the source code is public. There is an optional Dayflow Pro plan at $20 a month that handles cloud analysis for you. You can instead run analysis with a local model on your Mac or connect your own cloud provider, which has its own charges and terms.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required