Teams each grabbing emphasis for their feature accumulate into global emphasis

What it is

Growth wants a badge, marketing a top campaign, operations a red dot, legal a yellow disclaimer, support a second brand-coloured “contact us.” Each request is reasonable in isolation: that team’s metric really does run on being seen. On the same home, a year later, the first screen has four colour strips, three badges, two motions. Global emphasis is the sum of departmental decisions, not one author bolding every line on a layout. Single-author inflation happens in one typesetting pass. This ledger crosses quarters and teams; each entry made the page “only a little louder.”

Why it happens

Attention is a commons; the right to emphasise is private inside the organisation. Each team optimises exposure for its own feature and does not pay for a drained pool. Every review asks only whether the new block is “visible enough,” never how much contrast remains after it enters. Locally rational moves saturate the page. Unlike one person turning every knob to the stop, there may be no one who over-turned anything; everyone turned a little. The visible form of accumulation is more kinds of device (badge + strip + motion + a second primary colour), not one author using one device on every block. To see it, count along a timeline who added emphasis in which month, rather than judging the taste of the current frame.

Where it stops holding

A new-feature coach with an automatic removal date is not accumulation. “Temporary” without a date stays. Platform-level system status (a site-wide outage bar) may interrupt and does not share the product-feature budget — but product features may not impersonate system status. A product with one or two authors almost never reaches this organisational mechanism; a loud screen there is more likely single-screen inflation.

Applying it

• Keep an emphasis ledger on shared pages (home, workbench): date, requesting team, device, promised removal. Without a ledger you cannot prove that “it wasn’t my extra strip” still sums.
• A new request may only answer “which existing emphasis leaves when we enter,” not only “how do we make our block more visible.”
• A quarterly review is not “how many new features.” It is whether the count of still-present ledger rows is monotonically rising.
• Check: from version history or design files, list badges, colour strips, motions and extra primary buttons added to that page in the last two quarters, coloured by team. Three or more from different teams with no removal is accumulation. Take the ledger to a meeting, cut or demote half on the spot, ship a subtract-only version, and compare first-look concentration. If concentration does not rise, you cut the wrong objects — do not restore them and invent another device.

Related

• Same group: F3.11.2 Missing shared hierarchy rules are why global emphasis spreads · F3.11.3 Repairing global emphasis means re-ranking, not stacking new cues · F3.11.4 A globally emphasised UI makes users immune to all emphasis
• Nearby: F3.08.1 Emphasising everything emphasises nothing · F5.11.1 Accent colour works because it is used rarely
• Search terms: emphasis accumulation · attention commons · badge · banner