reflectionsOctober 23, 20261 min read

Before it feels ready

Waiting until something feels finished mostly delays the feedback that would tell you what finished means.

Every project has a version that lives only in my head: complete, polished, obviously right. The version I can ship is smaller and rougher, and the temptation is to keep working until the two match.

They rarely do. Most of the gap closes from the outside, once people start using the thing.

Two release plans over twelve weeksPolish, then launchShip small, keep shipping024681012

Week 12 · polish first: 1 release, 2 weeks of feedback · ship small: 6 releases, 10 weeks of feedback

Polish, then launch, or launch, then iterateA toy model of twelve weeks. It counts releases and weeks of feedback from real use, and knows nothing about quality.1.8s linear sweep · marks fill 120ms as the playhead passes

What a late launch costs

The study compares two plans over twelve weeks. One polishes in private and launches in week 10. The other ships something small in week 2 and keeps shipping. Pick how often it ships, then press Play.

It's a toy model. It counts releases and weeks of feedback and knows nothing about quality. Even so, it shows the part I keep forgetting: a late launch delays the release and every lesson queued up behind it.

An old idea

Eric S. Raymond put it plainly in The Cathedral and the Bazaar, describing how Linux was developed: "Release early. Release often. And listen to your customers." The last sentence carries the other two. Shipping early is worth very little if nobody is reading the replies.

The principles behind the Agile Manifesto say something similar for teams: deliver working software frequently, with a preference for the shorter timescale.

Small scope, same standards

Shipping early doesn't mean shipping broken. A first version can be narrow and still careful: one job done well, clear states, honest words. Cut the scope and keep the bar where it was.

When the Lab on this site went up, the useful fixes came from seeing it in a real browser: a name cut off at one width, a "Copied" label sitting off-centre. Neither was visible in my head.

Ready is a feeling

I've stopped waiting for the feeling of readiness, because it doesn't arrive on schedule. I ask three questions instead. Does it do its one job? Does it fail gracefully? Do I know how I'll hear from the people using it? Three yeses and it's ready enough to learn from.