Fragmentation is not a design problem
Any organisation that has grown across borders for long enough eventually finds that it is several brands wearing the same name. The logo has variants nobody authorised. Packs in one region follow a hierarchy that would be unrecognisable in another. The same product carries three names in four markets. Websites have been built by different partners on different platforms in different decades. Marketplace listings, which no one entirely controls, contain photography and claims from every era simultaneously.
The instinct is to treat this as a design failure and to correct it with a document — a stricter set of guidelines, more firmly enforced. That instinct misreads what happened. Almost every deviation was, at the time it was made, a reasonable local decision taken by someone with a deadline, a regulator, a retailer requirement or a genuine cultural constraint. Fragmentation is not indiscipline. It is the accumulated residue of a company that was growing faster than it was governing, and the deposits are load-bearing.
This distinction matters because it determines who has to be in the room. A design failure is fixed by designers. An accumulation of local decisions is unwound only by re-deciding who has the authority to make them — which is a governance question, and governance questions are not resolved by a manual.
The four costs that never appear in the business case
The first is archaeology. Before anything can be unified it has to be found, and in most global organisations nobody knows the true count of live packs, live pages, live languages, live marketplace listings or live third-party assets carrying the brand. The inventory itself is a substantial piece of work, and it is invariably larger than the estimate given before it started. Programmes that skip it discover the missing material later, at a worse moment.
The second is adjudication. Every deviation found has to be judged: is this a violation to be corrected, or an adaptation with a real reason behind it — a regulatory requirement, a script that does not support the typeface, a retailer's mandated format, a colour with a specific local meaning? This is slow, unglamorous work requiring both design judgement and market knowledge, and it cannot be delegated to either alone. Under-investing here produces a system that markets are entitled to ignore, because it will visibly be wrong somewhere.
The third is migration, which is the only cost most business cases contain. Re-issuing artwork, re-shooting, re-platforming, re-writing and re-translating content across every language and every channel is mechanical, expensive and unavoidable. It is also the most predictable of the four, which is precisely why it dominates plans that should be dominated by something else.
The fourth is political, and it is the one that ends programmes. A market leader who has built a business with a degree of local autonomy is being asked to surrender part of that autonomy in exchange for a promise about a future benefit that will mostly accrue centrally. Unless the exchange is made explicit and something real is offered in return — speed, cost relief, better assets, faster approvals — the rational local response is passive compliance followed by quiet reversion. Two years later, the fragmentation is back and the organisation concludes that unification does not work.
Why the savings argument is the weakest one available
Unification does reduce duplicated production. One photography library rather than nine. One template set rather than a project per market. One content model rather than a rebuild each time a site ages out. These savings are genuine and they recur.
They are also a poor foundation for the decision, for two reasons. They are second-order — a reduction in the cost of doing something, not an increase in what the something is worth. And they are measured against a declining base, because much of the duplicated work would have been consolidated eventually by platform change anyway. An argument built on savings invites the finance function to approve the cheapest version of the programme, which is reliably the version that does not change anything.
Where the return actually is
The first return is compounding recognisability. Consumers cross borders far more than brand governance assumes — through travel, migration, diaspora households, cross-border marketplaces and social platforms that have no notion of a market boundary. Every market that presents the brand consistently makes every other market's spend work slightly harder. Fragmentation means each market is paying to build recognition that stops at its own border.
The second is launch speed. In a fragmented organisation, entering a new market is a project: identity decisions re-litigated, assets rebuilt, a site commissioned, content produced from nothing. In a unified one it is a configuration: an existing system instantiated with local variables. The difference is measured in quarters, and quarters are where category positions are taken.
The third is negotiating position. Retailers, marketplaces and platform partners assess a brand partly on how much work it will be. A supplier arriving with a complete, correct, ready-to-ingest asset system is a materially easier partner than one whose material has to be chased, corrected and reformatted — and ease is a currency in a negotiation about placement.
The fourth is legibility to capital. Investors, acquirers and boards can only underwrite what they can see as a single asset. A portfolio that presents as one coherent brand across markets is understood as one thing with global reach. The same portfolio fragmented is understood, correctly, as a collection of local positions — which is a different and less valuable proposition.
A system, not a standard
The unification programmes that hold share one characteristic: they deliver a system rather than a standard. A standard tells a market what it may not do. A system gives a market the fastest available route to doing the right thing — production-ready assets, templates that already handle their script and format, a content model their platform can consume, and clear answers to the questions that actually arise on a Friday afternoon.
The organising discipline is deciding, explicitly, what is fixed, what may flex within defined limits, and what is genuinely free. Fixed elements are the small set that carry recognition across borders and are never negotiable. Flex covers the adaptations that have real reasons — script, format, regulatory display, seasonal and cultural expression — bounded so they remain recognisably the same brand. Free is everything that does not affect recognition and therefore should not consume anyone's time. Most guidelines fail by making everything fixed in language and nothing fixed in practice.
Sequence, and the governance question underneath it
Sequencing follows one rule: unify first what a consumer can encounter in more than one market. That generally means the identity core, then nomenclature and brand architecture — because a product called different things in different markets cannot be unified by design work at all — then the packaging system, then digital templates and the content model, then the long tail of collateral that nobody misses.
Underneath the sequence sits the question the programme is really about. Who decides? A unification effort without a named owner holding authority over both the system and the exceptions is a design exercise that will be admired and then ignored. With that authority, and with a genuine exception process that markets can use rather than circumvent, the same work becomes durable — because it survives the first Friday afternoon when a market needs something the system did not anticipate.
That is the honest description of the discipline: unification is a governance change delivered in the form of a design change. Organisations that understand this before they start spend more time at the beginning and far less at the end.
