Adhocracy

Bureaucracy answers every question with a procedure. Adhocracy answers it with a team, assembled for the problem and dissolved when the problem is gone.

The term was popularised by Alvin Toffler in the 1970s and given management form by writers like Robert Waterman, who defined it as any organisation that cuts across normal bureaucratic lines to capture opportunities and get results. Henry Mintzberg placed it in his taxonomy of organisational structures, describing adhocracy as the structure of choice where work is innovative, non-routine and too complex for standardisation.

He distinguished two flavours: the operating adhocracy innovates directly for its clients, like an advertising agency, while the administrative adhocracy innovates for itself, like an aerospace project organisation. The anatomy is distinctive, with authority flowing to whoever has the relevant expertise, teams forming around projects, and coordination happening through mutual adjustment rather than rules or plans.

That design shines where the environment moves fast. Technology firms, creative agencies, research groups and startups use adhocratic forms because the cost of a slow, committee-bound decision is a missed market.

Adhocracies prize specialists who tolerate ambiguity, because job descriptions go stale within months and status comes from contribution rather than title, and leadership changes job rather than disappearing: leaders set direction, connect teams and remove obstacles, since commanding from a chart is no longer an option. The weaknesses are just as real.

Without hierarchy, work gets duplicated, roles blur, half-finished initiatives pile up, and conflicts have no referee. Culture carries the load that rules would otherwise bear, so shared purpose, trust and tolerance for ambiguity are what stop flexibility from sliding into chaos.

Scale is the natural enemy. A thirty-person company can run on mutual adjustment; a thirty-thousand-person company usually cannot, which is why mature firms graft adhocratic units onto a bureaucratic core.

That hybrid even has a name, bureau-adhocracy, where routine operations follow procedures while project teams roam free. For a manager, the practical question is not whether adhocracy is superior but which parts of the business genuinely face novel problems, because those are the only parts that benefit from dissolving the structure.

Routine work organised adhocratically is just disorganisation with a fashionable name. The test of maturity is what happens when a project fails: healthy adhocracies dissolve the team and move the lesson, unhealthy ones hunt for someone to blame, and the idea's staying power comes from naming something real, the difference between work that can be specified in advance and work that cannot.