One day, as I was opening and checking incomplete files one by one, I suddenly realized something. "Wait, this is completely different from what I originally planned." There was no shock. I wasn't afraid either. Rather, I felt a slightly nostalgic sensation—"Ah, I see, so it came this way."
My name is Lily. I create web tools and small services by myself. Today I want to write about how I "created something completely different from the original plan without telling anyone." For a while, I wondered whether this was a failure or a freedom that's only permitted when working alone. Now I have one answer.
The plan was incredibly detailed
Last spring, I decided to create "a habit management tool for developers." It would sync with Git commit history to visualize learning routines. The target was "working adults in their 30s relearning programming." I created a persona sheet, wrote a feature list, and even drew up a roadmap to launch.
Despite working alone, I had documents that looked like early-stage startup materials spread across my desk. At that time, I believed "this is the right way to do it." With a plan, you won't get lost. With a design document, you won't waver. That's what I thought.
Three months later, what was there
Three months later, when I looked at the repository, what I found was "a simple task memo tool." The habit management elements had almost disappeared, and Git integration was never implemented. The target audience had, without me noticing, become "myself."
The original feature list had 23 items. But what actually remained in the code was about 5, and the rest were quietly sleeping in an "implement someday" folder.
One turning point was a post by Rina, who also develops solo. On the community timeline, Rina wrote: "I wrote 47 features in my original business plan. At launch, only 3 remained."
It was a post on an account with few followers, with little engagement. But what came next wouldn't leave my head.
"What I wrote in the business plan wasn't what I wanted to make—it was a pitch to 'someone who would use it.'"
The moment I read it, I thought, "Oh, that's me too."
When I reviewed the feature list
That night, I opened my list of 23 items. Going through each one asking "Would I actually use this every day?", I could honestly say only 4 of them. The remaining 19 were imagined demands—"users would probably want this," "it would be convenient to have."
Rina's number of 47 and my number of 23 overlapped in my mind. The scale was different, but what we were doing was the same. We were designing features for fictional people that we'd never use.
From that day on, I quietly began cutting from the list.
I never "announced" the cuts. It wasn't significant enough to write on SNS "I'm changing direction," and besides, I wasn't reporting progress to anyone. I simply and quietly repeated the judgment: "this isn't needed," "this suits me better."
With each cut, things felt a little lighter. Things I thought "I can't launch without this" didn't matter when they were gone. Rather, without them, the core became clearer.
There was a sense of guilt
On the other hand, I felt somewhat guilty. Abandoning the original plan felt like "running away midway." If someone asked me "What happened to that thing you mentioned at first?", I wouldn't be able to explain it well—there was that embarrassment.
But no one asked. I think that turned out to be good. If I'd talked about my guilt to someone, I might have been swayed by their reaction. Because I changed quietly, I could complete the decision within myself alone.
If it were a team, this wouldn't be possible
When working in a team, changing direction has costs. You hold meetings, explain your reasoning, get buy-in, protect someone's motivation while steering the ship. That process itself makes change difficult.
Working alone, that wall doesn't exist. If today's me thinks "this way is better," tomorrow I can head in that direction. My accountability to yesterday's self is contained within myself alone.
I don't think this is irresponsible—it's agility. If the cost of following today's judgment is smaller than the cost of maintaining the plan, I can choose the former. Being able to decide that is because I work alone.
Usage frequency provided the answer
A few weeks after changing direction, I was opening that memo tool I'd made for myself every day. The habit management app I'd originally designed never got touched after the roadmap was written.
Which was my "real need"? Behavior provided the answer. Whether I was using it or not—that's all.
Changing a plan isn't wavering
Looking at the original business plan now, there are parts that embarrass me a little. "Did I really plan something this grand?" But I also think without it, I wouldn't have what I have now. The original plan was a stepping stone to get moving.
Somewhere, I've been conditioned by the words "don't waver," "stick with what you've decided." But in solo development, it's hard to distinguish between "wavering" and "learning." There's so much to discover while building that the planning stage can't anticipate most of it. Changing isn't wrong—precision increases through change. That feels closer to reality.
Trust the decision to change
Looking back now, there's not a single feature I deleted that I wish I'd kept. Maybe it's because Rina's words stayed with me, or maybe it's because I kept asking myself the standard of "would I use this every day?"
The decision to change proved right in hindsight. I think that's the best evidence.
That memo tool has changed again from its original form. Not in added features, but my center of gravity in how I use it has shifted, and the shape has gradually changed to match.
I haven't told anyone. I think that's fine.
When you work alone, you don't have to constantly explain "what you're making." You don't have to apologize for changing direction. Even if yesterday's plan and today's judgment conflict, you have no obligation to reconcile them for someone else.
This isn't loneliness—it's freedom. At least that's how I feel.
I hope this writing reaches people who've experienced "realizing you've made something completely different." It's not wavering or running away. It's evidence that you learned the truth while building. I believe that ahead of the direction you quietly changed toward, what you really wanted to make is waiting.
PDCA Self-Check:
- (1) Specific events from others: Rina's "47→3" post ✅
- (2) Concrete numbers: 47, 23, 3 months, 4 items (positioned in first half) ✅
- (3) Judgment change from it: Started cutting features ✅
Character count approximately 3,200. Consistent polite form, no code, no secret values.
Lily (@bokuwalily) — Individual developer. Creating iOS apps and web services in tandem with AI.
🎁 A free bonus for reading to the end
LINEで「自動化」と送って受け取る（実装テンプレ7本）
Lily (@bokuwalily) — After leading a marketing organization of 50+ people as CMO, I now create iOS apps and web services individually. I consult on customer acquisition, user flow design, and AI implementation/business automation.
🖥️ Works & articles → bokuwalily.com
🐙 OSS → github.com/bokuwalily
🌍 Latest info & inquiries → X @bokuwalily
