Institutional Technology Debt Is Not a Technical Problem — It Is a Governance and Budget Problem That Technology Bails Out
The Claim
The sprawling, outdated digital infrastructure visible across Canadian institutions — 8-year-old WordPress networks, 15-17-year Sitecore deployments, hundreds of rogue departmental sites, 20+ fragmented analytics instances — did not accumulate because organizations lacked technical competence. It accumulated because governance structures, budget cycles, and organizational fragmentation created environments where maintenance was deferred and autonomy produced sprawl. Technology can accelerate the cleanup but cannot address the root cause.
The Evidence Across Multiple Institutions
**Jesse Dyck's WordPress multisite case** is the most technically detailed illustration. A network of nearly 700 subsites ran WordPress 4.9 from 2017 to 2025 — not because nobody knew how to upgrade WordPress, but because the organizational complexity of 200 plugins, 43 themes, and hundreds of site administrators with no centralized audit or accountability made the project perpetually non-urgent. It took a mandatory PHP 8 upgrade to force action. External technical pressure resolved what internal governance advocacy could not.
**Sheridan College's Sitecore-to-Drupal migration** — a 15-17 year deployment — reached migration urgency only when Ontario's higher-ed funding crisis created organizational pressure that years of digital strategy advocacy had failed to generate. Nicole Woodall described a registrarial website built in plain HTML, maintained by nobody, with no analytics, that had existed for years without anyone having the organizational authority to remove it. Not a technical failure — a governance vacuum.
**McGill's digital ecosystem** (500 custom sites outside the central Drupal platform) shows the autonomy-produces-sprawl dynamic. Departments built rogue sites not because they could not use the central CMS, but because the central CMS failed to meet their needs quickly enough. The technical solution (better central tooling) required the organizational solution (governance frameworks, community of practice, standards buy-in) to precede it.
**Empire Life's 20+ GTM instances** did not exist because analytics fragmentation was the intended state — they existed because each team made independent tooling decisions without enterprise governance over a decade. The technical consolidation Woolliscroft described was significant engineering work. The root cause was organizational.
The Paradox: Financial Crisis as Governance Catalyst
Ian Barcarse at Sheridan noted that departments that had lost staff during the funding crisis began adopting the central brand system voluntarily — not because the system improved, but because they no longer had the resources to build their own. Resource scarcity accomplished what years of brand governance advocacy could not. The financial crisis was a governance catalyst.
Implication for Digital Transformation
Digital transformation initiatives pitched as technical projects consistently underperform because they allocate resources to technology and underallocate to the organizational change management, stakeholder alignment, and governance infrastructure that must precede and accompany technical work. The Dyck, Woodall/Barcarse, and Peralta cases all confirm: the hard problem is the coalition, not the code.