Running an Institution

Moving From Registers to Software Without Losing a Term

studive-official0 comments
Moving From Registers to Software Without Losing a Term

The failure mode is not that the software is bad. It is that the school tried to switch everything in August, and by October was running two systems and trusting neither.

Every school that has done this has a story about the first attempt. Software bought in summer, training in August, enthusiasm in September, and by November the registers are back out “just to be safe” — which means both systems are half-maintained and neither can be trusted.

The mistake is almost never the choice of software. It is the shape of the change.

Move one thing

Pick the single process that causes you the most pain and move only that. For most schools it is attendance or fees.

Everything else stays exactly as it is. No simultaneous move of examinations, payroll and parent communication, however much the vendor's demonstration made it look easy.

One process means one habit to form, one set of problems to solve, and one thing to judge after a term. It also means that if it fails, you have lost one process and not a year.

Run parallel, but with an end date

Running paper and software together for a few weeks is sensible. Running them indefinitely is how schools end up with two unreliable records.

Set the date in advance: for six weeks we keep both, after which the system is the record and the register is history. Say it out loud to staff at the start.

Without a stated end date, the parallel period never ends, because there is always a reason to keep the paper one more month.

Someone owns the data

Every system needs a person responsible for students being in it, sections being current, leavers being marked and new admissions being added.

When nobody owns this, the system diverges from reality within weeks and staff start working around it. When they work around it, it is finished, because a system people do not trust is a system people stop updating.

This is a real part of someone's job, not something that happens in the gaps. Name the person before you start.

Decide the process before you configure it

If three members of staff have three understandings of how fee concessions are approved, software will not settle that. It will encode one of them, and the other two will find a workaround.

Have the argument first, on paper, and write down the answer. The configuration then takes an afternoon. Done the other way round, you spend months discovering the disagreement one exception at a time.

Train on the real thing

Generic training in a hall, in August, on demonstration data, is forgotten by the time it is needed.

Train small groups on their own work, with their own students, in the week they will start using it. A class teacher needs fifteen minutes on how to mark attendance for their section — not an hour on the full system.

And accept that the first fortnight will produce the same five questions from everybody. Answer them patiently; that is the actual training.

Judge it after a term, with numbers

Before you start, write down what better would look like: attendance recorded for ninety per cent of classes daily, fee defaulters identified within a week, whatever matters to you.

After a term, check. If it has not improved, find out why before adding the next module — adding more to a system that is not working produces a bigger thing that is not working.

If it has, move the next process. One at a time, a school can be substantially digital in two years, with each step actually working. Attempted in one summer, it usually produces two years of recovery instead.

Comments

Leave a reply