Big government: The bigger a group or system becomes, the more stupid it acts

                BIG GOVERNMENT

The bigger a group or system becomes, the more stupid it starts acting.

Many “laws” and heuristics point the same way—scale breeds coordination friction, goal drift, and perverse incentives. Closest relatives:

Systemantics (John Gall)

• Gall’s Law: Complex systems that work evolve from simple systems that worked; big systems usually don’t.
• Large‑system effect: As systems grow, side effects, failure modes, and unintended consequences multiply faster than benefits.
• Goal displacement: Systems tend to oppose their own stated purpose once routines and status needs take over.

Augustine’s Laws (Norman R. Augustine)

• The “last 10%” law: The last slice of capability produces a disproportionate share of cost and problems—complexity rises faster than performance.
• More generally: Organizational complexity and bureaucracy scale up faster than insight and control.

Murphy’s Laws

• Anything that can go wrong will—especially when you add interfaces, handoffs, and moving parts.
• If there’s a wrong way to do it, someone will; with more someones, they will, sooner.

Other closely related laws and effects

• Brooks’s Law: Adding people to a late project makes it later (communication paths scale roughly with n²).
• Ringelmann effect (social loafing): Individual effort drops as group size rises.
• Parkinson’s Law (+ bikeshedding/law of triviality): Work (and agenda) expands to consume resources; groups fixate on the trivial when big issues are hard.
• Pournelle’s Iron Law of Bureaucracy: Those serving the bureaucracy outcompete those serving the mission as organizations grow.
• Goodhart’s Law (and Campbell’s Law): When a measure becomes a target, it ceases to be a good measure; larger orgs get better at gaming metrics.
• Conway’s Law: System designs mirror the organization’s communication structure; bloated comms yield bloated designs.
• Ashby’s Law of Requisite Variety: Control must match system variety; growth without matching governance looks “stupid.”
• Dunbar’s number: Beyond certain sizes, cohesion and trust degrade; coordination quality falls.
• Bystander effect: Responsibility diffuses in larger groups; inaction and safe conformity rise.
• Amdahl’s Law: Diminishing returns from parallelization; coordination overhead caps speedup.
• Shirky Principle: Institutions tend to preserve the problems for which they are the solution.

Summary (channeling Murphy, Gall, and Augustine): As headcount and interfaces rise, noise scales faster than signal, incentives drift, and the cost of being wrong outpaces the benefit of being right.

In addition:

Below is a field guide for “big government” through the lenses of Systemantics (Gall), Murphy’s Laws, and Augustine’s Laws. Translation: expect complexity to misbehave, assume what can fail will, and remember that costs/complications scale faster than capability.

1. Coordination drag and n² interfaces

• Failure pattern: Interagency initiatives stall; disaster responses and cross-cutting programs create endless handoffs and conflicting SOPs.
• Laws: Brooks’s Law (more people → later project), Conway’s Law (design mirrors comms sprawl), Systemantics’ large‑system effect.
• Countermeasures:
  • Limit team size: Stand up small joint “mission cells” (6–10 people) with authority and budget.
  • Reduce interfaces: Name one lead agency; others support via pre‑negotiated MOUs and an incident command model.
  • Single‑threaded ownership: One accountable official (and clear delegate) with decision rights; publish a RACI and escalation ladder.

2. Metric gaming and goal drift

• Failure pattern: Agencies hit targets (case closures, inspections, response time) while outcomes stagnate or get worse.
• Laws: Goodhart’s/ Campbell’s Laws; Systemantics’ goal displacement.
• Countermeasures:
  • De‑target gamed metrics: Pair outputs with outcome and harm metrics; rotate a subset quarterly.
  • Ground truth loops: Embed field audits, citizen feedback, and random “mystery shopper” checks.
  • Budgeting: Tie a portion of funding to longitudinal outcomes, not quarterly dashboards.

3. Bureaucratic accretion and review creep

• Failure pattern: More layers, forms, and sign‑offs than work; decisions die of a thousand approvals.
• Laws: Parkinson’s Law; Pournelle’s Iron Law; Murphy’s corollary that anything requiring many approvals will miss the window.
• Countermeasures:
  • Structural diet: Cap span-of-control; 2‑in‑1‑out rule for reviews/committees; zero‑base org charts every 2–3 years.
  • Sunsets: Time‑limit task forces and temporary offices unless explicitly re‑chartered.
  • Decision hygiene: Pre‑reads, consent agendas, and “two-way vs one-way door” triage to fast‑track reversible calls.

4. Big‑bang programs that never arrive

• Failure pattern: Monolithic IT or policy rollouts collapse under their own weight.
• Laws: Gall’s Law (working complexity evolves from working simplicity); Augustine’s “last 10%” costs explode.
• Countermeasures:
  • Evolve from a small working core: Pilot in one region or cohort; ship minimum viable services within 90 days.
  • Stage‑gated funding: Release money by milestone with kill criteria; no “too big to stop.”
  • Modular architecture: Open standards, small contracts, replaceable components.

5. Diffuse accountability (“not my remit”)

• Failure pattern: Many agencies touch a problem; no one owns the bad outcome.
• Laws: Bystander effect; Systemantics’ “systems oppose their stated purpose.”
• Countermeasures:
  • Single‑point accountability in statute or executive order; name and publish the “owner of last resort.”
  • Always‑on duty officer model with 24/7 escalation tree.
  • Quarterly public “owner’s report” on outcomes and blockers.

6. Regulatory complexity outruns control capacity

• Failure pattern: Rulebooks balloon; enforcement capacity and public comprehension lag.
• Laws: Ashby’s Law of Requisite Variety; Augustine on rising complexity costs; Murphy on compounded edge cases.
• Countermeasures:
  • Outcome‑based rules and safe harbors; fewer prescriptive boxes to check.
  • Sandboxes and time‑boxed waivers to learn before scaling.
  • Shared services/regtech: common data standards, e‑filing, automated validation to amplify scarce inspectors.

7. Procurement bloat and gold‑plating

• Failure pattern: Years to buy anything; over‑spec’d requirements that few can meet; vendor lock‑in.
• Laws: Augustine’s cost curves; Murphy’s “more parts, more failure points.”
• Countermeasures:
  • Modular contracting and bake‑offs; short, competitive sprints before scale.
  • Use fixed‑price for mature tech; cost‑plus only for true R&D with stage gates.
  • Independent red‑team on requirements; ban “nice‑to‑haves” from MVP phases.

8. Social loafing and mission dilution

• Failure pattern: Individual contribution and urgency fade in very large teams.
• Laws: Ringelmann effect; Systemantics routinization.
• Countermeasures:
  • End‑to‑end mission teams with clear, citizen‑visible deliverables.
  • Recognition and promotion for shipped outcomes, not meeting attendance.
  • Rotation programs to refresh context and avoid local maxima.

9. Bikeshedding and agenda capture

• Failure pattern: Endless debate on trivial items; hard choices deferred.
• Laws: Parkinson’s Law of Triviality; Murphy’s “critical path is what’s least discussed.”
• Countermeasures:
  • Timebox discussions; quorum and decision deadlines.
  • Require a one‑page decision memo with options, risks, and a default “do nothing” baseline.
  • Reserve senior time for the top 2 irreversible issues per week.

10. Data silos and privacy paralysis

• Failure pattern: Agencies can’t share the right data fast enough; either overshare or undershare.
• Laws: Conway’s Law; Murphy on interface failures.
• Countermeasures:
  • Interoperability first: common identifiers, APIs, and canonical data contracts.
  • Privacy‑preserving linkages (minimization, role‑based access, differential privacy where appropriate).
  • Data stewardship: name data owners; publish SLAs for data quality and access.

11. Crisis messaging whiplash

• Failure pattern: Inconsistent public guidance during emergencies.
• Laws: Systemantics on side effects; Murphy on ambiguity breeding failure.
• Countermeasures:
  • Pre‑approved message templates, thresholds, and a single public voice.
  • Daily incident rhythm: situation report, decisions, blockers, next actions.
  • Red‑team communications for clarity and unintended readings.

Implementation playbook (operationalizing the countermeasures)

• Design for smallness at scale: Organize into many small teams with narrow mandates; connect them via simple, standard interfaces.
• Default to reversible bets: Make choices you can roll back quickly; save heavyweight process for irreversible moves.
• Short loops, visible outcomes: 2–4 week delivery cycles with citizen‑facing milestones; publish burn‑up/outcome graphs.
• Pre‑mortems and chaos drills: Assume failure, practice it, and build graceful degradation and manual fallbacks.
• Kill criteria and sunsets: Write the exit plan on day one; no perpetual pilots.
• Platform the boring stuff: Identity, payments, notifications, document upload, and case management as shared services to reduce duplication.
• Governance rhythm: Weekly ops review (are we shipping?), monthly outcomes review (are citizens better off?), quarterly architecture review (are interfaces getting simpler?).