Two words turn up in the hindering column of improvement plans far more often than they should: "training required".

It looks like a factor. It sits where a factor should sit. But it isn't one. It's an action wearing a factor's clothes, and once it's in the column it decides the plan before anyone has looked at the problem.

The jump we all make

Most of us know the pattern. We judge that something isn't good enough, and within a minute someone says, "So let's run some training." It feels responsible. It's familiar, it's visible, and it can be booked.

Sometimes it's the right answer. Often it isn't, and we find out a term later, when the INSET has happened and nothing has moved.

The analysis step in iAbacus is there to interrupt that jump. It's force-field analysis, after Kurt Lewin: helping factors on one side, hindering factors on the other, each dragged into priority order. John Pearce and I have always seen it as the heart of the process, because it sits between the judgement and the plan and asks the question a plan can't answer on its own: why are we where we are?

A factor describes the situation

The test is simple. Read each factor back and ask: does this describe how things are, or what we should do about it?

"Inconsistent use of the new system" describes the situation. It's either true or it isn't, and you can check. "Training required" describes a solution. It assumes the cause is a gap in what staff know, and it shuts out every other explanation.

A factor that describes the situation leaves the action open. That's the point. It might still lead to training. It might just as easily lead to a change to the timetable, a simpler form, or a conversation with one department.

A worked example: Kingsbridge Academy

Kingsbridge Academy is a fictional 11–16 school. In September it moved to a new online system for logging behaviour and rewards. At half term, the deputy head who leads on behaviour opens the abacus for that area.

She slides the bead first. Her honest judgement is the second of four levels. Then she checks it against the criteria behind the bead, and it holds: the description at the next level talks about routines being applied the same way in every classroom, and that isn't true yet. For evidence she writes a short statement and links to what the school already holds, the system's own reports and the notes from recent learning walks.

Then the analysis. Her first draft of hindering factors reads:

  • Training required on the new system
  • Refresher session needed at the next INSET
  • More senior leaders on corridors

Three actions. None of them describes the situation. So she rewrites them:

  • Use of the new system is inconsistent: some departments log almost every incident, others very few.
  • Logging from a classroom computer takes several steps, so many staff leave it until the end of the day, and some never get to it.
  • Staff who joined after September haven't had the expectations explained to them.

Only the third factor points towards anything like training, and even then it's an induction conversation, not a whole-staff session. The second points to how the system is set up. The first needs a closer look at which departments, and why.

Give the helping column the same care

It's easy to spend most of the time on what's hindering and very little on what's helping. But improvement is not only problem-solving, and strengthening what already works is usually the cheaper gain. Helping factors deserve equal weight.

At Kingsbridge, the helping column ends up reading:

  • Year 7 tutors use the system consistently and follow up with students the next morning.
  • The pastoral team reviews the logs every week.
  • Students know the rewards and talk about them.

The first of these may be the most useful line on the page. Somewhere in the building, the routine already works. Spreading it costs far less than inventing a new one.

From factors to a plan

For each priority factor, the plan asks four things: what will be done, who leads it, how success will be measured, and by when. One action at Kingsbridge reads:

  • What: Year 7 tutors talk through their next-morning follow-up routine at each department meeting.
  • Who leads: Head of Year 7.
  • Success measure: every department's logs show incidents followed up within a day.
  • By when: end of the spring half term.

Another goes to the network manager: cut the number of steps needed to log an incident from a classroom computer. Neither is training in the usual sense.

When the routines have had time to bed in, she'll place a new bead. The old one stays, faded, so the distance travelled is there for staff and governors to see.

Try the test on your own plan

Open your current plan and read each hindering factor back. If it starts with a verb, or ends in "required" or "needed", ask what situation it was trying to describe, and write that instead. Then look at the helping column and ask whether it has had the same care.

If you'd like to try this in iAbacus with one area of your own, you can set up a trial or book a demo at www.iabacus.com/trial-demo.