Why technicians abandon facility software

Ask a facility director why their last system failed and you will usually hear "the team never adopted it". Ask the team and you hear something more specific: it took too long, it did not work in the basement, and it asked questions nobody could answer.

The four o’clock test

Any feature should be judged by whether a technician will use it at four o’clock on a cold Friday with one job left. Not in a training room. Not in the demo. At four o’clock, with cold hands.

Most facility software fails this test in the same three ways: too many taps, a form instead of the work, and a spinner where there is no signal.

Signal is not an edge case

Plant rooms, basements, tunnels, lift motor rooms, roof plant behind a parapet. These are not unusual places for facility work. They are where most of it happens. Software that treats no signal as an error state has misunderstood the job.

The right behaviour is to say nothing at all. Save the work, upload it later, and never make the person think about it. Telling a technician their work is "syncing" is telling them about your plumbing.

Give people a way to be honest

A technician who cannot record that a job was impossible has two dishonest options and no honest one. Building a way to turn work back, with a reason, is not a nice extra. It is what makes everything else in the record trustworthy.