Bureaucratic Capture

When the administrative apparatus of an organization becomes the de facto decision-maker, supplanting the people nominally in charge. Unlike regulatory capture (where industry captures regulators), bureaucratic capture is internal: the compliance department, legal team, HR, or process managers accumulate veto power over operational decisions until the tail wags the dog. The pattern: (1) a legitimate support function is created, (2) it develops rules and approval gates, (3) it gains veto power, (4) operational teams route all decisions through it, (5) the support function effectively controls strategy without accountability for outcomes. Symptoms include: product decisions made by legal, hiring timelines set by HR process rather than business need, and innovation killed by compliance review. The Pentagon's acquisition process—where a weapons system takes 15+ years from concept to deployment—is bureaucratic capture at industrial scale.

When to use it

When decisions take longer despite no increase in complexity. When support functions grow faster than operational functions. When the answer to 'why can't we do this?' is always a support function's policy. During organizational restructuring.

How it can help

Helps leaders identify when support functions have shifted from enabling to controlling. The diagnostic: map every approval gate in your key processes and identify who has veto power versus advisory input. If support functions can block but aren't accountable for the business outcome of blocking, you have capture. Prevention requires keeping support functions in advisory roles with escalation paths, setting time-bound approval windows (silence = approval), and ensuring that the people accountable for outcomes retain final decision authority. Regular 'process pruning' reviews where every gate must justify its existence against actual risk prevented.