The industry is consolidating product, design, and engineering under single technology leaders and calling it a culture of builders. The precondition nobody prices is the platform.
Right now the fashionable org chart consolidates product, design, and engineering under a single technology leader and announces a culture of builders. AI tools made it plausible, a few famous companies made it enviable, and boards like how it reads. PMs prototype and own evals. Designers and Applied AI data scientists ship. Everyone builds. Speed is the whole pitch, and I understand the appeal, because parts of it are already working near me.
In our own pilot, designers with repo access prototype directly against the design system and ship low-stakes fixes, color bugs, token mismatches, alignment breaks, straight to production without a handoff. That’s real leverage, and it’s the real version of the builder story: more hands, same product. The dishonest version skips a step, and the step is the platform.
Are we building components solid enough that when a PM builds something, it still looks and feels like our product, instead of Frankenstein and bolted on?
When only engineers built, code review was the immune system. When everyone builds, the design system is the immune system, and most component libraries were never staffed for that job. Tokens with gaps, primitives with drift, patterns that live in a senior designer’s head instead of the library. A person routes around those. A PM with a prototype tool does not. Whatever your platform tolerates, your product will now express, at volume.
So the sequencing question for leaders considering this shape: platform before permission. Fund the component foundation like it’s load-bearing, because it’s about to be. Give the design system a roadmap owner, not a side-of-desk champion. And audit weekly for drift on the surfaces where the new builders are working. Builder culture with a solid platform compounds. Builder culture without one produces a stitched-together product at a speed you’ve never achieved before.
The teachable part
Before you widen who builds, make the platform load-bearing: tokens, primitives, and guardrails strong enough that a PM’s prototype still feels like your product. Sequence platform before permission, assign the design system a real owner, and audit weekly for drift.