The instinct is to wait. Finish it. Polish it. Make it good before anyone sees it. The problem is that “good” is a moving target you can’t hit without outside eyes — so you polish in private, forever, and the thing never ships.

The fix is uncomfortable and it works: ship the half-done thing, on purpose, and let real feedback do the editing you can’t do alone.

Why “done in private” is a trap

Polishing in private has two hidden costs that usually don’t show up on any timeline:

  • You’re editing against yourself. The only person judging the work is the person closest to it — who is exactly the wrong person. You can’t see the parts that confuse a stranger, because you wrote them. You can’t hear the missing step, because you already know it.
  • The novelty decay clock is running. The longer a thing sits unfinished, the less you want to finish it. That’s the week-three wall in its purest form: the energy to ship doesn’t survive the distance you insist on keeping between “started” and “seen.”

“Good enough to show” is a real milestone, and it arrives a lot sooner than “done.” Treat arriving there as the ship point, not the halfway point.

What feedback actually buys you

When you show a half-done thing, the feedback you get back is not a grade — it’s a map. Three specific things it tells you that you cannot learn alone:

  1. Which direction is wrong. A stranger spots a dead end in ten seconds that you’d defend for a month, because they don’t have your sunk cost.
  2. What’s actually confusing. The step you thought was obvious turns out to be the single thing nobody follows. You’d never find it yourself — it’s invisible to you.
  3. Whether anyone wants it at all. The most valuable feedback is silence followed by a flat question: “what’s it for?” That’s the cheapest market test there is, and it only costs a half-done draft.

Each of these is a defection risk uncovered before you’ve sunk the full cost. That’s the whole economic case for shipping early: feedback is cheaper when the thing is still cheap to change.

The exact move

  • Pick the smallest shippable slice. Not the feature, the slice — the one thing a person could look at and react to. A landing page. A single screen. A paragraph that makes the argument.
  • Show one real person, not the void. Broadcasting into a crowd is performance; showing one person who’ll actually respond is editing. One honest reader beats a hundred silent impressions.
  • Ask one specific question. Not “what do you think?” — that invites politeness. Ask “what’s confusing here?” or “would you pay for this?” A pointed question gets a pointed answer.
  • Ship the revision, not the debate. Take the one piece of feedback that matters, fold it in, ship again. The loop is the product.

Why this beats polishing

Here’s the honest part: the half-done thing you ship will be worse than the finished thing you imagine. That’s fine, because the imagined finished thing has a flaw — it’s imaginary. The real thing, shipped and revised, exists, and existence is what compounding runs on (see the ship one tiny thing loop — this is that system applied to one launch instead of a weekly cadence).

Perfectionism isn’t a quality standard. It’s a delay mechanism dressed up as one. The builders who ship early and revise in public aren’t sloppier than you — they’re running a tighter feedback loop, and it’s the loop that wins.

This is the “ship ugly, then edit” half of the ship-one-tiny-thing system — and the antidote to the perfectionism that feeds the week-three wall.

Sources

  • Carta — Solo Founders Report 2025: solo founders’ persistence (36% of new startups) is correlated with faster time-to-launch and iteration cadence, not bigger pre-launch polish.
  • Ericsson — deliberate-practice literature: skill is built from frequent feedback-rich iterations, not prolonged private refinement; shipping early is that principle applied to product, not just practice.