Addition is rewarded. Removal never wins the meeting.
Leaders who invested heavily in reducing customer friction went home and reproduced the same condition inside their own walls. Every tool, dashboard, priority, framework, and notification channel is another door in a corridor that employees walk every day. Each looks defensible when added. Together they impose a quiet tax on the one resource that cannot be replenished: the attention required to make a considered decision under real conditions.
The reason organisations keep accumulating is that the incentive system selects for it. Adding earns a reward; subtracting earns almost nothing. A new tool gets a launch. A new OKR gets a champion. Retiring something generates a small political cost, no visible win, and the quiet hostility of whoever introduced the thing being removed. The environment therefore compounds in the way a browser accumulates tabs — quietly, incrementally, and entirely by design of a reward system that has no mechanism for removal.
There is a second driver, and this one concerns altitude. Senior leaders see the portfolio. Teams see the corridor. The strategy deck shows ten priorities. The team hears: pick one and hope you guessed right. The stated strategy says focus. The revealed strategy, visible in calendars, tools, and rituals, says accretion, because accretion is what the incentive system actually pays for.
When I worked as a lecturer, I logged into a portal that gave access to roughly twenty pieces of software: lesson planning, marking, assessment data, safeguarding alerts, timetabling, registers. Each was competent in isolation. Each had its own model, its own pathways, its own ways of generating downstream work when something was entered incorrectly. Single sign-on solved the password problem and solved nothing else. Context switching was the default state, and by the time the accumulation had run its course, navigating the stack had become a second job layered on top of the teaching. The system had been built to support the work. In practice, it had quietly become the work.
Two things that experience made undeniable. Every tool arrives with a hidden invoice, paid in attention, that nobody budgeted for and nobody tracks. And the people closest to the work are the only ones who can see the full shape of the load — which means they are almost always the last to be consulted when the stack expands.
Choice overload inside an organisation is a design output. The designer is whoever controls what gets added and what never gets removed. Treating it as a discipline problem on the front line mislocates the lever entirely. Complexity that nobody owns becomes complexity that everybody pays for, and the people paying are the ones whose judgement the organisation most depends on.
Once named as a design problem, the leadership job shifts. The interesting question stops being what else the team should do, and becomes what the team is currently being asked to hold in its head at once, and whether that is a reasonable ask of finite human attention. Honest answers tend to retire things that someone senior announced with pride — which is why the question is rarely asked, and why the implication of asking it runs deeper than most operational reviews reach. A list of ten priorities is an instruction to pick one and ignore the rest. Ranking makes that choice visible, which is precisely why most organisations resist it. Defaults need an owner, because they carry more weight than guidance ever will. And the number of things on the list should be small enough that a tired person can recall them without effort, because tired people are the ones making the decisions that matter most.
Behavioural research has been making this argument about users for years — that poor decisions in over-optioned environments are more often a product of the environment than of the person inside it. Organisations rarely extend the same logic inward. A manager who cannot execute across ten priorities is called unfocused rather than over-optioned, which flatters the designer of the environment and punishes its occupant.
A manager who cannot remove is a manager who cannot lead, because the thing being led is attention, and attention is finite. The organisations that out-execute their peers will be the ones that treat addition as a cost and subtraction as a craft.