When doing personal development, one day your hands suddenly stop. It's not that you can't write code or fix bugs—it's a much vaguer kind of "stopping." You're sitting in front of the screen, but you can't do anything. The cursor just blinks, and before you know it, 30 minutes have passed. Does that feeling ring a bell?
Lily has experienced that moment many times. While building a product alone, bit by bit, I found that emotional roadblocks were far more common and lasted much longer than technical ones. This article is about that kind of "emotional stalling." I won't write technical solutions. I'll just honestly describe what Lily actually did when her hands stopped, and how she gradually became able to move again. I'd be happy if this helps someone else who's stuck in the same way.
At first, I thought it was a technical problem. "I don't know how to implement this, so I'm stuck." "I don't know how to build this feature, so I can't move forward." That's what I thought.
But when I really thought about it, that wasn't usually the case. I could find the method if I searched. There was documentation. There were references. Yet I still couldn't move. Why?
After thinking about it for a while, I realized that what had stopped wasn't my "hands"—it was my "mind." "Should I really be making this?" "Won't anyone use this feature?" "Isn't there a better way to do this?"—I was going in circles before the point of actually creating, and I couldn't reach the stage of making anything.
The kind of stalling that comes from "overthinking"
With personal development, you have to decide everything yourself. The direction, the specifications, the design. If you're at a company, someone says "let's go with this for now." If you're on a team, someone pushes your back. But when you're alone, you have to decide everything, and that "deciding" step becomes incredibly heavy.
In Lily's case, what I was particularly struggling with was the feeling of "is this okay?" When I started making something, it would work properly, and I could create something usable. But the question "isn't there a better way?" and "is this really necessary?" never left my head, and I'd find myself stopping even while creating—a strange state.
The most painful kind of stalling is when "I'm almost done, but I can't move."
80% of the feature is done. All that's left is fine-tuning and final polish. Yet somehow that last 20% sits untouched for days, sometimes weeks—does that sound familiar?
Lily struggled with this for a long time. Why is the end always the heaviest? I wondered.
The honest truth: I was afraid to release
The answer is simple: I think I was afraid to ship it. An incomplete state is still protected. There's an excuse: "it's still in development." But once you release it, you see the reaction. There's a possibility it won't be used. You have to face the reality of "nobody used it."
By not finishing, I was protecting the possibility that "maybe it could work out." Like, if you don't open the box, you can still dream. But of course, that way nothing moves forward.
The spiral of self-blame
When you're stuck, you start blaming yourself. "Why can't I move?" "Can't I even keep doing this?" "Maybe I'm not cut out for this?"—once this inner criticism starts, you become even more paralyzed.
Can't move → blame myself → become even more paralyzed → blame myself more. Lily got caught in this spiral too, and there was a period where I couldn't do anything.
There's no complete solution, and there's no magic that works for everyone. Still, I'll honestly write about methods that helped me a little.
Decide "it doesn't have to be finished" and release something
What worked best was deciding "I don't have to finish it, I just have to release something."
It doesn't have to be the finished version. 80% is fine. 60% is fine. Bugs can remain. Just try the act of "releasing" itself.
At first, I was scared. But when I released it, the world surprisingly didn't end. Someone used it. I got feedback like "I'd be happy to have this feature." Sometimes that half-finished version helped someone more than what I thought was the complete version, and I was taken aback.
Make something else small
Another approach was to set aside the stuck product for a while and make something completely unrelated and small.
Something that takes a day or two, something really tiny. Something where the finished form is clear and it ends quickly.
What's good about this is that you can recover the feeling of "I made something." When you're stuck, it's easy to feel "I can't make anything." But when you complete something small, you can think "oh, I can make things." That feeling gives you the energy to face the original product again.
Make a "don't do" list instead of a "to do" list
One more thing that quietly helped: this.
When stuck, I often had too many tasks and didn't know where to start. So I decided to make a list of "what I won't do today." "I don't need to improve this UI today." "I don't need this feature this week." That kind of thing.
Instead of deciding what to do, decide what not to do. Just that alone made me feel "I only need to do this today," and I could move a little.
When you're making something alone, you tend to try to complete everything in your head, but talking to someone changes things.
When Lily was stuck, I'd write "I'm stuck" in community threads or progress-sharing spaces. I wasn't looking for solutions—just trying to put it into words, that's all.
When you put it into words, you often realize "wait, I was stuck on something this simple?" What was going in circles in your head suddenly gets a clear outline when you write it down.
When someone says "I get it," that alone makes you feel a little better. Because it's such solitary work, that one word becomes incredibly comforting.
"I'm stuck" isn't shameful
Before, I was embarrassed to say "I'm stuck." It felt like I was the only one not making progress, like I was showing weakness.
But when I actually said it, everyone was stuck the same way, and nobody thought it was "weak." Most responses were "me too!" I realized that putting your stalling into words and sharing it isn't weakness—it's honesty.
When I got stuck, at first all "stalling" looked the same to me, but when I observed carefully, I noticed there were different kinds.
Technical stalling: I don't know how to do it, I don't know how to research it. This usually gets solved by searching or asking someone.
Decision stalling: I can't decide the direction, I don't know what's right. Information gathering often doesn't solve this. You just have to decide at some point with "okay, let's go with this."
Energy stalling: I don't feel like doing it, I'm tired. You just have to rest. Forcing yourself to move just spins your wheels.
The approach is completely different for each
These three types need completely different approaches. Researching works for technical stalling, but researching doesn't solve energy stalling at all. It just makes you more tired.
When I got stuck, I started asking myself "what kind of stalling am I experiencing right now?" and things became a little easier to move through. Depending on which type it was, I could decide "I'll rest today," "I'll talk to someone," or "I'll try moving my hands first."
To be honest, I still get stuck sometimes. I don't think there's a way to never get stuck.
Still, I'm glad I kept going, because I've gotten a little better at stalling. Before, when I got stuck, I thought "it's over." Now I can think a bit more calmly: "I'm stuck again—what kind is it?" The frequency of getting caught in spirals has decreased.
I feel like with personal development, the difficulty of "continuing" is greater than the difficulty of "making" itself. You can learn technology by researching. But how to work with your own heart—you have to learn that yourself while stalling.
For Lily, personal development wasn't just about making a product. It was also practice in how to live with my own heart.
I wrote this article not to tell someone else, but also to organize it for myself. "Don't deny the stuck version of yourself, just observe it, and move a little." Repeating that, I somehow got here.
Are you stuck right now too? I think that's probably because you're continuing. People who aren't moving don't get stuck. Getting stuck is proof that you're trying to move forward.
Take it slow. Move small. Let's continue together.
Lily (@bokuwalily) — Personal developer. Making iOS apps and web services with AI as my partner.
