Product and brand are the same decision
We're yet to be convinced they're separate disciplines. A note on why.
Somewhere in most engagements, someone asks whether this week is a product week or a brand week. It's a fair question. We've just never found a way to answer it.
The industry treats them as two trades. An agency does the brand: the name, the story, the campaign. A product team does the product: the roadmap, the build, the backlog. Between them sits a handoff, and in the handoff the promise quietly changes hands.
But nobody experiences a company as two disciplines. Your users experience one thing.
The promise and the keeping
A brand is a promise. A product is that promise kept, or broken, several times a day. The campaign sets an expectation; the onboarding either survives it or it doesn't. The pricing page is brand copy. The error message is brand copy. The empty state your users meet on day one says more about what you stand for than the manifesto ever will.
When the promise and the keeping are run by different people with different targets, the seams show. Marketing promises effortless; the product ships forty toggles. Nobody lied. The org chart did.
One decision, two altitudes
So we work on both, deliberately, in the same head. Not because specialists are wrong, but because underneath it's the same decision at different altitudes: who is this for, what do they get, and why should they believe you. Answer that once, properly, and the roadmap and the brand book stop arguing.
A test we like: if you changed your logo tomorrow, would churn move? If you changed your onboarding, would it? That's where your brand actually lives. Look after that one first.