When 'workflow tools' become another problem

One of the small ironies of school operations is that the platform purchased to reduce admin load can quickly become an additional source of admin load. I have watched this happen often enough that I now look for it.

Three patterns to watch for.

Pattern one. The workflow tool becomes the place where decisions are made instead of the place where decisions are recorded. This is the most common failure mode. The tool was sold on the basis of "track all your decisions in one place". In practice, the team starts using the tool to debate the decision, document the decision, communicate the decision, and chase the people who haven't read the decision. The tool absorbs all of these jobs and slowly grinds.

The healthier pattern is to use the tool only for the thing it is good at. Recording decisions and the next action. The decision-making conversations should still happen in the formats your school already uses well. A meeting, a staffroom corridor, a phone call. The tool catches the outcome.

Pattern two. Notifications outpace attention. The school turns on every notification setting at install time, and within two weeks staff are receiving thirty or forty pings a day, almost none of which are actionable for the recipient. The reaction is predictable. Staff start ignoring notifications. The notifications they then miss are sometimes the important ones.

The healthier pattern is to start with the smallest possible notification footprint and add only when a specific failure case justifies it. The default should be "I will check this tool on Monday morning" rather than "the tool will tell me when something happens". Most school workflows are not so urgent that a Monday morning check is too late.

Pattern three. The tool becomes the source of disagreement about what is true. The leadership team's spreadsheet says one thing. The workflow tool says another. The week-old PDF that was emailed to parents says a third. Nobody is sure which is current. The tool was meant to be the source of truth and has instead become a fourth source of confusion.

The healthier pattern requires a hard organisational decision, not a software decision. Pick one source of truth for each kind of question. The workflow tool, the SIS, the email, the spreadsheet. Whichever you pick is fine. What is not fine is having three of them be the source of truth simultaneously, because in practice that means none of them are.

If your school has bought a workflow tool in the last eighteen months and you are not yet sure whether it is helping, the diagnostic question I would ask is this. When the deputy principal needs an answer to a current operational question on a Wednesday afternoon, what does she check first? If the answer is the workflow tool, the investment is paying off. If the answer is anything else, you have a structural issue that no amount of feature requests will fix. The fix is at the level of how the tool is being used, not what it can do.