The floating architect

Working notes. The full essay is in progress; this is the argument in outline.

The claim

Most product organizations assign one person per swimlane and lose the system in the seams. The most valuable seat I have held is the one that floats: close enough to engineering to be trusted with the roadmap, close enough to product to shape the brief, close enough to design to keep the craft honest.

What the role actually looks like

• At Meta my title was Design Architect, Family of Apps. The job was coherence: a V2 design system pushed to 80% adoption, 1.73 million lines of code removed.
• At Bullish the same instinct looked like an Innovation Lab: gated testing that let Voice and Bullish leave the lab as real launches.
• At Inworld AI it meant owning design across three pillars I stood up: Product Design, UX Research, and Design Systems.

Why it works

• Systems fail at interfaces, and org charts are interfaces.
• A floating architect pays down coordination cost before it becomes headcount.
• The trade: you give up a clean lane for leverage across all of them.

Where this is going

The essay will close with a practical section: how to tell whether your org needs an architect, and how to carve the role without creating a bottleneck.