- A long project almost never dies all at once. It wears down, until the day the folder stops opening.
- This article explains why motivation fades on long projects, what researchers found about interruptions, and the three ingredients that keep momentum going.
- You leave with three questions to ask your project, and one proof of progress to produce within two days.
Your project started strong. Three weeks of momentum, notes, a plan, almost a sense of pride. Then the weeks pass and the folder stops opening. When you come back to it, you spend twenty minutes rereading what you already did, you cannot find where to pick up, and you close it again. After a few months the question changes: it is no longer “I am not making progress,” it is “maybe this is not for me.”
[ANECDOTE DIANE: a long project you let sleep, and the moment you realised motivation was not the missing piece.]
That conclusion is almost always wrong. It turns a gap in conditions into a flaw in character, and it sends you looking for the fix in the wrong place: a resolution, a new tool, a burst of willpower that lasts a week. This article starts from the other end. Motivation on a long project is not a stock of energy you have or lose. It runs on specific conditions, and when one of them is missing, momentum collapses without warning. You can check them one by one in about ten minutes.
A long project rarely gives you a signal
On a short project the reward arrives quickly: you finish, you see the result, you start the next one. On a long project (a book, a website rebuild, a course, a two-hundred-page report) the signal is rare. You work for weeks before anything visible exists. Your brain then receives effort and no evidence, and it starts avoiding the effort.
Anne-Laure Le Cunff, founder of Ness Labs treats self-motivation as a skill built from a few ingredients rather than a trait you are born with. I keep coming back to the word “built”. If motivation is constructed, a project that loses it does not prove you are incapable. It tells you that one condition is missing, and the job is to find which one.
Three ingredients, three diagnoses
Le Cunff’s framework names three: self-efficacy, curiosity and competence. Each one breaks in a different way, and the fix changes with it.
Self-efficacy is the belief that you can move forward. You cannot decree it. It runs on small, repeated proof: a section finished, a session kept, a mistake handled without drama. When that proof disappears, you start doubting that the work is doable, even though you know how to do it. The typical symptom is telling yourself “I don’t know where to start” when you have already started three times.
Curiosity is what makes a question worth answering. A long project turns into a chore when it no longer asks anything new, when each task is only the execution of a decision made three months ago. The symptom: you open the file and feel no urge to check, compare or test anything.
Competence is the feeling of getting better. You can work hard without feeling it if your work produces no visible improvement. The symptom: you reread your first pages, find them as weak as before, and cannot tell whether anything has moved since.
Interruptions, the cost you do not see
Long projects also suffer from a more ordinary enemy: interruptions. A message, a notification, a tab asking for attention. Each one seems harmless. In an experiment led by Gloria Mark and her co-authors at the University of California, Irvine, 48 participants worked through a simulated inbox while being interrupted every two minutes. They finished faster than without interruptions, with no measurable difference in errors, but with clearly more stress, frustration and effort.
The last part is the one that matters. The brain compensates: it speeds up, it writes less, it grits its teeth. The work moves forward, but the bill arrives somewhere else, as tension that builds up. A long project broken into interruptions does not stop in one go. It wears down, and the wear looks like a lack of motivation. That is why the slowdown arrives late and is hard to spot. If this mechanism sounds familiar, the article on open tabs and attention debt shows how these interruptions pile up without any noise.
The three-question diagnosis
Ask yourself three questions about your stalled project, in this order. Each one maps to an ingredient, and the answer points to the move to make.
What is the last proof that you moved forward? If you cannot name one from the past ten days, self-efficacy is the missing piece. Cut a section into a deliverable you can finish in one session, then finish it. Every finished deliverable is a proof.
What question does this project still ask you? If the answer is “none”, curiosity is the gap. Write a question you cannot answer without testing something, then test it. A project becomes interesting again once it contains an unknown.
What has changed since your first draft? If nothing shows, competence is the gap. Compare the current version with an older one on one precise criterion: a paragraph, a screen, a loading time. Progress has to be visible to count.
The mistakes that make the slide worse
Three reflexes turn a small slowdown into a full stop. The first is to restart with one big session: you block a whole Sunday to catch up on three weeks. It goes badly because there is no clear entry point, and what you remember is the fatigue. The second is switching tools: a new project app, a new document template. The project does not have a tool problem, it has a proof problem, and a tool does not produce proof for you. The third is blaming yourself for the delay. Each self-reproach adds tension, and as the interruption study suggests, that tension is paid in stress rather than progress. The better reflex is duller: one short session, one proof, then the next.
What the diagnosis does not fix
It does not fix everything. If fatigue, low mood or lack of sleep dominate, no ingredient will be enough: repair the base first. The article on sleep debt and productivity explains why that ground matters before anything else.
It does not fix the bigger question either. If the project no longer serves a purpose, stop it cleanly. A dead project kept alive weighs more than a stopped one, and it keeps up the guilt that makes every restart harder.
The action to take today
Take your longest project, the one you keep avoiding. Answer the three questions in one sentence each, in three minutes. Then pick the smallest proof you can produce within two days (a section, a test, a comparison) and block it in your calendar with a duration. You do not need to restart the whole project. You need the next proof.
What this changes for you
Once the diagnosis is done, the rest becomes concrete. The full method, with the decision grid and the “if X, then Y” rule that triggers the start, is in the Motivation lesson of the course. For restarts after a break, the broken habit streak covers the same problem on the habit side. And if you first want to get your Windows setup in order, the free guide to 10 Windows settings covers the basics.
Sources
Figures and references checked on 5 November 2026.
See the 2 sources for this article
- Anne-Laure Le Cunff, “The Self-Motivation Toolkit: How to Stay Curious and Committed,” Ness Labs, 15 April 2024 (read the article)
- Gloria Mark, Daniela Gudith and Ulrich Klocke, “The Cost of Interrupted Work: More Speed and Stress,” CHI 2008 (read the PDF)