Staff adoption in the first month decided whether the project succeeded. What we did to reach 94%, and what we would do again.
Software for schools has an unusual constraint: the people who must adopt it are busy teachers who did not ask for it. When Northgate Academy engaged us to replace four tools and a great deal of paper, the technical work was the smaller half of the challenge.
We spent a week observing registration, grading, fee collection and parent contact. The most valuable discovery was how much time went on re-entering the same information in different places. Every screen we designed had to remove a step, not add one.
Attendance is taken in the first five minutes of a lesson, often on a shared computer. We built it so a whole class can be marked in under thirty seconds, with defaults that make the common case a single click.
We ran short sessions in the departments themselves, using each teacher’s own timetable and class list. People learn faster when the data on screen is theirs. We also nominated one confident teacher per department as a first point of contact.
Attendance first, because it is daily and low-risk. Grading second. Fees and parent communication last, once confidence had built. Each stage ran in parallel with the paper process until the numbers matched.
1,400 students managed, 94% staff adoption in the first month and no paper attendance registers remaining. The lesson we carry to every project: adoption is a design problem, and you solve it by respecting how people already work.
