How to stop procrastinating: what research says and one small experiment
Procrastination is less a time-management failure than a way of avoiding a task that feels unpleasant, so the steps that help make the start smaller and more specific: a first step you can begin in a few minutes, and a plan that says when and where you begin. A record of your day cannot fix the avoidance, but it can show you the moment you drift, which is more useful than a vague sense of having wasted the afternoon.
What procrastination is, according to research
Piers Steel's 2007 meta-analysis in Psychological Bulletin pulled together 691 correlations from studies of procrastination. The traits people often blame, neuroticism, rebelliousness and sensation seeking, showed only weak links. The strong and consistent predictors were task aversiveness, task delay, self-efficacy and impulsiveness, along with conscientiousness and its facets of self-control, distractibility, organization and achievement motivation.
Fuschia Sirois and Timothy Pychyl, in a 2013 paper in Social and Personality Psychology Compass, argue that procrastination has a great deal to do with short-term mood repair. When a task feels aversive, putting it off gives immediate relief, and the cost lands on your future self. That is why the afternoon of tidying and reading feels fine while it happens and bad on the next day.
Taken together, the findings point away from the idea that you lack discipline or a better calendar. The task feels bad, the reward for avoiding it is immediate, and the benefit of doing it is far away. The practical question becomes how to make the task feel less bad and the start less costly.
Make the first step smaller
Steel's strongest predictors include how aversive a task is and how far away its reward is, and a large vague task such as write the report is aversive in exactly that way. Reading those findings, a sensible response is to cut the task down to a first step that is concrete and quick: open the document and write the heading and three bullet points, not finish the section. This is an inference from the research, not something those papers tested on its own.
A good first step has three features. You know exactly what your hands do, such as open the file and write one paragraph. It takes minutes, not an hour. And it produces something you can see, so the next step is easier to start than the first.
Write an if-then plan
Peter Gollwitzer's work on implementation intentions is the better-supported tool here. In his 1999 review in American Psychologist he describes plans of the form: Whenever situation x arises, I will initiate the goal-directed response y. These plans hand control of the response to a situational cue. He frames them as a way through problems such as failing to get started, becoming distracted and falling into bad habits, and the program of research he summarizes shows that they further goal attainment. A 2006 meta-analysis by Gollwitzer and Sheeran pooled 94 independent tests and found a medium-to-large effect on goal attainment, d = .65, and the plans helped in particular with getting started, which is the step a procrastinator is stuck on.
An example: When I close the standup call, I open the draft and write the first paragraph. The cue is something that already happens, the action is the small first step, and you decide in advance so the moment of starting needs no new decision. Write the plan down and put it where you will see it at the cue, not only in your head.
If you have several things to start, try one plan first and see whether that way of starting helps.
Seeing when you drift, without guilt
A recorded day answers the question what happened, which is hard to answer from memory because avoidance rarely feels like avoidance. Hina 0.6.0, a macOS menu bar app, records which app was in front and for how long, with counts of key presses and clicks, and keeps it on your Mac. It takes no screenshots and asks only for the Accessibility permission. Window titles and page paths stay off until you turn them on in Settings, Privacy. It gives no productivity score and no streaks, so the record describes the day without grading it.
In the Trail tab each hour shows its active time, up to two main projects and, when you switched apps more than once, the number of app switches, with a row per stretch and the time it ran until. If you want to see the pull, look at the rows around the time you meant to start: which app were you in at the moment before you left the task? That is more useful than the total hours.
The Week tab has an Interruptions card that lists the apps that cut into work, and the sites when page paths are turned on, where an interruption is a break under 5 minutes in the middle of work. Reading the card as a list of cues is the helpful way to use it. If one site shows up again and again right after you open a hard file, that is your if-then plan's trigger.
Recording works offline. The app reaches the network in three places, each only when you click: opening the checkout page in your browser, activating a purchased key, and Check for Updates, which reads a version number from hina.day. None of them sends your activity.
One small experiment for a week
Pick one task you tend to put off, and one if-then plan with a first step of about five minutes. Run it for five working days. At the end of each day open the Trail for that day and note two things: whether the first step happened close to the cue, and the first app you went to when you drifted, if you did.
On Friday open the Week tab and look at the Interruptions card next to your notes. Then change one thing: move the cue, shrink the first step further, or close the app that kept showing up before you start. Only one, so you can tell what made the difference.
If a day had the plan but not the start, do not count it as a failure. The point of the experiment is to find where the plan breaks, and a missed start tells you that more clearly than a good day does. Earlier days and the Week tab are readable during the trial or with a licence, the Daily report needs one even for today, and today's Trail and Day tab stay readable either way.
What records cannot fix
The record shows apps and time, not reasons. Avoidance often looks like work: reorganizing notes, answering easy email, or reading about the task instead of starting it all sit in work or neutral categories. Time away from the screen, on a phone or in a conversation, is invisible or shows up only as away. When the idle stretch is one the machine cannot classify, Hina asks once on your return, with choices Meeting, Reading / thinking, Watching and Away, and your answer reclassifies it.
Records also cannot change how a task feels, which is the center of the research above. If you are avoiding something because it frightens you or because you are low, a smaller first step may help, and talking to a professional may help more, particularly if the avoidance is constant or costs you sleep or health. An app cannot do that part.
Use the record to learn when and where your starts break, use the if-then plan and the smaller step to change them, and keep the review short.