( Product )
When brand meets product
A brand that only lives in the campaign will feel borrowed the moment it meets a button, a setting, or an empty state. The product is where the identity has to keep working.
The campaign is not the product
Brand work often ends on a beautiful still: a poster, a film, an object shot in perfect light. Then the product team opens the file and has to fit that feeling into a form, a nav, and an error.
That meeting is where identities usually thin out.
If the brand only performs when it is looked at, it will not survive being used. A product is a place people return to on a Tuesday, in a hurry, with the logo very small.
Two teams, one surface
Brand and product fail each other when they trade files instead of decisions. The brand team hands over a PDF. The product team invents a button style that "feels close". Neither side can point to the rule that was broken.
We put both in the same review. The question is not whether the screen looks like the campaign. It is whether a person can tell it is the same company without being told.
Make the brand usable
Color, type, and voice have to work at product scale. A display face that sings on a poster may fail in a label. A campaign red may fail as an error. We test the system on the smallest type and the dullest screen, not only on the hero.
Voice matters here too. Empty states, confirmations, and the words on a button are brand surfaces. If they sound like a different company, the visual system cannot save them.
We would rather ship a quieter interface that is unmistakably theirs than a screen that quotes the campaign and then falls back to a default component.
Recognition without a billboard
The test is a screen with the logo removed. If the type, the space, and the tone still belong to the brand, the two worlds have actually met.
Brand meets product when using the thing feels like the same idea as seeing the campaign, just closer.
Leave a Reply