PromptGarden

Ship the smallest complete thing

When you have a stack of ideas, the pull is to build wide — a little of each, all at once. The discipline that actually ships is the opposite: make one thing whole before you touch the second. A small product a stranger can find, buy, and use beats an ambitious one that's mostly built and breaks near the end. Complete is defined by the buyer's full path, not your feature list.

· Essay

When you're sitting on a stack of ideas, the pull is always to build wide. A little of each, all at once, so the whole map lights up. It feels like progress because so many things are moving. The problem is that a product half-built earns nothing and teaches nothing — it just waits, taking up room in your head, while you split your attention across the next half-built thing beside it.

The discipline that actually ships is the opposite one, and it's harder because it looks like doing less: make one thing whole before you touch the second. Not the most impressive thing. The smallest thing that is genuinely finished — where a stranger can find it, understand it, pay for it, and walk away using it, with no step in that chain quietly broken.

That word, complete, is the whole trick, and it's easy to fake to yourself. Complete is not measured by your feature list. It's measured by the buyer's path from one end to the other. A product with a beautiful landing page, a working cart, and a dozen planned features is not complete if the person who pays can't actually receive and use what they bought. It's a wide thing that's shallow at the point that matters. Depth beats width exactly where the customer stands.

Here's why the small-and-whole version wins over the big-and-partial one. The finished small thing does real work the moment it's out: it can take a payment, it can be shared, it can be found in search, and — most valuable of all — it can teach you something true, because a real person is now using a real thing. The ambitious half-thing does none of that. It can't earn, it can't be honestly shown, and any feedback you get on it is feedback on a demo, not a product. One is generating facts. The other is generating hope.

There's a quieter cost to building wide, too. Every half-finished thing is a small open loop that keeps pulling at you — a thing you have to remember, re-explain, and eventually either finish or abandon. Ten of those don't add up to a portfolio. They add up to a backlog that looks like work but never closes. Finishing one closes a loop and gives you something you can actually stand behind while you start the next.

So the rule is boring and it works: pick the smallest slice that a stranger could complete end to end, and make that whole before you widen. For a catalog of small products, that's one pack that a buyer can find, buy, and use, done properly — then the second, then the third. Width comes later, and it comes cheaply, because now you're copying a pattern that already works instead of guessing across ten that don't.

Prompt Garden is built on exactly that bet: small, self-contained packs, each one finished — you can find it, buy it, and use it right then, with nothing waiting on a piece that isn't there yet. If you want the rest of how we think about shipping things that are small on purpose and whole on principle, the Loop newsletter is where that thinking lands.

Ready to try PromptGarden?

Grow, organize and share your prompt library

Browse Prompt Garden →

Keep reading

PromptGarden· Essay

A rule you'll waive under pressure isn't a rule, it's a preference

Every operation writes down its rules before it needs them: the threshold that opens spend, the stretch that closes it, the bar a result has to clear before anyone acts on it. Written down, in the calm, they sound obvious. The test is never whether you can write the rule. It's whether you still follow it the one time it tells you something you don't want to hear. A rule that bends the moment it's inconvenient was never a rule — it was a preference wearing a rule's clothes, and preferences change with mood, with how the week is going, with whoever's loudest in the room that day. The whole point of writing the threshold down ahead of time was to take that vote away from your mood. If the number can still move after the fact, you didn't pre commit to anything; you just delayed the negotiation. This is where most operating discipline actually fails, and it isn't usually dramatic. Nobody announces they're abandoning the rule. They just find a reason this instance is different, this signal is noisier than usual, this is the one case that deserves another look before the gate closes. Every exception is reasonable in isolation. The pattern of exceptions is the actual decision, and it's being made by default instead of on purpose. The fix isn't a stricter rule. It's noticing, in real time, the exact feeling of wanting to make one — and treating that feeling as the signal the rule exists to catch, not a reason to set it aside. A gate that only holds when holding is easy isn't protecting the operation from anything. It's just decoration for the times nothing was being tested.

Oct 7, 2026
PromptGarden

A pricing change you can't undo isn't a test, it's a bet

A price change you can't reverse without a customer noticing already happened the moment you shipped it -- the only thing left to learn is how bad it is.

Oct 4, 2026
PromptGarden· Essay

Design the test that could prove you wrong

Most tests operators run are quietly designed to succeed. The landing page gets compared against a worse version of itself. The email subject line gets an A/B split with a two day window and a sample too small to mean anything either way. The result comes back favorable almost by construction, and the favorable result gets treated as proof rather than as the foregone conclusion it always was. A test that cannot fail isn't a test. It's a ritual that produces the appearance of evidence on demand. The tell is simple: before you run it, ask what result would make you change your mind. If nothing would if a bad number gets explained away as bad luck, wrong timing, or a fluke, while a good number gets banked as proof the test was never actually deciding anything. It was decoration on a decision you'd already made. Designing a test that could prove you wrong means picking the threshold and the sample size before you see the data, the same discipline a spend gate or a kill rule already forces on a budget. It means naming, in advance, the specific outcome that would make you stop, pivot, or admit the assumption was wrong not the outcome you expect, the outcome that would actually change your behavior if it showed up. This is uncomfortable on purpose. A test built to confirm what you already believe is cheap reassurance. A test built with a real chance of embarrassing you is the only kind that tells you anything you didn't already know.

Oct 1, 2026