Prototypes instead of specs

I scaled the content component library, which the Opendoor content design team had built over about a decade before I got there, and used it as the source for prototypes I built myself. States, errors, empty states, the lot, assembled into something you could click rather than something you had to imagine.

That cut development cycles and cut the engineering time a prototype needed before anyone could react to it. It also killed an entire category of meeting, the one where four people argue about what a screen will feel like when nobody has seen it yet. Hard to argue with a thing that runs.

Cash Plus was a new category on the buy side of home transactions, expanding nationally through Agent Led Offers. New category means no shared vocabulary: not with agents, not with sellers, not internally, not in the product.

I owned the language and the lexicon for that expansion. What the thing is called, what it promises, what it explicitly does not, and how the same idea keeps its meaning from an agent conversation through to a screen. The national expansion shipped with Cash Plus conversion up 1.4 percentage points.

One person cannot review an organization’s content. You can try, and it works right up until the first day you’re unavailable. Nobody stays available forever, and a system that assumes otherwise is already broken.

So I instantiated the content design library inside the AI tools the company already used. The patterns, the lexicon, the voice, the error and empty-state rules, sitting where generation happens rather than in a document somebody has to remember to open. Product teams got their work off the ground without waiting on me, and what came out was closer to right on the first pass.

That is the whole idea I have been chasing since. Guidance nobody reads is decoration. Guidance loaded into the thing that does the writing is a system.