There's a moment everyone waits for and no one reaches: the moment you feel ready. Ready means the skills are all there, the plan is sound, the funding is lined up, the timing is right. It's a comforting thing to wait for, and it never arrives, because readiness in that complete sense is not a real state. It's a story we tell ourselves to justify not starting yet.
What's actually true is that you learn the thing by doing the thing, which means you are never ready before you start, by definition. The skills you're waiting to acquire are precisely the ones the work would teach you. So waiting to feel ready is waiting for an effect to precede its cause. You can wait a very long time for that, and many talented people do, and they call it being careful.
I don't mean recklessness. There's a difference between starting before you're ready and starting before you've thought at all. The point isn't to skip preparation. It's to recognize that past a certain point, more preparation stops teaching you anything, and the only remaining way to learn is to make contact with reality. Reality is a harsh teacher but a fast one, and it grades on things the plan never tested.
The builders who get somewhere tend to start while they still feel unqualified, and then learn in public, in front of users, with a product that's visibly incomplete. This is uncomfortable, because incompleteness is exposure, and exposure feels like risk. But the discomfort is the price of the only information that matters, which is how real people respond to a real thing rather than how you imagine they'll respond to an imagined one.
There's a failure mode on the other side, and it's worth naming so this doesn't sound like a license to ship garbage. Some people start before they're ready and then never get more ready, shipping the same half-thing forever and calling it iteration. Starting early only works if you actually use what you learn — if each rough version teaches you something the next one fixes. Motion without learning is just a different way to stall.
But assuming you're learning, premature is usually just early enough. The cost of a rough first version is small and bounded: some embarrassment, some wasted effort, a few users who saw the thing before it was good. The cost of the perfect version that ships too late, or never, is everything — the whole opportunity, gone to someone who started while they still felt unqualified and figured it out along the way.
I think the deeper issue is that 'ready' is doing emotional work, not practical work. When people say they're not ready, they usually mean they're afraid, and 'not ready' sounds more responsible than 'afraid.' Naming it honestly helps, because fear is a reasonable thing to feel and a bad thing to obey. The fear doesn't go away when you start. It just stops being in charge.
So if you're waiting for the feeling of readiness before you begin, you can stop waiting. It isn't coming. What comes instead, if you start, is competence — earned slowly, in public, through a sequence of versions that are each a little less embarrassing than the last. That's the only path there is. The ready feeling, when you finally get it, arrives years after you started, as a result, never as a prerequisite.