Why does my motivation hold up on some projects and completely drop on others?

I spent several years treating motivation as though it were purely internal. If I cared enough about something, I reasoned, I would find the energy to see it through. When motivation dropped halfway through a project, it meant either that my commitment had waned or that I lacked sufficient discipline. The problem felt straightforward: I wanted it badly enough, or I didn’t.

What I’ve since learned, both through coaching others and through my own experience, is that this view is incomplete. Motivation isn’t stable. It fluctuates in response to conditions, some of which are internal but many of which are structural. And once you recognise that, everything changes. You stop treating motivation as something you generate through willpower and start treating it as something you can design.

What this actually buys you

Understanding what sustains motivation matters because most of us operate as though motivation is either present or absent. We show up with energy or we don’t. We care deeply or we don’t. This binary thinking leads to predictable responses: push harder, find more willpower, question whether we actually want the thing.

But once you recognise that motivation depends partly on conditions, you shift from blame to design. You move from “I must want this more” to “What conditions would allow motivation to persist?” The practical effect is significant. You stop abandoning projects because you’ve “lost interest” and start examining whether you’ve designed them in ways that sustain focus. You stop treating motivation as something you generate and start treating it as something you can architect.

This matters especially in leadership. Leaders often assume their teams’ motivation is a function of how inspiring the mission is or how much autonomy they’ve granted. But teams abandon important work regularly, not because the mission stopped mattering but because the conditions that sustain attention have eroded. Learning to diagnose and redesign those conditions is one of the higher-leverage leadership capabilities.

Why it matters

Self-determination theory, developed by Deci and Ryan, established that intrinsic motivation depends on three psychological needs: autonomy (the sense of choice and control), competence (the experience of capability), and relatedness (connection to something beyond yourself). This framework is genuinely useful. I’ve found it invaluable in coaching conversations. Someone abandoning a project often lacks one of these three elements. If you want to understand how to activate intrinsic motivation in others, the principles work equally for sustaining your own.

But it is not the whole picture. Research across multiple fields reveals that what keeps motivation alive over months differs from what gets it started. The research spans goal setting, progress psychology, temporal motivation, and identity theory. You can have autonomy, competence, and relatedness in place and still lose momentum halfway through. Conversely, people persist through projects where one or more of these needs go unmet, sustained by forces the theory doesn’t fully account for.

The gap lies in four distinct mechanisms: goal clarity and feedback, the perception of progress, alignment between the work and your identity, and the temporal and social conditions around the effort. These aren’t luxuries or nice-to-haves. Research by Locke and Latham, Amabile and Kramer, Steel, and others suggests they’re foundational to sustained motivation.

The pattern typically plays out across a project arc. Initial enthusiasm carries you through the first phase. But around the midpoint, if one or more of these mechanisms is weak, motivation dips sharply. Visibility of progress vanishes. The finish line recedes. Competing priorities surface. At that moment, you’re relying on willpower alone, and willpower is expensive and context dependent. Motivation collapses because the structure that sustained it wasn’t in place.

How motivation quietly compounds or collapses

The four mechanisms interact. When one weakens, it stresses the others. This table shows what happens:

What this reveals is that these mechanisms are interdependent. Weakness in one creates cascading stress on the others. This is why some projects suddenly collapse: not one factor failed, but one weakness went unaddressed long enough to undermine the others.

Five practices

Practice 1: Define progress with precision

Before you start, spend an hour describing what done looks like. Not vaguely (“finish the strategic plan”) but specifically enough that someone else could assess whether you’ve done it. “Produce a 12-page document with five scenarios, each showing financial impact over three years, with stakeholder feedback incorporated, and board sign-off” is a definition that works.

Once you have this definition, build checkpoints into it. Mark which sections constitute meaningful progress. Identify intermediate milestones that represent real completion, not arbitrary halfway points. A progress loop requires specificity: you need to know when you’ve moved from A to B. This is how drive for results actually works in practice: focus on the outcomes you can articulate and track, not the effort you’re expending.

Steps:

1. Write a description of what done looks like, specific enough that someone else could verify it.
2. Identify three to five major milestones between start and finish.
3. For each milestone, name a specific deliverable or decision that marks it as complete.
4. Share this with someone you’re accountable to. Their questions will show you where clarity is still missing.
5. Revisit this description mid-project. Has done changed? Adjust it.

Variation: If the project is genuinely uncertain (research, exploration, learning), define what “progress in understanding” looks like. What will you know when you didn’t before? What decisions become possible once you’ve learned it?

Practice 2: Make progress visible

Amabile and Kramer’s research on 12,000 diary entries showed that the perception of progress matters more than motivation itself. But perception requires visibility. Progress that exists in your head or in behind-the-scenes effort doesn’t count neurologically. You need an artefact or a tracker. This connects to how people actually learn from feedback and progress. Waiting passively for motivation doesn’t work. You need to actively seek signals that you’re moving forward.

Pick one that you’ll actually maintain. A shared document updated weekly. A tracker that shows forward movement. A weekly email naming what moved. A chart that’s updated in real time. Pick something simple enough that it becomes automatic, not something you’ll abandon after month one.

Steps:

1. Identify what “visible progress” means for your project. What artefact or metric shows you’re moving?
2. Design a tracker or document that surfaces that artefact weekly.
3. Commit to updating it every Friday (or your chosen day). The consistency matters more than perfection.
4. Share it with your accountability partner or team. Others seeing progress matters as much as you seeing it.
5. At the mid-project dip point (usually month two or three of a longer project), increase the frequency. Weekly updates become twice-weekly. This is when motivation typically drops, and visibility is your lever.

Variation: If your work is invisible (thinking, writing, strategy), create artefacts that make progress tangible: drafts shared, frameworks sketched, decisions documented. The artefact doesn’t need to be finished. It needs to show you’re moving.

Practice 3: Connect the work to who you’re becoming

When a project reinforces your identity or moves you towards a version of yourself you want to be, motivation persists even when obstacles mount. When it conflicts with your self-concept, motivation dries up regardless of external conditions. This is why knowing yourself and understanding what actually matters to you makes such a difference. You’re not just managing a project. You’re either building or diminishing the person you want to become.

This requires clarity about two things: who you see yourself becoming as a leader, and how this specific project contributes to that becoming. Not forced connections. Real ones.

Steps:

1. Write a sentence describing what kind of leader or professional you’re building yourself to be. What capability are you developing? What impact do you want to have?
2. For your current project, write a sentence connecting it to that vision. How does this work contribute to that becoming? Be specific. “This organisational redesign will teach me how to move at pace through complexity” is stronger than “it’s part of my job.”
3. Post this where you’ll see it. Not secretly. Your accountability partner should know it too.
4. When motivation dips mid-project, return to this statement. Does it still ring true? If not, the project itself might be the wrong one. If it does, reconnect to why you’re doing this, not just what you’re delivering.
5. Revisit it at project end. What did you learn about yourself? How did you grow?

Variation: If the project doesn’t initially connect to your development, ask what aspect of it does. Even in assigned work, some piece usually contributes to capability you value. Find that piece and anchor motivation there.

Practice 4: Create artificial deadlines and feedback loops

Temporal motivation theory reveals that motivation responds to how far away the finish line feels. As deadlines approach, motivation climbs. As they recede, motivation naturally drops. Long projects or those without clear deadlines suffer: the finish line stays abstract.

You cannot change how long the project actually takes. But you can change the perceived distance to completion by creating interim deadlines. These aren’t the real deadline. They’re checkpoints that reset the temporal dynamic. This is related to how habits actually survive sustained pressure. Breaking the work into smaller, achievable cycles keeps momentum alive.

Steps:

1. If your project runs longer than 6-8 weeks, divide it into cycles with their own endpoints.
2. For each cycle, establish a real deadline (not flexible, not negotiable). Even if it’s internal, treat it seriously.
3. Establish a feedback loop: weekly check-ins with a peer, monthly reviews with a sponsor, sprint reviews with your team. The cadence matters less than consistency.
4. At each feedback point, ask three things: Are we moving towards done? What’s blocking progress? What’s the next deadline?
5. Use feedback to reset expectation and timeline, not to criticise effort. The goal is to keep the finish line visible.

Variation: If external deadlines exist, use them. If they don’t, create internal ones and defend them. Ambiguous timelines are motivation killers.

Practice 5: Design the social and structural conditions

Motivation doesn’t happen in isolation. Peer engagement, visibility, accountability, and regular feedback create conditions that extend internal drive far beyond what willpower alone can sustain.

This might mean embedding yourself in a team or community working on the same thing. It might mean creating a working group, establishing regular check-ins with a peer, or sharing progress weekly. It might mean inviting others into the thinking early so accountability becomes relational rather than individual. Accountability structures work when they’re clear and relational, not punitive. The social dimension keeps motivation alive.

Steps:

1. Identify who needs to be involved in this project’s success. Include your accountability partner, your sponsor, and anyone who will benefit from the work.
2. Design a structure that keeps them engaged. Weekly emails? Fortnightly working sessions? Monthly showcases?
3. Make the structure predictable. Consistency matters more than frequency.
4. Use it to surface progress, invite input, and maintain connection. The social function is as important as the informational one.
5. At the point where motivation typically dips mid-project, increase the frequency slightly. This is when isolation feels strongest. Social connection is your circuit-breaker.

Variation: If your project is genuinely solitary, create the conditions artificially. Find an accountability partner outside the project. Join a cohort working on related things. Create a monthly reflection session. Something to anchor you to others.

When redesigning isn’t the answer

Sometimes improving the conditions around a project doesn’t restore motivation because the core problem isn’t structural. It’s directional.

Sometimes you should abandon a project. Not because you lack discipline or willpower, but because it’s genuinely misaligned with who you want to become or what actually matters to you. You can build perfect feedback loops around the wrong work and still feel hollow.

The diagnostic question is honest: if I could redesign every condition around this project, making it perfectly clear, perfectly visible, perfectly paced, would I want to do it? If the answer is still no, the work itself might be the problem, not how you’re approaching it. This is where how you talk to yourself about the work matters. Sometimes the voice telling you to quit is actually wisdom, not weakness.

Additionally, sometimes motivation needs rest. If you’ve been pushing hard on a project, success sometimes requires stepping back, not pushing harder. A redesigned structure that demands more intensity when you need recovery is counterproductive. Energy and capacity matter. Permission to pause is sometimes what sustains motivation, not intensity.

These moments are rare, but they’re real. The practices in this article assume the project is worth doing. If that assumption is false, no amount of structural redesign will fix it.

Five micro-practices

Weekly progress audit. Every Friday, write down three concrete things you moved forward this week on your project. Not effort or hours spent. Actual progression: sections completed, decisions made, obstacles resolved. The act of articulating progress matters neurologically. It anchors motivation for the week ahead.

Mid-project check-in. Around month two or three of a longer project, pause and review: Is progress visible? Am I connecting to identity? Are the social conditions strong? This is when motivation typically dips. Reviewing these four mechanisms now, before the dip becomes crisis, is preventative.

Identity reminder. When you find yourself avoiding the project or feeling stuck, return to your identity statement. Why does this work matter to who you’re becoming? Reconnect there, not to willpower.

Deadline visualisation. Each Monday, visualise the next intermediate deadline. Not the final one. The one that’s close enough to feel real. Proximity affects motivation more than importance.

Peer accountability check-in. One sentence to your accountability partner: what’s the one thing you’ll move forward by next week? Knowing you’ll report it matters. Being known matters.

Reflection questions

Where in your work right now is motivation flagging? Apply these questions to that project or commitment:

On clarity and feedback: Could you describe precisely what done looks like? Do you have feedback loops that tell you whether you’re moving towards it? What’s one checkpoint you could add this week?

On progress perception: Can you see the progress you’re making? What artefact or tracker would make invisible progress tangible? Who else needs to see it?

On identity: Does this project connect to who you’re becoming? If the answer is uncertain, what aspect of it does? If the answer is no, is that telling you something worth hearing?

On temporal dynamics: How far away is the finish line? Does it feel abstract or real? Would breaking the project into shorter cycles help? When is the mid-project dip point likely? How will you maintain conditions then?

On environment: Are you working on this alone or with others? If alone, what forms of accountability or feedback would help? If with others, what’s working and what would make the social structure stronger?

Sources

Amabile, T. M., & Kramer, S. J. (2011). The progress principle: Using small wins to ignite joy, engagement, and creativity at work. Harvard Business Review Press.

Deci, E. L., & Ryan, R. M. (2000). The “what” and “why” of goal pursuits: Human needs and the self-determination of behavior. Psychological Inquiry, 11(4), 227–268.

Locke, E. A., & Latham, G. P. (2002). Building a practically useful theory of goal setting and task motivation: A 35-year odyssey. American Psychologist, 57(9), 705–717.

Steel, P. (2007). The nature of procrastination: A meta-analytic and theoretical review of quintessential self-regulatory failure. Psychological Bulletin, 133(1), 65–94.