When a building collapses in Nairobi, the public reaction is immediate and familiar: corruption, greed, or incompetence.
These factors are real, but they are incomplete explanations. If greed alone were the cause, failures would be random. They are not. Building collapses in Nairobi follow a disturbing pattern-and patterns point to systems, not accidents.
The failures are overwhelmingly associated with privately financed developments, client-dominated delivery models, weak construction supervision, and limited independent verification during construction.
This consistency suggests a deeper problem: a governance failure in how buildings are delivered, supervised, and held accountable. Increasingly, this assessment is shared across the built environment professions, which have pointed to systemic breakdowns across approvals, supervision, inspection, and enforcement rather than a single technical lapse.
It is important to clarify what this does-and does not-mean. Buildings do not collapse because of corruption in the abstract. Collapse is a physical event governed by engineering realities: load paths, material strength, foundations, and construction quality.
A structure fails only when its load-resisting capacity is exceeded, due to identifiable causes such as inadequate design, poor materials, uncontrolled changes, or absent supervision.
Engineering systems exist because such failures are foreseeable. Design checks, testing, inspections, and supervision are intended to detect and arrest risk before it becomes catastrophic. When a building collapses, it is evidence that this control system failed to function as intended.
Corruption operates at a different level. It does not create structural failure mechanisms. Rather, it weakens or disables safety barriers, allowing known defects to persist.
In practical terms, corruption extends how long unsafe conditions are tolerated, increasing exposure until failure becomes inevitable. This distinction matters because it shifts attention from moral outrage to system performance.
A critical but often overlooked factor is the governance gap in private developments. Unlike public projects-where formal contracts, defined roles, and audit visibility are standard-many private developments operate under weak or informal arrangements.
Developers often control consultant appointments, payment schedules, scope changes, and site access. In extreme cases, the developer acts as both client and contractor, collapsing the separation between decision-making, construction, and supervision.
This concentration of power undermines professional independence. Technical advice becomes negotiable rather than authoritative, and safety safeguards are treated as costs to be minimised rather than risks to be managed.