PromptGarden

A model is not a forecast

A spreadsheet full of assumed conversion rates cannot be hit or missed — it just restates its inputs back to you in a confident font. The fix is not better guessing. It is labeling every number as a fact or an assumption, and treating the whole plan as a machine for turning the second kind into the first.

· Essay

There is a particular kind of spreadsheet that feels like knowledge and is actually a mirror. You build a revenue model: visitors times a conversion rate times a price, summed across products, compounded across months. The bottom-right cell says something enormous. It feels like a forecast. It is not. Almost every input was a number you typed because it seemed reasonable — a two percent conversion here, a thousand visitors there — and the giant total is just those guesses multiplied together and handed back to you in a confident font. You cannot hit it or miss it. It restates its inputs.

This matters because a model dressed as a forecast quietly changes how you behave. You start defending the number instead of testing it. You feel busy and on-track because the projection still says so, while the one thing the projection cannot contain — whether a single real stranger will pay you — goes unmeasured for weeks. The spreadsheet is not lying, exactly. It is doing precisely what you built it to do. The mistake is asking it a question it was never able to answer.

The fix is not better guessing. It is a labeling habit so simple it sounds trivial: tag every number in the plan as a fact or an assumption. A fact is something you measured — a real transaction, a real click-through, a count you could show someone. An assumption is everything else, no matter how confident it feels. Then you look at your grand total and notice, often for the first time, that ninety percent of it is standing on assumptions and maybe one cell is a fact. That is not a failure. That is the map finally telling the truth about the terrain.

Once the numbers are labeled, the whole plan reorganizes itself around one job: converting assumptions into facts as fast as possible. The assumed two percent conversion is not a thing to defend — it is a thing to go replace with a measured rate from a live page. The modeled price is a thing to test against a real checkout. Every week you should be able to point at one number that used to be a guess and is now a measurement. Progress stops being "the projection still looks good" and becomes "we retired three assumptions and two of them came back worse than we hoped." The second kind of progress is the only kind that compounds, because it is the only kind that is real.

This is also where a quiet discipline earns its keep: you never let an assumption walk out the door wearing a fact's clothes. The confident total is fine to steer by internally, as long as it is labeled — a stretch star, not a promise. But it never becomes a public claim, a marketing stat, or a number on a landing page, because the moment an unmeasured figure faces a customer, you have converted a modeling convenience into a lie. Sell with the things you can actually stand behind. Model with the things you are still guessing. Keep the wall between them, and label which side every number lives on.

So treat the plan as a machine, not a prophecy. Its output is not a target to be admired; it is a to-do list of assumptions ranked by how much they matter. Point the whole operation at the biggest unmeasured guess, go turn it into a fact, and repeat. A forecast tells you a comforting story about a future you cannot see. A labeled model tells you the one true thing you can act on today — which of your beliefs you have actually earned, and which one to go earn next.

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