--- title: "Predictability" description: "Predictability is defense by sameness." canonical: https://moa.giglabo.com/strategies/predictability/ locale: en --- # Predictability > Markdown twin of https://moa.giglabo.com/strategies/predictability/ — the same content as the HTML page, a fraction of the bytes. > Every page of this site has one: append `.md` to any URL, or `index.md` to a directory URL. > Site structure and the full page list for agents: https://moa.giglabo.com/llms.txt Category: Defense · Role: Holds · Depth: 4 Gist: repeatable, consistent experience ## Moats - [#8 Brand and trust](https://moa.giglabo.com/moats/8/) (direct, depth 4 · Mine) — The customer trusts that the next experience will match the last; each matching unit is a deposit and each surprise a withdrawal. - [#25 Habit](https://moa.giglabo.com/moats/25/) (direct, depth 2 · Excavator) — When the outcome is always the same, the choice stops being made; the customer reaches for you by reflex, and a rival must interrupt a reflex, not win an argument. ## Summary Predictability is defense by sameness. The customer knows exactly what they will get, in every place and every time, so choosing you costs no thought. That certainty is both a trust asset and a habit: the brand stands for a known outcome and the hand reaches for it without a decision. A rival has to be better and be known to be better, which is two problems. ## How it works The mechanism is the removal of decision cost. Every unfamiliar choice costs attention and carries a risk of disappointment; a predictable product prices both at zero. The customer who orders the same coffee in a new city is not buying the best coffee, they are buying the absence of a gamble. Producing that takes the opposite of craft: standard recipes, standard training, standard layouts, tight tolerances on the experience, and the discipline to suppress local variation even when a local variation would be better. The edge appears at scale and across contexts: the more places and moments you are the same, the more the sameness is worth. In software the same holds for interface stability, release cadence and the shape of the API. A team that knows your product will not surprise them builds on it and stops evaluating alternatives. ## Why it holds — or only takes Holds. Sameness kept over years becomes #8, trust: the buyer believes the next unit will match the last and stops verifying, and that belief is a mine, depth 4, because it needs years of matching units to exist. Sameness in the daily loop becomes #25, habit: the choice stops being a choice. Habit is shallower, depth 2, and eroding as AI agents make the choice on the customer's behalf. Both moats need repetition; a product used once a year can be predictable and hold nothing. ## Do you have it - Customers order without reading the menu or the changelog; they know what they will get. - Your product is the safe default in a team's stack: chosen to avoid a decision, not after one. - Complaints spike when you change anything, even for the better. - New locations or new versions hit the same satisfaction scores as the old ones from day one. ## How to dig it - Write the standard down: the recipe, the tolerances, the interface contract, and audit against it. - Version and deprecate slowly; announce every change long before it lands. - Train for sameness: the new hire reproduces the experience, not their own version of it. - Measure variance, not just the mean; the outlier is the thing that breaks the promise. - Put the same product in the customer's path daily so the reflex has something to form on. ## How it erodes - Sameness curdles into staleness; a rival's novelty looks like life next to your routine. - One inconsistent unit, location or release breaks the expectation and reopens the decision. - A context shift, a new device or a new channel, restarts the habit from zero. - An AI agent chooses for the customer and has no habits; it compares every time. - A rival copies the standard exactly and adds one thing; sameness alone was never the whole product. ## Solo, without capital You can be predictable from day one: a stable interface, a fixed release day, a changelog with no surprises, the same reply tone every time. Habit, #25, is fully within reach of a solo builder; put the product in a daily loop and keep it identical. Trust at depth 4 is not: it needs years and many matched units, and a solo builder's record is short. Do not confuse predictability with not shipping; ship on a schedule the customer can set a watch by. What the matrix says of its moats: - [#8 Brand and trust](https://moa.giglabo.com/moats/8/) — Solo: ~ partly · Capital: ◐ medium · AI: ↑ AI-resistant · Rent: ~ partly - [#25 Habit](https://moa.giglabo.com/moats/25/) — Solo: ✓ solo-reachable · Capital: ○ low · AI: → eroding · Rent: ✗ not for sale ## In nature, in business Nature: — Business: Disneyland, Starbucks - **McDonald's** — A Big Mac is assembled the same way in every franchise from a written operations manual, and the sameness is why a traveller walks in. - **Starbucks** — Starbucks fixed the sizes, the naming and the store layout so that the order and the outcome are the same in any city. - **Ubuntu** — Ubuntu ships a long-term-support release every two years on a fixed calendar, and the calendar is why operations teams standardise on it. ## Combines with - [Cloning](https://moa.giglabo.com/strategies/cloning/) — Identical copies are how sameness travels; a franchise or a template makes the tenth unit match the first. - [Standardization](https://moa.giglabo.com/strategies/standardization/) — A written standard is the thing that gets reproduced; predictability is what the customer feels when it holds. - [Reliability](https://moa.giglabo.com/strategies/reliability/) — Same every time and working every time are two halves of one promise; each makes the other believable. - [Omnipresence](https://moa.giglabo.com/strategies/omnipresence/) — The more places you are the same, the more the sameness is worth; reach multiplies predictability. [This strategy on the map](https://moa.giglabo.com/strategies/?view=lanes&hl=predictability) [Map this combination](https://moa.giglabo.com/strategies/?view=lanes&hl=predictability,cloning,standardization,reliability,omnipresence) ## Fights with - [Unpredictability](https://moa.giglabo.com/strategies/unpredictability/) — Surprise is the direct opposite; a product cannot be a reflex and a novelty in the same quarter. - [Divergence](https://moa.giglabo.com/strategies/divergence/) — Creative difference from the norm breaks the expectation that predictability spent years building. [Map this tension](https://moa.giglabo.com/strategies/?view=lanes&hl=predictability,unpredictability,divergence) ## Source Strategy taxonomy © kepano (Steph Ango), paraphrased with attribution. Role and moat mapping © Moat Atlas. https://stephango.com/ ## Related - HTML version of this page: https://moa.giglabo.com/strategies/predictability/ - Русский: https://moa.giglabo.com/ru/strategies/predictability/ - Previous: Reliability — https://moa.giglabo.com/strategies/reliability/ - Next: Unpredictability — https://moa.giglabo.com/strategies/unpredictability/ - Atlas: https://moa.giglabo.com/ - Catalogue: https://moa.giglabo.com/moats/ - Calculator: https://moa.giglabo.com/calculator/ - Strategies: https://moa.giglabo.com/strategies/ - Site map for agents: https://moa.giglabo.com/llms.txt