What is done

This question comes up a lot: How do I know when it’s ready?

The honest answer is… it’s never finished.
But it can absolutely be done enough.

“Done enough” means your product can stand on its own without you explaining it. If someone can understand what it’s for, what to do, and what happens next — you’re there.

Early on, I used to wait for confidence. Now I wait for signals.

Here are the signals I look for:

• Users complete the core action without help

• The same questions come up repeatedly (this is good — it means patterns)

• Feedback shifts from “what is this?” to “what if it also did…”

• I’m making small tweaks instead of big structural changes

That’s usually the moment to share it more widely.

Another trap is thinking “world” means thousands of people. It doesn’t. Your world might be:

• 10 users

• A Slack group

• A client

• An investor

• A workshop room

Scale comes later. Learning comes first.

I also remind myself that showing work isn’t a performance — it’s a conversation. You’re inviting people into the process, not pitching a final product.

If you wait until it’s perfect, you lose the chance to shape it with users. And that’s where the best ideas usually come from.

One practical trick I use is a “confidence checklist”:

• Can I explain the value in one sentence?

• Does the prototype support that sentence?

• Can I change it quickly if feedback surprises me?

If the answer is yes, I ship.

And here’s the quiet part people don’t say enough: showing unfinished work builds trust. People like being part of something early. They like seeing progress. It makes your product feel human.

Momentum doesn’t come from polish.
It comes from progress you’re willing to share.