What Nobody Tells You About Getting Started
Personal · 2026-08-13
What Nobody Tells You About Getting Started
Starting things is harder than it looks. Every single time, regardless of how prepared you feel or how clear the idea is.
There's a widely repeated belief that the hardest part is having the idea — that once you know what you want to build, the rest unfolds naturally. It's an appealing story. But it doesn't hold up. The idea is the easy part. It's free, it costs nothing, and it usually arrives in about four seconds — in the shower, on a walk, or right as you're falling asleep.
The hard part is what comes next. The unglamorous Tuesday where you actually sit down and do the work, with no audience, no applause, and no guarantee it's going to come together. Just you, the thing, and a lot of rough early attempts.
The Physics of Starting
Think about momentum in the most literal sense. An object at rest stays at rest unless something acts on it. Most projects stall not because of laziness or lack of intent, but because starting requires a kind of activation energy that the middle of a project simply doesn't need anymore. Once something is moving, it tends to keep moving. The difficulty is concentrated right at the beginning — in the stillness before motion.
That discomfort at the start isn't a signal that something is wrong. It's just what starts feel like: uncertain, a little uncomfortable, full of small failures that feel disproportionately significant because there's no accumulated evidence yet that the thing is going to work.
Early Is Supposed to Be Clunky
Consider a product or project in its first week of existence. Nothing works quite the way it was imagined. The gaps between vision and execution feel enormous. That experience is nearly universal — and it's almost always misread as a sign that something has gone wrong, when in reality it's simply a description of what early-stage work looks like.
Clunkiness at the start isn't a warning sign. It's a developmental stage. The question isn't whether the first version is rough — it will be — but whether you stay in it long enough to find out what it becomes.
Ready Is a Moving Target
The idea that there's a right moment to begin — a morning where everything clicks into place and you feel genuinely prepared — is one of the more persistent myths around creative and professional work. That moment doesn't arrive. Waiting for it is a mechanism for delay dressed up as diligence.
What actually works is starting underprepared and learning as you go, mostly by making small, recoverable mistakes in the early stages rather than large, costly ones later.
The practical implication of this is worth sitting with: lower the stakes of the first attempt. Not the ambition — that can stay as large and slightly terrifying as you like. But the first version? Make it small. Make it almost embarrassingly minimal. The goal on day one isn't to build the whole thing. It's to prove to yourself that the thing can exist at all, even in its roughest, most incomplete form.
Why This Philosophy Shapes How We Build at jstov
At [jstov](/), this thinking sits at the core of how we approach every new project and client engagement. We prioritise small, functional, working versions over large, polished, theoretical ones — not because ambition is unwelcome, but because a working version, however rough, generates real learning. A polished imaginary one generates nothing except more planning.
It's not a glamorous framework. But it's the approach we've seen hold up consistently, across projects of different scales and industries. You build something real, however small, and then you improve it. That sequence matters. The improvement can only happen once the thing exists.
The Only Real Message
If you're sitting with an idea right now — something you've been circling, waiting until you feel more ready — the honest answer is that the readiness you're waiting for isn't coming. Nobody starts ready. The preparation happens through the doing, not before it.
Start anyway. Start small. Stay in the clunky early phase long enough to find out what you're actually building.
That's the part nobody tells you: the discomfort isn't a detour from the process. It is the process, at least at the beginning. Once you know that, it gets a little easier to keep going.