How product decisions become brand decisions at founding

The Document as Declaration

Stripe's API documentation does something unusual for a financial infrastructure company: it makes you feel like someone thought carefully about you before you arrived. The prose is plain, the examples are concrete, the structure assumes competence without assuming prior knowledge. Engineers have cited it for years — not in conversations about technical writing, but in conversations about brand. That slippage matters. When developer tooling starts appearing in brand discussions, something is being revealed about where brand actually lives.

The question is whether that was a discovery or a confirmation of something already understood.

James Hurst ran workshops for founding teams at Shack 15 in San Francisco built around a single working principle: the product interaction is where brand gets made. Not as a slogan, but as a structural argument. The onboarding, the error message, the empty state, the moment a user hits friction and the company decides how to respond — these are where brand lives. The campaign introduces. Only the experience of the thing itself can convince. If those two things are misaligned, the campaign writes a cheque the product can't cash.

Stripe's documentation decision, traceable to its earliest years, looks like a founding team that understood this instinctively. The documentation wasn't a support function bolted onto a real product. It was the product, or at least the first meaningful encounter with it. Making that encounter feel considered, even generous, was a brand argument before Stripe had the scale to make any other kind.

Airbnb's 2014 rebrand offers a different version of the same bet. The Bélo identity — designed with DesignStudio — got most of the public attention, partly because of the jokes, partly because a new logo is a legible event in a way that a strategic shift is not. But the more consequential move was the deliberate turn toward storytelling about hosts rather than inventory. The product interaction — the moment a guest read a host's description, looked at photographs taken in real light, exchanged a message with a person rather than a property manager — became the brand argument. Airbnb wasn't selling rooms. It was selling the evidence that a stranger had prepared for your arrival. The product was the proof.

What's interesting about both cases is that neither company was doing this in response to a brand problem. Stripe wasn't trying to recover lost ground. Airbnb wasn't correcting a perception gap. They were making founding-era decisions about what the product was for, and those decisions turned out to have brand consequences that compounded over time. The documentation became a signal of Stripe's values — precision, respect for the developer's time, belief that good writing is part of good engineering. The host story became a signal of Airbnb's values — that the platform existed to make human connection possible, not merely to aggregate listings.

James' second edition of Use Design To Design Change opens with cases where unpolished but purposeful launches — Amazon, Google, Extinction Rebellion — outperformed polished but purposeless ones. The argument isn't that polish is bad. It's that purpose is load-bearing in a way that polish isn't. A company can add finish later. It's much harder to retrofit meaning into a product that was built without it. The Shack 15 workshops were, in a sense, an attempt to have that conversation before the product was built — or at least before the brand strategy was written separately from the product strategy, which is where the trouble usually starts.

There's a version of brand strategy that treats the product as a vehicle for a separate message. You build the thing, then you figure out what story to tell about it. The campaign arrives to translate. This is how most large organisations still operate, and it produces a particular kind of brand: coherent on the surface, slightly hollow underneath, because the message and the experience were never required to agree with each other.

The Stripe and Airbnb decisions suggest a different model — one where the product decision is the brand decision, made at the same moment by the same people. The choice to write documentation that treats developers as intelligent adults is a values statement. The choice to surface host personality rather than listing count is a values statement. Neither required a brand brief. Both required a founding team that had already answered the question of what they were trying to make possible for the people who would use the thing.

The campaign introduces. Only the experience of the thing itself can convince.

What the Shack 15 workshops were testing, it seems, is whether that conviction can be transmitted early enough to matter — before a company's product and brand teams become separate departments with separate briefs and separate success metrics. The workshop format is interesting precisely because it catches founding teams at the moment when those separations haven't yet calcified.

Whether that intervention holds as companies scale is a genuinely open question. Both Stripe and Airbnb have grown enormously since the decisions described here, and large organisations develop their own gravitational pulls toward the separation of message and experience. It would be worth knowing — and James' workshops presumably generated some evidence on this — whether the founding-team conversation is a permanent inoculation or just a longer delay before the usual drift sets in.

Or whether the real question is what it takes to keep having that conversation, not just once at the beginning, but every time the product changes enough to require the brand argument to be remade from the inside out.