> ## Content Index > Fetch the complete content index at: https://arther.ghost.preview.themeanax.com/llms.txt > Use this file to discover other available public pages before exploring further. # Scaling a design system across a growing product team - URL: https://arther.ghost.preview.themeanax.com/scaling-a-design-system-across-a-growing-product-team/ - Published: 2026-09-24T11:38:02.000Z - Updated: 2026-09-24T11:38:32.000Z - Description: The interesting thing about design is how rarely the hard part is the part everyone prepares for. - Author: arther - Tags: #themeseed, Design, Notes Ask ten people to define design and you will get ten answers, most of them describing a symptom rather than the thing itself. ## The numbers 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. It is worth saying that we have not run this long enough to be confident. ![person writing on white paper](https://arther.ghost.preview.themeanax.com/content/images/2026/09/photo-1587440871875-191322ee64b0-1.jpg) Photo by UX Indonesia on Unsplash The interesting constraint is almost never the one in the brief. 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. Consider the failure mode rather than the success case. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer. ## How we knew it was working The expensive mistakes here are rarely the technical ones. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. 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. ## The situation 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. The evidence here is thinner than anyone quoting it tends to admit. Scope is the variable everyone adjusts last and should adjust first. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. That said, none of this generalises cleanly across team sizes. Consistency is worth more than any individual improvement to design. Design rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem. ## What we tried first Most of the difficulty lives at the boundaries, not in the middle. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. 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. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. Set a date at which you will stop, and write down in advance what would make you stop earlier. > The cost of a bad decision is rarely the decision. It is the six months of building on top of it. — Overheard in a retrospective ## What we would do differently The first thing to establish is what you are actually optimising for. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. A useful test: if this disappeared tomorrow, how long before anyone noticed? There is a version of design that is mostly ritual. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. Documentation is a symptom: you write it where the design is unclear. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The version of this that works fits on an index card. The version that fails needs an onboarding session. The checklist we ended up with: - Agree on what "done" means, in writing, before starting - Decide in advance what would make you stop - Write the constraint down before choosing a tool - Prefer the reversible option when the evidence is thin ## The part that surprised us A shared definition of "done" removes more friction than any tool. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. In practice the answer showed up in the calendar before it showed up in the dashboard. The tooling question is downstream of the constraint question. The first quarter shows the intended effect; the second shows what the intended effect displaced. What looks like a process problem is frequently an ownership problem. 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. ## What changed Nobody gets credit for the work that did not need doing. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not. 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. ## What it cost 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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests. 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. What looks like a process problem is frequently an ownership problem. 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. ## Where it still breaks The first thing to establish is what you are actually optimising for. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. Documentation is a symptom: you write it where the design is unclear. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. 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. ## The numbers Scope is the variable everyone adjusts last and should adjust first. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison. We will revisit this once we have another two quarters of data. The current answer feels right, which is exactly when it is worth checking.