On July 28, 2026, an earthquake hit Kumamoto. Eight days later, on August 4, Japan’s cabinet designated it a catastrophic disaster with no regional limit (“hongeki”), designated it a “specified non-ordinary disaster” (which triggers things like driver’s license renewal grace periods and extended bankruptcy filing deadlines for affected residents), and approved over ¥24 billion in reserve-fund spending — all in a single meeting12.

Eight days, for an institution not exactly famous for speed. I found that timeline more interesting than the earthquake itself, because it forces a question: how does a bureaucracy move that fast?

The obvious answer — “in a crisis, red tape gets cut” — is wrong, or at least backwards. Nothing about that August 4 meeting involved improvising. Every hard question had already been answered, in advance, by people under no time pressure at all. What counts as a “catastrophic disaster.” What threshold of damage triggers “specified non-ordinary” status. Whether a reserve fund can be spent without a full Diet budget deliberation, and under what conditions. Those are genuinely difficult questions — they involve tradeoffs between speed and accountability, between central and local authority, between precedent and flexibility for the unknown next disaster. They just weren’t answered on August 4. They were answered years earlier, in ordinary legislative time, by people arguing over statute language with no fire to put out.

What the crisis-response team did in week one was check a real event against pre-written criteria and sign. That’s not the absence of deliberation. It’s deliberation that already happened, somewhere else, at a different time, and got banked for later.

The same shape, at a much smaller scale

I noticed this pattern first somewhere unrelated: in Japanese aviation. In February 2007, JAL wrote a one-sentence rule into its safety management policy — an error made without intent, recklessness, or negligence would not trigger internal discipline3. On paper, it looks like a small HR footnote. In practice, drafting it took real, contested institutional work: where exactly does an honest mistake end and negligence begin? Who decides, and how do you keep that decision from quietly drifting back toward blame the first time a mistake actually costs money? None of that got settled in the moment of any specific incident. It got settled once, off the clock, before any concrete error existed to argue about.

ANA’s safety framework does something structurally similar, built around trust and voluntary near-miss (“hiyari-hatto”) reporting rather than after-the-fact discipline4. And as of April 2026, a revision to Japan’s Medical Care Act enforcement regulations now requires every hospital, every inpatient clinic, and every midwifery facility to appoint a dedicated safety manager5 — extending the same instinct, that safety culture has to be structurally mandated rather than left to individual judgment in the moment, into a third industry.

None of these are about response speed at the crisis, the way the disaster designations are. They’re about something narrower: what happens to an employee’s incentives the instant after they make a mistake. But the mechanism is identical. A hard question — will this be punished? — gets answered once, generically, in advance, instead of being re-litigated by a stressed, exposed individual in the seconds after something goes wrong.

Naming the mechanism

I want to call this “load-bearing friction”: deliberation that is real, effortful, sometimes genuinely contested, and deliberately front-loaded — so that speed later isn’t purchased by skipping the hard thinking, but by relocating it to a moment when nobody is bleeding, no plane is on fire, and no political deadline is breathing down anyone’s neck.

Systems researchers who study risk and organizational failure — James Reason’s “Swiss cheese” model of how accidents slip through layered defenses, and Sidney Dekker’s later work reframing blame culture into what he calls “restorative just culture”67 — describe roughly the same insight from the safety-engineering side: an organization’s real defenses aren’t the people on the front line reacting to the moment, they’re the structural layers built in advance that make individual, real-time judgment less load-bearing than it looks.

The contrast case is what you might call ad hoc friction, or sludge: a form, a discretionary call, a policy that gets worked out in real time by whoever happens to be handling the case. This fails in both directions at once. It’s slow when speed doesn’t matter (a routine benefits renewal that re-litigates eligibility every year), and it’s unreliable exactly when speed does matter, because the hard thinking is happening under the worst possible conditions — performed by the single most time-pressured, most exposed person in the whole system. Ask someone to weigh “was this negligence or an honest mistake” in the same breath as handling the actual emergency, and you get one of two outcomes: dangerous hesitation, or a reflexive rubber stamp that defeats the point of having judgment involved at all.

Speed and deliberation were never actually in tension

The real tradeoff isn’t between moving fast and thinking carefully. It’s about when the thinking happens and who is doing it. An institution that needs to act fast under pressure has exactly two options: do the hard thinking in advance, while there’s no pressure, and turn the crisis-time decision into a lookup — or skip the advance work and improvise an answer nobody can fully stand behind, produced by whoever’s unlucky enough to be on shift. Disaster law, JAL’s 2007 policy, and mandatory hospital safety managers are three completely unrelated domains that all landed on the first option.

I don’t think this generalizes cleanly to “always pre-commit everything,” though, and that’s the part I haven’t resolved. Front-loaded rules are sticky in a way ad hoc judgment isn’t — once “catastrophic disaster” has a legal definition, it’s genuinely hard to revise it quickly when a new kind of disaster doesn’t fit the categories drawn years earlier. Pre-commitment buys speed at the cost of flexibility for the case nobody anticipated. So the question I’m actually left with isn’t “should institutions front-load their hardest decisions” — clearly, sometimes, they should. It’s: how do you know in advance which decisions are safe to freeze into a rule, and which ones need to stay improvisational, held open for a judgment call nobody could have written down ahead of time?

  1. Jiji Press. “熊本地震、激甚指定へ 予備費２００億円、４日決定―高市首相、初の視察.” Accessed 2026-08-06. ↩

  2. Yahoo!ニュース / 日テレNEWS NNN. “令和8年熊本地震 政府が予備費から総額242億円の支出決定 「激甚災害」に指定の方針.” Accessed 2026-08-06. ↩

  3. JAL. “JALグループ安全報告書 2006年度.” Accessed 2026-08-06. ↩

  4. ANA. “ANAグループ安全理念・安全行動指針.” Accessed 2026-08-06. ↩

  5. GemMed. “2026年4月からの「医療安全対策の厳格化」詳細.” Accessed 2026-08-06. ↩

  6. Flight Safety Australia. “The absent-minded professor who made a safer world.” Accessed 2026-08-06. ↩

  7. newwin.ch. “Just Culture: Part 1 – Basics & Cheese Model.” Accessed 2026-08-06. ↩