Skip to main content

The Friction Loop: How I Trained Myself to Avoid My Own Projects - Asterisk Pound

Unpacking the avoidance pattern behind stalled side projects — the loop of hesitation, distraction, and quick relief that quietly trains you out of building.

Alan Asher April 24, 2026 5 min read
personal reflection habits side-projects focus

The Friction Loop: How I Trained Myself to Avoid My Own Projects

After paying closer attention to why I haven’t been building lately, I started noticing something uncomfortable:

This isn’t random.

It’s a pattern.

And worse—it’s a pattern I’ve probably trained myself into.


What it feels like vs what’s actually happening

On the surface, it feels simple:

“I sit down to work, and I just don’t feel like doing it.”

But if you zoom in a little, there’s a very consistent sequence playing out.

It looks like this:

  1. I decide I should work on a project
  2. I sit down to start
  3. It feels mentally heavy or unclear
  4. I hesitate
  5. I reach for something easier (usually my phone)
  6. I get a quick hit of relief
  7. I tell myself I’ll come back to it

Then I don’t.

That’s not a one-off decision. That’s a loop.


The moment that matters most

The critical point isn’t when I choose to scroll.

It’s the moment right before that.

That split second where the work in front of me feels:

  • undefined
  • complex
  • effortful

Even if the task itself isn’t that hard, it feels like it is.

And that feeling is enough.

Because right next to it is an option that is:

  • immediate
  • easy
  • predictable

So my brain does exactly what it’s designed to do.

It chooses the lower-cost path.


Relief is the reward

Here’s the part that makes this sticky.

When I avoid the work and switch to something easier, I don’t just distract myself—I feel better.

That relief is important.

Because now the loop isn’t just:

“work vs distraction”

It becomes:

“discomfort vs relief”

And every time I choose relief, I reinforce the pattern.


Training the wrong system

Over time, this creates a kind of conditioning:

  • “Starting work” becomes associated with friction
  • “Avoiding work” becomes associated with relief

Eventually, the resistance shows up before I even begin.

I don’t need to fail at working.

I just need to remember what it felt like last time.

So the brain gets ahead of it:

“Let’s not do that again.”


Why this didn’t happen overnight

This didn’t show up out of nowhere.

It’s likely the result of a few things stacking up:

  • working a full day already (reduced mental energy)
  • tackling projects that are open-ended or complex
  • not having a clearly defined “next step”
  • easy access to high-reward distractions

None of those are extreme on their own.

But together, they create the perfect conditions for this loop to form.


The role of ambiguity

One thing stands out more than anything else: ambiguity.

When I sit down in the garden, the next step is obvious.

When I sit down to build something, it often isn’t.

Even if I know what needs to be done in a broad sense, the immediate action isn’t always clear.

And that gap—between “I should work on this” and “here is the exact next step”—is where friction lives.

The brain doesn’t like that gap.

So it avoids it.


This isn’t about discipline

It’s tempting to frame this as a willpower problem.

Just push through it. Be more disciplined. Stop scrolling.

But that misses the mechanism entirely.

If a system consistently produces the same output, the issue isn’t effort—it’s design.

Right now, the system looks like this:

  • high cognitive cost to start
  • unclear entry point
  • delayed reward
  • immediate alternative with low cost and high reward

Given that setup, the outcome is predictable.


The uncomfortable conclusion

I didn’t just “fall out of the habit” of building.

I built a competing habit.

A stronger one.

One that activates faster and pays out sooner.

And now it’s winning.


Why this actually matters

This isn’t just about productivity.

It affects:

  • whether ideas turn into anything real
  • whether projects ever leave the starting phase
  • whether I trust myself to follow through

If every attempt to start gets shut down by friction, eventually you stop trying altogether.

Not because you don’t care.

But because the system makes caring expensive.


The shift in perspective

Instead of asking:

“How do I force myself to work?”

The better question is:

“Why does starting feel expensive, and how do I lower that cost?”

That’s a systems problem.

Not a motivation problem.


What I’m starting to test

Nothing complicated. Just small adjustments to the system:

  • making the next step painfully obvious
  • reducing the scope of what “working” means
  • focusing on starting, not finishing
  • removing as much decision-making as possible

The goal isn’t to outwork the friction.

It’s to remove it.


Where this goes next

If this loop is learned, it can be unlearned.

Or at least reshaped.

But it won’t happen by accident.

It’ll require deliberately building a system where:

  • starting is easy
  • progress is visible
  • the reward comes sooner

In other words, something that looks a little more like the garden—and a little less like an abstract, open-ended task.


Because right now, the system I have is working perfectly.

Just not in the direction I want.