The Mandate Problem: Why Brand Roles Fail

When a brand leadership role fails inside a year or two — and a meaningful share of them do — the retrospective usually focuses on the person: wrong fit, wrong experience, wrong personality for the culture. Far more often, the actual cause sits one level up, in how the role was scoped before anyone was hired into it. A role asked to govern brand strategy across a complex organization, and in the same breath asked to select merchandise or approve routine creative requests, doesn’t have a mandate.

It has a job description assembled from whatever needed a home, and no amount of individual talent fixes a role built that way.

What a mandate actually requires

A functioning brand leadership role needs three things to succeed, and none of them is primarily about the person’s skill: the authority to make a decision and have it actually hold across the parts of the organization it affects, a scope narrow enough that the role’s time is spent on decisions that require that authority rather than on tasks anyone could do, and visible backing from leadership so that the role’s decisions aren’t quietly reversible by whoever complains loudest. A brilliant hire without these three structural conditions inherits an impossible job; a merely competent hire with all three tends to succeed, because the structure is doing most of the actual work.

The specific failure pattern: strategic authority bundled with operational debris

The clearest version of this mistake shows up in how roles get written before they’re ever posted. A job description asks for someone to develop and enforce brand governance across multiple countries and business units, build management presentations, and steer international campaigns — and then, in the same list of responsibilities, adds selecting the merchandise assortment or approving routine regional creative requests. These aren’t equivalent kinds of work. One requires the standing to say no to a regional general manager.

The other is an operational task that happens to touch the brand. Bundling them into one role doesn’t create efficiency — it creates a person who spends their governance-level authority on merchandise decisions and has no time left, structurally, for the harder work the role was actually meant to do.

Why this bundling happens so consistently

It’s rarely a deliberate choice. Roles get built by accumulating whatever brand-adjacent work doesn’t have an obvious owner elsewhere in the organization, and a new brand leadership hire looks like a convenient place to route it all. The accumulated list reads as thorough on a job posting — broad scope can look like an important role — but broad scope assembled this way usually means the strategic core of the job is competing for the same hours as its most tedious operational tail, and the tail, having concrete deadlines, tends to win.

What good candidates notice, even if they can’t always name it

Experienced brand leaders tend to sense this mismatch during the hiring process, even when they can’t immediately articulate why a role feels off. A posting that asks for governance authority across a complex organization while also listing operational tasks several levels below that authority signals, correctly, that the organization hasn’t yet decided what it actually wants from the role — and the strongest candidates, who have often lived through exactly this failure pattern before, read that signal and self-select out, leaving the role to be filled by whoever didn’t notice or didn’t have better options.

What a well-scoped mandate looks like instead

The fix isn’t more seniority or a bigger budget attached to the same bundled scope — it’s separating the two kinds of work at the design stage, before a role is posted. Strategic governance — deciding the position, defending it, holding the line across business units and geographies — deserves a role built entirely around that authority, with operational and creative-execution tasks routed elsewhere, to people whose job is explicitly to execute rather than to govern. A role given this narrower, clearer mandate can actually succeed at the thing it exists for, rather than spending its authority on decisions that never needed a governance-level person to make them in the first place.

Source Code B supplies strategic rules; it does not automatically staff or permanently run the company’s internal brand function. The company must decide which choices a role may make, where its authority holds, and which tasks explicitly sit elsewhere. That question follows the prior decision about whether a dedicated governance function is needed at all. In an international organisation, the mandate must also fit the decision structure across countries and business units.

Continue with related topics

• When a Brand Needs a Governance Function — And When It Doesn’t
• Brand Architecture Is Capital Allocation, Not Design
• A Rulebook That Holds Across Countries and Business Units

FAQ

Does this mean brand leadership roles should never include any operational responsibility? Not necessarily — some operational visibility can help a governance role stay grounded in reality. The distinction is whether the operational tasks are proportionate and clearly secondary, or whether they compete directly for the time and attention that the governance mandate requires. A small amount of operational awareness is different from operational tasks structurally crowding out strategic ones.

How can an organization tell if it’s building this mistake into a role before posting it? A useful test: list every responsibility in the draft job description and ask, for each one, whether it requires the authority to override a regional or departmental decision, or whether it’s a task someone without that authority could also do. If the list mixes both kinds significantly, the role as written is likely to reproduce this failure regardless of who’s hired into it.

Is this failure pattern specific to large, multi-entity organizations? It’s more visible there because the governance and operational sides of the role are more clearly distinct at scale, but the same mismatch can happen in smaller organizations too — any brand role asked to both hold a strategic line and personally execute routine tasks below that line is vulnerable to the same structural problem, just at a smaller scale.

---