Hong Kong’s Deadly Fire: Not an Accident, but a Complex System Forced to Reveal Its Truth
The flames and thick smoke on screen weren’t just Hong Kong’s tragedy—they felt like the very moment a city was forced to confront its hidden truth. This wasn’t an “accident.” It was a complex system, strained by years of accumulation, finally collapsing out in the open.
We all know this, even if we don’t say it: the moment a building is completed, it begins to age. Its fire-safety conditions start accumulating like a growing piece of “technical debt.” We simply avoid facing it. We don’t know when we’re supposed to deal with it. And worse—there’s no system in place that forces us to.
When I teach Scrum, I often say that agility isn’t a method for engineers — it’s a way of navigating a complex world.The Hong Kong fire is a painful reminder of just how true that is.
If you treat a city’s fire-safety system as a “product,” the entire picture becomes strikingly clear —What we lack isn’t regulation. What we’re drowning in is years of accumulated technical debt.
Fire Safety Is Technical Debt:
The Longer You Ignore It, the Higher the Price You Pay
What does this “technical debt” actually look like?
It looks like: “The equipment still works — no need to replace it yet,” “The tarp isn’t fire-resistant — but let’s finish construction first,” “We’ll clear the escape route later,” “The fire alarm doesn’t always respond — probably fine,” “The safety standards don’t need upgrading unless something big happens”… It’s not that we don’t know — it’s that we’ve ignored it for too long.
Technical debt has one defining trait: The longer you avoid it, the more likely it is to blow up at the worst possible moment. The Hong Kong fire was a textbook case of technical debt going bankrupt.
If we can acknowledge that aging buildings naturally accumulate risk,
then regulators can’t limit their role to issuing fines.Their real responsibility is helping every building develop a practical, enforceable “repayment plan” — turning improvement into an ongoing practice, not a one-time slogan.
Lack of transparency: the most dangerous blind spot in urban fire safety
To repay technical debt, transparency is always the first step. Scrum treats transparency as its first pillar, because without transparency, there’s no inspection — and no way to adapt.
Yet this is precisely where both Taiwan and Hong Kong stumble — the information exists, but no one can actually see it.
- How old are the building’s fire-safety systems?
- Is the exterior canvas fire-retardant?
- Has any fire-compartmentation been broken?
- When was the fire alarm system last tested? Was the test actually carried out?
These things aren’t missing — they’re simply scattered across reports, filing cabinets, meeting minutes, and contractor paperwork. Residents don’t know, management committees don’t track them, and regulators have no visibility at all.
In Scrum, transparency isn’t about blame — it’s about ensuring everyone stands in front of the same shared “truth.” Without a shared truth, improvement is impossible.
Inspection ≠ Insight: A Signature Won’t Save Lives — Practice Will
But even with transparency, inspection often becomes a ritual. I’ve seen too many drills — in cities and in companies — that look serious on the outside but are sloppy on the inside.
Forms get filled out, stamps get added, drills get performed, year after year. And when something truly happens, everyone knows: those “checks” were never real inspection.
Scrum’s version of inspection emphasizes cadence, honesty, and actions that lead to improvement. So if we treated every fire-safety inspection as a Sprint Review, we would have to ask: Did this inspection actually bring us closer to a safer building? Or did it just create another document that looks complete?
Real safety doesn’t come from paperwork — it comes from drills and real testing.
Only what you’ve actually practiced counts.
And even when we do see the problems, improvement is often too slow. Deadlines for corrective action sound reasonable, but six-month improvement lists often get stuck on: property rights, costs, scheduling, resident consent, and endless committee negotiations.
When the deadline arrives, nothing has changed — or the progress is far behind.
This isn’t malice. It’s a system that simply can’t deliver.
Scrum-Style Improvement: Making a Building Truly Safer in Just 30 Days
Scrum teaches us that in complex environments, the most effective approach isn’t a massive master plan — it’s taking small, fast, incremental steps. If we replaced long corrective deadlines with a Sprint rhythm — completing one concrete, verifiable improvement every 30 days — the entire city would look very different.
- Clear all evacuation routes this month.
- Test the entire fire alarm system next month.
- Replace all non-fire-resistant materials the month after that.
- Conduct evacuation drills and adjust escape pathways the following month.
- One year later, the building will be ten times safer than it is today
Not because of any massive renovation, but because things kept getting better — continuously
Who Is This Building’s PO? — Safety Needs Someone Who Truly Owns It
But improvement requires someone to set priorities. In Scrum, that role is called the Product Owner (PO). The PO is the one who can say, “Wait — this is what matters most.”
But in most buildings, the one thing missing is a PO. Management committees rotate among residents with limited expertise; budgets are always tight, so improvements are always postponed; cosmetic upgrades win support more easily than internal safety work. Everyone cares — but no one actually owns it.
Perhaps Taiwan needs a new approach: high-risk buildings should have an “external PO,”
and larger buildings should have a “professional safety PO.” Only when someone truly owns the responsibility will improvement actually happen.
The lesson from Hong Kong’s fire is brutally clear — we can no longer govern complex systems with nothing more than a “follow the regulations” mindset. Fire safety isn’t an annual inspection; it’s a product that requires long-term maintenance and care.
Scrum happens to offer three extremely practical insights:
1.Acknowledge the technical debt and break improvements into small, manageable steps
2.Let the PO set the priorities and drive completion
3.Transparency, inspection, and adaptation may look simple, but they are among the few methods that can actually make a complex system better
Transparency, inspection, and adaptation may seem simple, but they’re among the few approaches that can truly improve a complex system
Hong Kong is a mirror. It reflects not only the risks we may face in the future, but also the choices we still have time to make.
Scrum isn’t designed to prevent every disaster.But it offers a way for us to keep becoming safer in a complex world.When a city is willing to treat safety as a product, repay its debts, and improve in small increments— we won’t need another headline tragedy to remind us of what we failed to fix.
May this be the moment we finally learn.
Note: With thanks to Dr. Shih Fu-Yuan, expert in disaster medicine and emergency prevention, for reviewing and contributing valuable insights.