CAQA Digital / The Paper That Never Left

Why the technology is the easy part of digital change

Education providers keep discovering that the difficult half of a digital project has almost nothing to do with what was installed. It has to do with how the institution actually works, who knows that, and when anyone is free to find out.

There is a familiar pattern in education institutions that decide to modernise. A great deal of attention goes into what will be put in, how it will be paid for, and when it will be switched on. Comparatively little goes into the question of what the institution currently does, why it does it that way, and which parts of that should survive. The result is a project that finishes on schedule and yet changes very little about the daily experience of the people doing the work. The thing that was installed works. The work did not get better. Those two statements sit together far more often than anyone plans for.

Part of the reason is that technology is legible in a way that organisational habit is not. A piece of software has a name, a price, a delivery date and a person accountable for it. The way an enrolment actually moves through a provider, by contrast, is distributed across a dozen heads, several spreadsheets nobody owns, a shared inbox, and one long serving staff member who knows which exceptions matter. None of that appears in a project plan. It appears later, usually at the worst possible moment, as a series of small crises that look like technical faults and are not.

The second reason is that institutions rarely separate two different activities that get bundled under one heading. Putting a process online means taking what exists and giving it a screen. Redesigning a process means asking whether the steps should exist at all, in that order, performed by those people, and then building for the answer. The first is cheap, fast and disappointing. The second is slow, uncomfortable and the only one that produces a genuine improvement. Most projects promise the second and deliver the first, because the second requires decisions that nobody wants to be responsible for making.

Timing compounds all of it. An education provider does not have a quiet season in any meaningful sense. There is always a cohort partway through something, always an assessment window approaching, always a group of learners for whom a disruption is not an inconvenience but a genuine problem. Work that would be routine in a business with a slow month becomes expensive when there is no slow month. The calendar does not move to accommodate a project. The project must be shaped around the calendar, and providers that discover this late pay for the discovery several times over.

Then there is the question of whether any of it worked, which is asked far less often than it should be. The habit in most institutions is to treat the switch on as the finish line. Announcements are made, thanks are given, the project group disbands, and the people who now have to live with the change are left to make it work quietly. Nothing has been proven at that point. Whether the work is better is a question that can only be answered by the people who do the task every day, and only after enough time has passed for the novelty and the goodwill to wear off.

This publication is interested in that gap: the distance between a system being live and a way of working being better. The four sections that follow take it in turn. The paper that never left, on processes that were digitised without being rethought. The people part, on why staff knowledge is the asset most often overlooked and most expensive to lose. Doing it in an institution that cannot stop, on sequencing. And knowing whether it worked, on the uncomfortable business of asking, months later, whether anything actually improved.