> ## Content Index > Fetch the complete content index at: https://bastian.ghost.preview.themeanax.com/llms.txt > Use this file to discover other available public pages before exploring further. # The Model Is Not the Product - URL: https://bastian.ghost.preview.themeanax.com/the-model-is-not-the-product/ - Published: 2026-09-07T12:47:53.000Z - Updated: 2026-09-07T12:48:03.000Z - Description: Artificial intelligence is one of those topics where the obvious answer is right about sixty per cent of the time, which is exactly often enough to be dangerous. - Author: Bastian Team - Tags: #themeseed, Artificial intelligence, Notes, Artificial The interesting thing about artificial intelligence is how rarely the hard part is the part everyone prepares for. ## Where to start on Monday There is a version of artificial intelligence that is mostly ritual. The things that are easy to count are rarely the things that matter, and once a number reaches a dashboard it starts shaping behaviour whether or not it deserves to. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer. ![a computer circuit board with a brain on it](https://bastian.ghost.preview.themeanax.com/content/images/2026/09/photo-1677442135703-1787eea5ce01.jpg) Photo by Steve A Johnson on Unsplash Measurement is usually where this falls apart. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem. The expensive mistakes here are rarely the technical ones. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. ## What to do first A shared definition of "done" removes more friction than any tool. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests. Documentation is a symptom: you write it where the design is unclear. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. The version of this that works fits on an index card. The version that fails needs an onboarding session. ## The one people skip The second-order effects arrive about a quarter after the first-order ones. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not. The tooling question is downstream of the constraint question. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. ## The one that only matters at scale The default answer is right often enough to be dangerous. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The first thing to establish is what you are actually optimising for. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The compounding effects matter far more than the individual wins. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound. ## The expensive mistake Speed and reversibility are the trade-off worth naming out loud. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. It helps to separate the decision from the execution. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. Nobody gets credit for the work that did not need doing. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. When we mapped it out, four of the seven steps existed only to compensate for the second one. > Every process is perfectly designed to get the results it gets. — Overheard in a retrospective ## Begin with the obvious one Feedback loops shorter than the planning cycle change everything. Artificial intelligence rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Most of the difficulty lives at the boundaries, not in the middle. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. It is worth saying that we have not run this long enough to be confident. Scope is the variable everyone adjusts last and should adjust first. The first quarter shows the intended effect; the second shows what the intended effect displaced. Set a date at which you will stop, and write down in advance what would make you stop earlier. ## The habit that compounds The interesting constraint is almost never the one in the brief. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. What looks like a process problem is frequently an ownership problem. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. That said, none of this generalises cleanly across team sizes. ## The quiet win Consistency is worth more than any individual improvement to artificial intelligence. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it. Consider the failure mode rather than the success case. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The compounding effects matter far more than the individual wins. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison. ## The advice worth ignoring The default answer is right often enough to be dangerous. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. Scope is the variable everyone adjusts last and should adjust first. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. What we look for now: 1. Review the numbers monthly; change the targets rarely 2. Decide in advance what would make you stop 3. Name one person accountable — not a group ## Where to start on Monday The tooling question is downstream of the constraint question. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. The evidence here is thinner than anyone quoting it tends to admit. It helps to separate the decision from the execution. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. In practice the answer showed up in the calendar before it showed up in the dashboard. ## What to do first The interesting constraint is almost never the one in the brief. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. This is easier to write than to hold to when a deadline appears. Measurement is usually where this falls apart. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. There are organisations where the opposite is true, and they are not obviously worse off. ## The one people skip The first thing to establish is what you are actually optimising for. Artificial intelligence rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The clearest signal was that people stopped asking where things were. Nobody gets credit for the work that did not need doing. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Consider the failure mode rather than the success case. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. ## The one that only matters at scale Documentation is a symptom: you write it where the design is unclear. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. A useful test: if this disappeared tomorrow, how long before anyone noticed? Most of the difficulty lives at the boundaries, not in the middle. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not. If there is one thing worth carrying away, it is that the expensive mistakes in artificial intelligence are almost never technical ones.