What 'ship and tend' really means after launch

Launch day gets all the attention and deserves the least of it. It's a single moment, easy to plan for, easy to celebrate, and almost meaningless on its own. What happens in the weeks and months after is the part that actually determines whether the thing you built was worth building. We release early, listen closely, and keep improving, because a product is a commitment, not a launch.

"Tend" is a deliberately unglamorous word, and we chose it over "iterate" or "optimize" on purpose. Those words imply a process happening to metrics. Tending implies a process happening to a living thing that will suffer if you stop paying attention to it. A product that's tended gets small, timely corrections. A product that's merely iterated on gets big, delayed ones, usually after the damage from neglect has already accumulated.

A product that's tended gets small, timely corrections. A product that's merely iterated on gets big, delayed ones.

This has a direct implication for how we think about scope: we release early precisely because we intend to keep working on it, not despite that intention. A team that treats launch as the finish line has to get everything right before shipping, which means shipping later and with more invented certainty than anyone actually has. A team that treats launch as the start of tending can ship a smaller, honest version sooner and correct it against real use, which is a better source of certainty than any amount of pre-launch guessing.

We apply this to client engagements the same way we apply it to our own products: the relationship doesn't end at handoff if the client wants it to continue, because we don't believe good software is a one-time delivery. It's closer to something you keep watering.