Missing shared hierarchy rules are why global emphasis spreads

What it is

Ask who can refuse a new badge and the answer is “each team owns its feature,” or “no one.” Badges, colour strips and motion then have no shared cap, and spread is only a matter of time. What is missing is not another style manual. It is governance: who assigns the first slot, and who cuts when the cap is hit. A component library can still spread: every emphasis device in it is legal; what is absent is the right to say “this screen may use them this many times.” If “rules” in the title is read as hex values and radii, people will write a thicker style document, while ownership stays empty.

Why it happens

Without a shared budget, the marginal cost of emphasis to the requester is zero: it spends no quota beyond their own hours, and it spends the page’s contrast. A rational requester keeps asking until the glass cannot physically take more. A library speeds this up: devices are ready, integration is cheap. Governance has to make contrast costly again — for example “home may have one strongest rung and two next rungs at once,” plus a cross-team role allowed to refuse a third. Without that role, even a careful document is advice, and advice is routed around under metric pressure. Spread is rooted in missing adjudication, not in designers who “don’t know restraint.”

Where it stops holding

A single team that already refuses surplus emphasis in review has informal governance; it need not incorporate first. Governance that is too tight will block a real incident bar, so system status sits outside the budget, and feature requests may not impersonate it. Multi-brand, multi-country pages may each need their own first-slot rule; align by page type rather than one global number. What must not be missing is “does this class of page have an adjudicator,” not “one number for the company.”

Applying it

• Name an adjudicator for one page type (a design lead, or the product owner of that page). Refusing an emphasis does not require the requesting team’s consent.
• Write budget numbers for that type: how many strongest rungs, how many next. The numbers enter the review checklist, not a long manual.
• Badges and strips in the library default to “need adjudication to appear on a shared page,” not “anyone may drag them in.”
• Check: walk a fictional “we must add a badge” mail through the current process and see whether a role can say no without talking colour or radius. If no one can be named, governance does not exist. Name someone and run two real requests: one approved as a swap (new in, old out), one refused as a third strongest rung. If the requesting team can still route around via escalation, adjudication is not in force. Do not lengthen a style document as a substitute.

Related

• Same group: F3.11.1 Teams each grabbing emphasis for their feature accumulate into global emphasis · F3.11.3 Repairing global emphasis means re-ranking, not stacking new cues
• Nearby: F5.11.3 The number of accent points on a screen needs a budget · F3.07.3 Conflicting priorities need a content tradeoff
• Search terms: governance · emphasis budget · visual hierarchy · ownership