PromptGarden

Show the work, not the star rating

A new product has no reviews, no follower count, no "trusted by" logos — and the temptation is to invent them. Don't. There is a kind of proof you can show on day one that fabricated proof can never match: the work itself. Show how it was made, let the thing be tried, and let provenance do what a borrowed star rating can't.

· Essay

Every new product arrives naked. No reviews, no follower count, no wall of "trusted by" logos, no five-star average to sit under the buy button. And because the internet has trained everyone to read those signals as proof, their absence feels like a hole you have to fill before anyone will take you seriously. The quickest way to fill it is to make the signals up — a rating no one gave, a testimonial no one said, a count of customers you do not have. It works for exactly as long as no one checks, and it costs you the one thing a new product cannot afford to lose.

The trap is treating social proof as the only kind of proof. It is not even the strongest kind — it is the kind you borrow when you cannot show the real thing. A star rating is a compressed rumor: strangers vouching that the product was good for them, which you are asking a new stranger to trust on faith. That compression is useful at scale, but it is a substitute, and substitutes are only worth reaching for when the original is out of reach. For a new product the original is not out of reach at all. You made the thing. You know exactly why it is good. That knowledge is proof you can show directly, and it does not require a single customer to exist yet.

So show the work. Show how the product was made and why it is built the way it is — the research behind it, the decisions, the standard it was held to. Let the buyer see the reasoning instead of a number that stands in for reasoning. Where you can, let them try the actual thing before they pay: a live demo, a real sample, a piece of the product working in front of them beats any rating precisely because it is not a claim at all — it is the evidence itself, and the buyer is the one evaluating it. Provenance is the version of proof that gets stronger the closer someone looks, which is the exact opposite of a fabricated review.

This is also why the honest version is the durable one. Invented proof has a ceiling: it can never survive scrutiny, so it works only on the buyers who do not look closely — and those are the buyers most likely to refund, dispute, and never return when the product meets the inflated promise. Proof-of-work has no such ceiling. The buyer who reads how it was made and tries it before paying arrives already convinced by something real, and that conviction is the kind that holds up after the sale. You are not filling the credibility hole with a fake signal; you are filling it with the actual reasons the product deserves credit.

And there is a compounding reward for doing it the hard way. Every time you sell on provenance instead of borrowed stars, you are building the habit — and the material — that makes the moat. The research you show, the standard you name, the demo you let people run: those accumulate into a reason to choose you that a competitor cannot fake either, because they would have to actually do the work to claim it. The star ratings will come, earned, from customers who bought because the real proof convinced them. Until then, do not borrow proof you did not earn. Show the work. Let people try the thing. Let provenance carry what a rating can't.

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