paid-only post

Making closure a practice

Understanding the Advance Filter is one thing. Keeping it alive in real situations is another. Closing a loop once is not that difficult, especially now that you have this framework. Keeping your system stable over time is where the real work begins.
Making closure a practice

So what destabilizes that progress over time? It is drift. And drift is not dramatic. It is subtle, gradual, and almost reasonable while it is happening. That's exactly what makes this difficult. Let me explain what I mean by that.

💡
Drift
Drift is the structural condition in which loops expand beyond their original scope. The results being that boundaries become unclear, and no loops are closing within a reasonable timeframe.

It is identified by ongoing activity without completion and by the absence of recent feedback.

Let's start by saying that I unfortunately had to learn this the hard way. Not through theory, as you're doing right now (although I imagine you have some real life examples of your own too. Otherwise, why would you be reading this to begin with), but through watching my own projects slowly lose their edges over time.

There was a period where I had this framework open in one tab, a brand document for a side-project in another, notes for a newsletter in Obsidian, and a half-written page on my site waiting to be published. Every document felt important. Every one felt almost done. None of them were actually finished though. I remember sitting at my desk late at night, technically productive, yet unable to point to a single closed loop. I was moving, but I was not advancing (see what I did there). That was drift. Not collapse, because that would make this much easier to deal with. That would be a clearer sign I was not focussing on the right things. Experiencing drift is difficult because it's sneaky and it hides itself. It's a slow dilution of your efforts and a draining of your energy.

And it happens, you know. This is part of the messy world we live in. Loops quietly reopen, scope stretches beyond what you first agreed to, boundaries become less clear, ownership becomes vague. Small tasks stack up until the weight feels strangely familiar. "How did I get here, again?" you suddenly ask yourself.

For me, it often looked like I was taking my responsibility. Adding one more paragraph to a draft to ensure I could not be misunderstood. Expanding the scope of a project slightly so it would be more complete, more finished, more perfect. Keeping something going just a little longer so it could become a better thing. If you read the earlier chapters of this framework, you know this pattern already. The desire to reduce social risk. The urge to protect yourself from being seen as premature or wrong, from looking like a fool. None of that feels reckless. It feels like you're being careful, well-considered. But being careful can cause the drift you want to avoid as well.

This drift from your original goals or commitments rarely announces itself: "Hello! Time to get distracted and focus on the wrong things again!" As I said, it does not feel like things are collapsing. You typically don't even notice it at first. Instead, it feels like being slightly off. Like something you can 'quickly fix, if you need to.' But that course correction can't come soon enough, for you drift a little further away as long as you don't take control. Until, one day, you suddenly recognize the pattern and realize you are back in a place you thought you had already moved on from.

This chapter is about noticing that drift early, and correcting it before your structure fragments again. This chapter will help you turn your newly learned skills into a practice, even when things in real life become complicated. The Advance Filter from the previous chapter is your tool, this chapter will tell you when to use it. This is where you will learn how to become a serial closer of loops in a world that keeps opening new ones for you.

When drift begins

Your plans or projects almost never fall apart all at once. They typically erode under specific conditions. But worry not, for there are signals! They are quiet, but they are consistent. This will take some practice, but over time you'll develop a sense for them.

To start, watch for these three early signs:

First: You are active, but nothing is finishing

You are working on multiple things, but none of them are moving toward a clear ending. Documents stay open. Tasks remain in progress. Energy is spent, but nothing is really finishing.

Second: There has been no real feedback in a while

Ask yourself when you last released something into the world. When did someone respond to your work? If nothing has shipped then nobody can provide you any feedback. And with no response, that often means no closure.

Third: You are waiting more than acting

You are blocked on someone else’s reply. Someone else’s approval. Someone else’s input. The question becomes: what is still within your own boundary of responsibility? What can you close without them?

When one of these shows up, it is a signal. When two or three show up together, you are already drifting.

This post is for paying subscribers only

Subscribe to continue reading

Advance

Toolkit map