What is Brand?

Ask most organizations to define their brand, and the answer tends to circle back to the same set of things: the logo, the color palette, the tone of voice in a campaign brief. This isn't wrong, exactly, but it's incomplete. A brand is also a promise, made at scale, to people the company will mostly never meet. And a promise made at scale depends on things design was never meant to carry alone: how a customer's data is handled, whether that promise holds the same way in every market, and whether anyone can actually show what the promise is worth.

We've spent a lot of time at Good Bards thinking about why this gap exists, and I see three reasons it keeps showing up across organizations of every size.

Brand Impact to Revenue

The Design Reflex

Design gets to own the word "brand" almost by default. It's the part of the work that's visible — the part you can put in a deck, hand to a client, and get a reaction to. A rebrand with a new logo makes the trade press. A change to how customer data is isolated between sub-brands doesn't, unless something goes wrong first.

I don't think any single person decided design should own brand. It happened gradually, as budgets and org charts settled into place around the part of the work that was easiest to see and easiest to approve.

There's a related distinction I think gets underused: what a customer perceives about a brand today isn't the same as what they expect from it tomorrow. Perception is shaped by the past — every interaction that's already happened. Expectation is a bet the customer is making about what comes next, and it's considerably more expensive to repair once broken. Most brand strategy work is built to manage perception. Very little of it is built to manage expectation, even though expectation is closer to where the real risk sits.

The Outsourced Instinct

Here's where expectation actually gets tested: in the systems underneath the brand, not the campaign in front of it.

Companies that run multiple brands or client accounts on shared infrastructure are, by definition, making a promise about separation — that one brand's data, consent, and customer relationships stay distinct from another's. When that promise breaks, it isn't a design failure. It's usually a data-isolation failure, and increasingly, a regulatory one. Singapore's PDPA carries penalties up to S$1 million or 10% of local annual turnover. Malaysia's PDPA, following amendments that took full effect in 2025, now caps at RM1 million and requires mandatory breach notification. France, operating under the EU's GDPR, faces fines up to 4% of global annual turnover for serious violations.

What I notice, talking with marketing leaders across the region, is that very few organizations can tell you who actually owns this. Ask who's responsible for access controls, data governance, and regulatory posture, and the answer is often a shrug, a vendor's name, or a pointer toward IT that points right back. This kind of expertise gets treated as something to call in during a crisis rather than something to build in-house, the way most companies build in-house creative or in-house media buying. The cost of that choice is that the organization never really learns where it's exposed until an incident teaches it directly.

The Missing Attribution Line

The gap runs in the other direction too, and it's the one I think gets talked about the least.

NielsenIQ's CMO Outlook: Guide to 2026 found that 83% of CMOs remain confident in their brand's equity, even as they face tightening budgets and heightened scrutiny over ROI. That gap is worth sitting with: confidence without proof is close to the exact problem this piece is about. Performance marketing doesn't have this problem in the same way; the path from spend to click to conversion is comparatively easy to show. Brand's contribution is real, but it's measured in awareness, consideration, and sentiment, and those numbers rarely survive a hard conversation with the board.

So accountability tends to split along the line of what's easy to measure, not what's actually true. Growth owns the revenue number. Brand owns awareness, consideration, and sentiment scores — real signals, but ones a CFO can't tie to a dollar. And because brand rarely gets asked to prove its impact on revenue, it rarely gets held accountable for protecting it either — which brings the two problems back together. If owning brand doesn't come with owning what protects the promise and what proves its value, the role ends up being a title without a mandate attached to it.

It Scales Down, Not Just Up

One assumption I'd push back on: that this only matters once a company is large enough to have complex brand architecture worth protecting. I hear a version of this often from founders and marketing leads at smaller companies — the idea that data isolation and access controls are a problem for later, once things are bigger.

I think that has it backwards. A five-person team running three sub-brands off shared infrastructure carries essentially the same structural exposure as an enterprise fifty times its size. What changes with scale isn't the risk itself — it's how many people are around to catch a mistake before a customer does, and how much accumulated trust there is to spend recovering from it. Smaller organizations usually have less of both.

Where I'd start

If there's one practical thing to take from this, it's to ask two people in your organization a direct question this week. First, whoever owns brand: if a customer of one of your brands received a marketing email meant for a different brand you own, would your team find out before the customer did? Second, whoever owns the P&L: is the person accountable for brand spend the same person who'd be accountable for a data incident?

If either answer is uncertain, that's not a reason to panic — it's a starting point. It usually means the fix isn't a new campaign or a rebrand. It's putting one accountable line against both what protects the promise and what proves it's working. That's the part of this work I find most interesting, and it's a large part of why we built Good Bards the way we did.

FAQ

Who is accountable for a brand's impact on revenue? In most organizations, no single role clearly is. NielsenIQ's CMO Outlook: Guide to 2026 found that 83% of CMOs remain confident in their brand's equity even amid tightening budgets and heightened ROI scrutiny — confidence that isn't backed by a clear line to revenue. Without that link, brand's contribution gets measured in awareness, consideration, and sentiment, which rarely satisfy a board, so accountability defaults to growth teams instead.

Why don't brand teams typically own compliance or data risk? Because that expertise is usually treated as something to bring in during a crisis rather than build internally. It often sits with an outside agency, a platform vendor, or legal counsel, engaged when there's an incident and released once it's resolved. Brand teams tend to own visual identity and messaging, not the access controls or data isolation that actually protect the promise.

Is brand a design function or a data function? It genuinely depends on both, which is part of why the ownership question is unresolved. Design announces the brand promise. Whether that promise holds, particularly across multiple brands or jurisdictions sharing infrastructure, depends on data isolation and access controls, which usually sit outside a brand team's authority.

What's the difference between owning a brand and being accountable for it? Ownership is usually about the logo, guidelines, and tone of voice. Accountability means answering for outcomes: a compliance incident, or a revenue number that can't be explained. Most people with the first don't have the second, and closing that gap usually takes an organizational decision, not a design one.