Jordan's Digital Transformation Push Is Creating an IT Governance Gap

Jordan's Economic Modernisation Vision targets doubling GDP and creating a million jobs by 2033, backed by roughly JD 41 billion in planned investment — and a National Digital Transformation Strategy running alongside it, pushing government entities, universities, and regulated enterprises toward digital services on an aggressive timeline. The direction is the right one. It is also, quietly, a governance problem for the IT teams executing it.

Every new digitised service, cloud migration, or e-government platform brings in a vendor: a systems integrator, a cloud provider, a security partner, a hardware supplier. Public-sector and regulated entities in particular end up managing a wide bench of implementation and maintenance contracts, often signed under time pressure to hit a national milestone — with vendor governance left as a "we'll build that once things settle down" item that never quite gets built.

The pattern we keep seeing

An IT director inherits a growing vendor list with no consistent record of what each contract actually commits to. SLA terms exist somewhere in a signed PDF, but not in a system anyone checks day to day. Renewal dates get tracked, if at all, in whoever's calendar happened to set the reminder. And when a service disruption happens — the exact moment governance matters most — nobody can produce a clean answer to "what were we promised, and did we get it?"

This isn't a Jordan-specific failure. It's what happens anywhere digital transformation outpaces the unglamorous back-office work of tracking what was actually bought. Jordan's pace right now just makes the gap show up sooner.

Why this matters more under PDPL

Jordan's Personal Data Protection Law adds a compliance dimension on top of the operational one: entities need to be able to show which vendors touch personal data, under what terms, and with what accountability if something goes wrong. A vendor list that lives across email threads and a shared drive doesn't answer that question quickly — and "quickly" is exactly what a regulator or an internal auditor expects.

Building governance in, not bolting it on later

The cheapest time to build vendor governance is before the vendor list gets long — not after. For teams already mid-transformation, the practical starting point is the same either way: one system of record for every active contract, its SLA commitments, its renewal dates, and its performance history, updated as it happens rather than reconstructed from memory when someone finally asks.

1. List every vendor brought on as part of a digital transformation initiative in the last 18 months. Most teams find more than they expect.
2. Check whether SLA terms for each are recorded anywhere searchable — not just filed as a PDF.
3. Before the next initiative kicks off, decide where its vendor's governance data will live from day one.