> ## Content Index > Fetch the complete content index at: https://meridian.ghost.preview.themeanax.com/llms.txt > Use this file to discover other available public pages before exploring further. # Opinion: Every Industry Is Now a Data Business, and Most Are Bad at It - URL: https://meridian.ghost.preview.themeanax.com/opinion-every-industry-is-now-a-data-business-and-most-are-bad-at-it/ - Published: 2026-06-17T10:17:30.000Z - Updated: 2026-09-08T10:35:54.000Z - Description: Ask ten people to define business and you will get ten answers, most of them describing a symptom rather than the thing itself. - Author: Meridian - Tags: #themeseed, Business, Opinion Ask ten people to define business and you will get ten answers, most of them describing a symptom rather than the thing itself. ## Where it still breaks The compounding effects matter far more than the individual wins. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. It is worth saying that we have not run this long enough to be confident. ![a woman in a turban is driving a car](https://meridian.ghost.preview.themeanax.com/content/images/2026/09/photo-1709985532799-92d35afb7593.jpg) Photo by Boston Public Library on Unsplash Feedback loops shorter than the planning cycle change everything. The first quarter shows the intended effect; the second shows what the intended effect displaced. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound. 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. ## What changed Documentation is a symptom: you write it where the design is unclear. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. In practice the answer showed up in the calendar before it showed up in the dashboard. The Real Reason Companies Have Become Obsessed With Your Data The interesting constraint is almost never the one in the brief. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. ## The numbers A shared definition of "done" removes more friction than any tool. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. Set a date at which you will stop, and write down in advance what would make you stop earlier. The first thing to establish is what you are actually optimising for. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. When we mapped it out, four of the seven steps existed only to compensate for the second one. The expensive mistakes here are rarely the technical ones. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. ## How we knew it was working The second-order effects arrive about a quarter after the first-order ones. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. There are organisations where the opposite is true, and they are not obviously worse off. Consider the failure mode rather than the success case. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The tooling question is downstream of the constraint question. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem. ## The situation What looks like a process problem is frequently an ownership problem. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. That said, none of this generalises cleanly across team sizes. There is a version of business that is mostly ritual. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it. > You can have it fast, or you can have it reversible. Pick before you start, not after. — Overheard in a retrospective ## The part that surprised us Consistency is worth more than any individual improvement to business. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison. The default answer is right often enough to be dangerous. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Speed and reversibility are the trade-off worth naming out loud. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. A useful test: if this disappeared tomorrow, how long before anyone noticed? ## What it cost Scope is the variable everyone adjusts last and should adjust first. 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. It helps to separate the decision from the execution. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Measurement is usually where this falls apart. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. This is easier to write than to hold to when a deadline appears. What we look for now: - Decide in advance what would make you stop - Review the numbers monthly; change the targets rarely - Keep the feedback loop shorter than the planning cycle ## What we tried first Nobody gets credit for the work that did not need doing. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests. The interesting constraint is almost never the one in the brief. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. The evidence here is thinner than anyone quoting it tends to admit. ## What we would do differently It helps to separate the decision from the execution. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Consistency is worth more than any individual improvement to business. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The clearest signal was that people stopped asking where things were. Documentation is a symptom: you write it where the design is unclear. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. This is easier to write than to hold to when a deadline appears. ## Where it still breaks Feedback loops shorter than the planning cycle change everything. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. The evidence here is thinner than anyone quoting it tends to admit. The expensive mistakes here are rarely the technical ones. 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. Speed and reversibility are the trade-off worth naming out loud. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound. ## What changed Scope is the variable everyone adjusts last and should adjust first. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The version of this that works fits on an index card. The version that fails needs an onboarding session. The compounding effects matter far more than the individual wins. The first quarter shows the intended effect; the second shows what the intended effect displaced. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer. The second-order effects arrive about a quarter after the first-order ones. 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. If there is one thing worth carrying away, it is that the expensive mistakes in business are almost never technical ones.