I shipped it. Then I rebuilt it 22 times.

We love the launch story. Ship it, screenshot the announcement, take the win.

Here's the part nobody posts about. After launch, I rebuilt pieces of one product 22 more times.

Twenty-two rounds of reality

Not a rewrite. 22 rounds of small, feedback-driven fixes. Real people used the tool I'd built, and reality started sending notes the plan never could.

The title link opened the editor. Turns out people want to look before they edit, so viewing became the default and editing became the deliberate click.

The download button needed to sit where I'd put an edit button, because that's the button people actually reached for first.

And a "regenerate share link" quietly inherited the old link's expiry date, so brand-new links were dead on arrival. Nobody finds that in a planning doc. A user found it in a week.

None of these were in the original blueprint. They couldn't have been. That's the whole point.

It's also why I've stopped trying to build the general case first. Every product I've taken to production started narrower than the ambition, on purpose, because the fastest way to learn you were wrong about the big version is to ship the small one and watch what breaks. Twenty-two rounds is what "narrow first" actually costs. It's a fair price.

Your first version is a first draft

Think of your first version as a first draft written before you've met your reader. It's your best honest guess at how people will behave, and by definition it's wrong in ways you can't see yet, because you haven't watched anyone use it.

Let me say the thing I wish more teams believed: launch isn't the finish line. It's the moment your roadmap finally touches reality, and reality starts talking back.

The teams I trust most aren't the ones with the cleanest launch. They're the ones still listening at fix number 22.

So let me ask you. What did your users teach you after launch that no amount of planning ever could?