> ## Content Index > Fetch the complete content index at: https://mitchellens.ink/llms.txt > Use this file to discover other available public pages before exploring further. # You're too competent to finish things - URL: https://mitchellens.ink/systems/advance/youre-too-competent-to-finish-things/ - Published: 2026-03-22T09:38:36.000Z - Updated: 2026-05-15T10:03:41.000Z - Description: If you’re reading this and you feel stuck, there’s a good chance you already know something important: the problem isn’t that you can’t do the work. It's something much more profound and therefore difficult to spot. - Author: Mitchel Lensink - Tags: Advance, Systems When I look back at the moments where I felt most blocked, it’s almost never because I lacked skill, discipline, or ambition. And when I talk to other creative people who feel the same kind of friction, they report the same thing. If anything, the pattern points in the opposite direction. We get stuck because we can do *too much*. Too many skills. Too many interests. Too much awareness of nuance. This chapter isn’t about motivation or grit. It’s about what happens when your capabilities outpace your ability to create closure for yourself. ### The beginner mindset Beginners move fast. Not because they know what they’re doing, but because they *don’t yet see everything that could go wrong*. They don’t feel the full weight or consequences of their actions. Beginner loops are small, and therefore feedback is pretty much immediate. A beginner's path, while uncertain, is simple enough to walk on without much hesitation. Forwards is the only logical option. At this early stage, not many problems show up yet. The problems we are discussing here appear later. After some experience is gained. After our taste has developed a little more. After you’ve learned to see the trade-offs too, instead of just the absolutes. You understand how things work now, once graduated from that beginner stage. You can anticipate some second-order effects. You can argue both sides of a decision convincingly. You're able to see some nuance in the world, and understand it truly is multiple shades of grey with black and white as rare extremes. As a result, very little feels obviously wrong anymore. But at the same time, very little feels obviously right either. And because of that, closing something starts to feel heavier than opening it. 💡 ****Decision** Everybody knows what a decision is, but in **Advance* we use the word a bit more broadly. In this framework, a decision is the point where something becomes actionable. Where an idea gains an end condition, and a loop begins. A decision is what turns possibility into direction. Your work doesn’t move forward through thinking alone, but through decisions that can actually finish. So things stay open. Not because you’re lazy. Not because you’re afraid of the effort required to finish things. But because finishing something now means giving up the possibility of finishing it *better* later. ### The weight of the open loop I’ve personally felt this most clearly when building my systems. Websites, note-taking, archiving, frameworks, all structures meant to support other work. I can get completely absorbed in thinking about how everything should connect, how it should scale, how it could be made more elegant or future-proof. And while I’m doing that, it genuinely feels productive. Until, at some point, I notice something’s off. Weeks have passed. The system has become more refined, sometimes even perfected. But the original purpose has faded. I have trouble answering a simple question: *what was this actually meant to support?* The work was done and I kept things moving, but I drifted away from the reason the work existed in the first place. From the outside, this still looks like progress. And technically, it is. But internally, something else starts to accumulate. **Open loops. Mental background processes causing a kind of fragmentation that’s hard to notice until it’s already there.** You don’t feel it immediately. Not consciously, at least. And that's very understandable, given how slowly it starts to show. You'll notice it in the way you talk, jumping between threads without quite landing. In how you explain your choices, layered and nuanced, but somehow unfinished. In how you receive feedback, intellectually engaged, yet either strangely untouched by it, or sometimes even frustrated, because there’s nothing concrete for that feedback to push against. The issue isn’t the effort you put in things. It’s the closure you're denying yourself. ### Being good at procrastinating This is the uncomfortable part, because this pattern disproportionately affects capable people. 💡 ****A note on intelligence** This section is not about ego or superiority. Intelligence does not make someone inherently better than others. It is simply a form of cognitive capacity — the ability to see nuance, anticipate consequences, and reason through multiple perspectives. That capacity is valuable, but it also comes with a responsibility. A strong analytical mind can easily justify delay. It can generate convincing reasons to wait, refine, or reconsider. When not paired with action, intelligence can become a liability rather than an advantage. Capability is not the same as intelligence, and intelligence itself has many forms. The point here is simple: if you are able to see many angles at once, you are also more prone to overthinking. Recognizing that pattern is not self-importance. It is self-awareness. There’s an obvious reason strong analytical capacity makes postponing action feel justified. Seeing multiple angles makes it easier to justify waiting. A nuanced view on the world gives you endless reasons why now might not be the right moment, yet. There’s always one more variable to consider, one more version that could be better, one more perspective worth integrating. What you are doing in that process is not avoiding responsibility but rather *explaining your way around it*. And that works, for a while. But over time, this lack of resolution starts to leak into other areas of your life. Mind you though, it won't emerge as chaos but as something a lot harder to pinpoint: friction. So how do you know you've inadvertently introduced more friction in your life than typically healthy? It depends on who you are as a person, of course it does, but there are some effects that are typical for most humans. Your sleep becomes lighter. Your mood shifts quickly, and frequently. Positive emotions become more fragile and are easily disrupted. Your body continuously carries a low-grade tension. Not the healthy resistance of working through something meaningful, but the kind of strain where nothing can be resolved today, or even this week, because everything seems connected to everything else. At that point, the problem is no longer about productivity. It's about assertiveness and the ability to keep it moving. ### The *un*finisher If you are unable to complete tasks or projects you've started, eventually that creeps into your systems. Into your identity. You become the person that 'always starts new things but never sees them through.' You don't want to be that person. Imagine going for a walk. Everybody enjoys a good walk. It brings you to new places, allows you to see different things, and every step comes with new information to you to process. You learn about the world around you and you learn about how you fit into that world. Now imagine walking in a circle. The same block, over and over again. That's fun the first time, maybe the second time "Hey, I didn't notice that before!". But, eventually, you've seen it all. There's nothing else for you to process. You're stuck. That's why it's important to keep yourself orientated. Do that, and you can maintain a sense of progress and your story as a human has an arch to it. Fail to do this, and over time your sense of self begins to detach from what you actually do. Your place in the world becomes less clear. Doubt will inevitably creep in and you start to question every next step you take. > Maintain a sense of progress and your story as a human has an arch to it. Apply this to your ideas, your projects, and your ability to earn an income, and doubt and directionlessness (that's a word, I promise) become expensive quickly. If your questions become: "Are these the right things to be working on? Are these the right steps? What is all of this actually leading to?" then your next paycheck is further away than ever. That might sound dramatic, but it’s surprisingly common. It’s what happens when nothing you do is allowed to become real. **Completion isn’t just a logistical step. It’s a condition for meaning. Without it, your sense of self slowly detaches from what you actually do.** Not necessarily in a worse way, but in a less grounded one. More hypothetical. More imagined. And the longer this goes on, the harder it becomes to tell who you are and who you *could've* been. ### Accidentally avoiding the end The problems described above don't resolve themself by thinking longer and harder. And it doesn’t get better by keeping options open either. When too many things remain unfinished, you don’t just lose momentum. You lose the ability to recognize yourself in your work. You stay busy, engaged, intellectually active, yet strangely untouched by what you’re doing. In my experience, that’s one of the most quietly exhausting states to be in. That’s the problem this framework starts with. Not a lack of ability, but a lack of closure. Not insufficient ambition, but too many unresolved paths. The next chapter looks at one of the main reasons this happens so easily: the way keeping options open delays ownership, often without us noticing it at all. That's why this framework is not meant to be read once and put away. It’s meant to be returned to while you’re in the middle of something. A project. A decision. A period where things feel busy, but strangely unresolved. You’ll learn how to recognize when thinking turns into avoidance, how to design work so it can actually finish, and how to make decisions that produce feedback instead of more doubt. Again, nothing here requires certainty. Everything here is meant to be applied immediately, in small, concrete ways, to whatever you’re already working on.