> ## Content Index > Fetch the complete content index at: https://norvane.ghost.preview.themeanax.com/llms.txt > Use this file to discover other available public pages before exploring further. # Opinion: We Are Measuring the Wrong Things in Public Life - URL: https://norvane.ghost.preview.themeanax.com/opinion-we-are-measuring-the-wrong-things-in-public-life/ - Published: 2026-08-22T09:28:19.000Z - Updated: 2026-09-08T08:04:31.000Z - Description: Most teams arrive at independent international news the same way: something breaks, and the fix becomes a habit. - Author: Norvane - Tags: #themeseed, Independent international, Teardown, Independent Most teams arrive at independent international news the same way: something breaks, and the fix becomes a habit. ## The quiet win The expensive mistakes here are rarely the technical ones. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The clearest signal was that people stopped asking where things were. ![the new york times newspaper](https://norvane.ghost.preview.themeanax.com/content/images/2026/09/photo-1611287158944-8ea51f26e4fa-1.jpg) Photo by little plant on Unsplash Documentation is a symptom: you write it where the design is unclear. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. When we mapped it out, four of the seven steps existed only to compensate for the second one. The default answer is right often enough to be dangerous. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. A useful test: if this disappeared tomorrow, how long before anyone noticed? ## Begin with the obvious one Measurement is usually where this falls apart. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. ![A news paper with the word news on it](https://norvane.ghost.preview.themeanax.com/content/images/2026/09/photo-1738190228336-aa4cf73874b7.jpg) ![a newspaper with a picture of a man on it](https://norvane.ghost.preview.themeanax.com/content/images/2026/09/photo-1579532582940-957ceba4f373.jpg) ![text](https://norvane.ghost.preview.themeanax.com/content/images/2026/09/photo-1613441589134-3fc7f95a3e16.jpg) Independent international news in practice Scope is the variable everyone adjusts last and should adjust first. Independent international news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not. The second-order effects arrive about a quarter after the first-order ones. 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 one people skip A shared definition of "done" removes more friction than any tool. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. It is worth saying that we have not run this long enough to be confident. It helps to separate the decision from the execution. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. Feedback loops shorter than the planning cycle change everything. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. That said, none of this generalises cleanly across team sizes. ## The advice worth ignoring Speed and reversibility are the trade-off worth naming out loud. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. In practice the answer showed up in the calendar before it showed up in the dashboard. Consistency is worth more than any individual improvement to independent international news. 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. ## Where to start on Monday 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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it. Most of the difficulty lives at the boundaries, not in the middle. The first quarter shows the intended effect; the second shows what the intended effect displaced. The version of this that works fits on an index card. The version that fails needs an onboarding session. What looks like a process problem is frequently an ownership problem. 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 to do first There is a version of independent international news that is mostly ritual. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. 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. There are organisations where the opposite is true, and they are not obviously worse off. The compounding effects matter far more than the individual wins. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests. > You can have it fast, or you can have it reversible. Pick before you start, not after. — Overheard in a retrospective What we look for now: 1. Keep the feedback loop shorter than the planning cycle 2. Agree on what "done" means, in writing, before starting 3. Write the constraint down before choosing a tool ## The one that only matters at scale The interesting constraint is almost never the one in the brief. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The first thing to establish is what you are actually optimising for. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. ## The habit that compounds Consider the failure mode rather than the success case. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer. 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. ## The expensive mistake The compounding effects matter far more than the individual wins. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. 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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison. There is a version of independent international news that is mostly ritual. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. ## The quiet win The first thing to establish is what you are actually optimising for. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound. Nobody gets credit for the work that did not need doing. Independent international news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. In practice the answer showed up in the calendar before it showed up in the dashboard. Most of the difficulty lives at the boundaries, not in the middle. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. The evidence here is thinner than anyone quoting it tends to admit. ## Begin with the obvious one 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 second-order effects arrive about a quarter after the first-order ones. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. ## The one people skip Documentation is a symptom: you write it where the design is unclear. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Feedback loops shorter than the planning cycle change everything. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison. The interesting constraint is almost never the one in the brief. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. This is easier to write than to hold to when a deadline appears. None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.