The Real Work

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 Paper That Never Left

The form that moves between the same desks in the same order

Digitising a process without redesigning it produces an electronic version of the queue that already existed.

Nobody can remember why this approval step exists

Most approval chains contain at least one link whose original justification has been lost entirely.

Putting a process online is not the same as improving it

The two are routinely described in the same language, which conceals a very large difference in ambition.

The People Part

The staff who absorbed the quirks are the ones who know the work

Years of accumulated workarounds live in people, not in documentation, and they are rarely asked.

Resistance is information about the work, not an obstacle to it

When experienced staff push back on a change, the content of the objection usually deserves examination.

Announcing a change to people who were never asked

The communication is not the problem when the consultation never happened in the first place.

An Institution That Cannot Stop

There is no quiet period in an education provider

Planning assumptions borrowed from other sectors break down against a calendar that never clears.

A change made mid teaching period costs several times more

The same work carries very different costs depending on where in the cycle it lands.

Sequencing work around a calendar that will not move

The calendar is a fixed constraint, and treating it as negotiable is the most common planning error.

Knowing Whether It Worked

Declared complete at go live, when nothing has been proven

Switching something on is the beginning of the test, not the conclusion of it.

Measure the work, not the software

Usage figures describe activity, while the useful question is whether the task got better.

Ask the people who do it daily, six months later

The most honest test of a change is a plain question put to the people living with it.

About CAQA Digital

CAQA Digital looks at digital change in education institutions as an organisational problem rather than a technical one. The starting position is straightforward: the parts of this work that go wrong are usually not the parts involving equipment or software. They are the parts involving processes nobody has examined for years, knowledge that lives in people who were never consulted, calendars that cannot be moved, and questions about success that are asked too early or not at all. Those problems are older than any of the tools currently available, and they will outlast them.

The editorial approach here avoids naming products and avoids technical guidance. Not because those things do not matter, but because they are covered thoroughly elsewhere and because they distract from the harder discussion. Choosing between options is a genuine decision with real consequences, and it is also the part of the work that most reliably absorbs attention that should be going somewhere else. What is written here is intended to be useful regardless of what an institution has chosen, is choosing, or will replace in three years.

The recurring theme across these pages is that institutions get better at changing through practice and honest assessment, not through better planning documents. A provider that finishes one piece of work, waits, asks the people affected whether anything improved, and adjusts accordingly, learns something that carries into the next piece of work. A provider that declares each project a success at the moment it is switched on learns nothing at all, and repeats the same difficulties indefinitely with different equipment. The difference between the two is a willingness to ask an uncomfortable question and to sit with the answer.