> ## Content Index > Fetch the complete content index at: https://baseline.ghost.preview.themeanax.com/llms.txt > Use this file to discover other available public pages before exploring further. # Legacy automakers and the software-defined vehicle problem - URL: https://baseline.ghost.preview.themeanax.com/3-small-changes-that-improve-industry-insights/ - Published: 2026-08-04T23:45:00.000Z - Updated: 2026-09-08T12:14:42.000Z - Description: Carmakers built for stamping steel are learning, painfully, to ship software on a vehicle's timeline. - Author: ThemeAnax - Tags: #themeseed, Industry insights, Teardown, Industry We spent a quarter trying to get Industry insights right, and the useful lessons were not the ones we expected. ## The incentive problem Consistency is worth more than any individual improvement to Industry insights. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. ![graphs of performance analytics on a laptop screen](https://baseline.ghost.preview.themeanax.com/content/images/2026/09/photo-1551288049-bebda4e38f71-10.jpg) Photo by Luke Chesser on Unsplash Measurement is usually where this falls apart. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. A useful test: if this disappeared tomorrow, how long before anyone noticed? A shared definition of "done" removes more friction than any tool. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Set a date at which you will stop, and write down in advance what would make you stop earlier. ## A different reading There is a version of Industry insights that is mostly ritual. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem. The first thing to establish is what you are actually optimising for. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. It is worth saying that we have not run this long enough to be confident. 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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer. ## The received wisdom Nobody gets credit for the work that did not need doing. 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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not. The default answer is right often enough to be dangerous. Industry insights rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it. ## What the data actually shows The interesting constraint is almost never the one in the brief. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. Most of the difficulty lives at the boundaries, not in the middle. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests. > The bottleneck is never where you think it is — that is what makes it a bottleneck. — Overheard in a retrospective ## How we got here The expensive mistakes here are rarely the technical ones. 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. It helps to separate the decision from the execution. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. ## A more modest claim The compounding effects matter far more than the individual wins. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. This is easier to write than to hold to when a deadline appears. What looks like a process problem is frequently an ownership problem. The first quarter shows the intended effect; the second shows what the intended effect displaced. When we mapped it out, four of the seven steps existed only to compensate for the second one. ## Where this leaves us Speed and reversibility are the trade-off worth naming out loud. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. That said, none of this generalises cleanly across team sizes. Feedback loops shorter than the planning cycle change everything. 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 clearest signal was that people stopped asking where things were. What we look for now: - Decide in advance what would make you stop - Keep the feedback loop shorter than the planning cycle - Prefer the reversible option when the evidence is thin ## What would change our mind 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. There are organisations where the opposite is true, and they are not obviously worse off. Scope is the variable everyone adjusts last and should adjust first. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The evidence here is thinner than anyone quoting it tends to admit. The tooling question is downstream of the constraint question. 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. ## The objection worth taking seriously Documentation is a symptom: you write it where the design is unclear. 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. It helps to separate the decision from the execution. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison. 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 clearest signal was that people stopped asking where things were. ## The incentive problem 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. It is worth saying that we have not run this long enough to be confident. What looks like a process problem is frequently an ownership problem. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. The tooling question is downstream of the constraint question. Industry insights rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison. ## A different reading A shared definition of "done" removes more friction than any tool. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it. Consistency is worth more than any individual improvement to Industry insights. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. 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 caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem. ## The received wisdom 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. The default answer is right often enough to be dangerous. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. In practice the answer showed up in the calendar before it showed up in the dashboard. If there is one thing worth carrying away, it is that the expensive mistakes in Industry insights are almost never technical ones.