Multi-Initiative Digital Transformation

Government mandates rarely arrive as implementation plans. They arrive as directives — a paragraph, sometimes a sentence, sometimes a verbal instruction routed down through three layers of leadership before it lands on someone’s desk. By the time it reaches the people who have to make it real, the mandate has lost most of its operational signal and gained a hard deadline. The work, embedded inside ADEK across four years and 150+ schools, was to absorb that ambiguity and convert it into something that 150+ school principals, five departments, and a sprawl of vendors could actually execute against.

What made it harder was that the initiatives never ran one at a time. At any given moment there were five, sometimes seven, parallel programmes — overlapping in stakeholders, fighting for the same budget cycles, drawing on the same exhausted middle managers. A change in one initiative would ripple sideways into three others. A delay in a procurement decision would silently push three roadmaps back a quarter. The portfolio was a single living system, even when it was officially treated as separate workstreams.

Translating mandates before designing anything

The discipline that mattered most was refusing to design any system before the mandate had been turned into a real business analysis. What outcome is this directive actually trying to produce? Who currently owns the work it’s about to disrupt? Where does the existing process break? Which dependencies sit outside ADEK entirely — Ministry of Education, federal data sharing rules, vendor contracts inherited from a previous administration? Until those questions had defensible answers, any technical scope was fiction.

That reframing changed the conversation. The question stopped being “what platform do we buy” and became “what work, performed by whom, will look different on a Tuesday morning six months from now.” Most stalled initiatives across the public sector stall at exactly this gap.

Working the human layer first

Government transformation lives or dies on whether the people closest to the work feel like the change is being done with them or to them. In schools especially — where teachers and principals have seen a decade of programmes arrive, demand effort, and quietly disappear — credibility is the scarcest resource on the project. The approach was to spend disproportionate time inside the institutions before shipping anything: sitting in operations rooms, watching how data was actually entered, hearing the workarounds people had built to survive previous systems. Each of those workarounds was a requirements document that hadn’t been written down.

Once the human layer had been mapped, the political layer became navigable. It was clear which department’s cooperation was on the critical path, which sign-off would take eight weeks instead of two, which conversation needed to happen in person before any document was circulated.

What changed

Initiatives that had previously been stuck at the pilot stage — the well-known failure mode where a shiny prototype runs in three schools forever and never reaches the other 147 — moved to actual deployment. Not because the technology improved, but because the framing shifted. The work was no longer “we are implementing a system.” It was “we are changing how this work gets done across 150+ schools and five departments, and the system is one of the artefacts of that change.” That reframing is the harder, more important transformation, and it’s the one that actually compounds.