10T Studios
en/sk
All articles

Why systems companies pay for end up unused

5 min read

Short answer

Systems fail not on technology but because they are slower than what they replaced, because nobody said why they exist, or because they were specified by someone who never did the work. All three are visible in the first fortnight and all three are cheap to fix.

01Three reasons that cover most cases

  • 01The brief was written without the people who do the work, so the system solves the process management imagines rather than the one that runs.
  • 02The new way is slower than the old one. If recording something takes longer than telling a colleague, the colleague wins.
  • 03Nobody said why. Without that, everyone assumes the worst — that it is surveillance.

02Spotting it early

Measure how many records were created in the first two weeks and how many came from one enthusiast. If three quarters are from one person, the system has not been adopted; it has an advocate.

The second signal: the group chat still handling what the system is for. Chat is the most reliable indicator of what the system cannot do.

03What management can do

Stop using the old way themselves. When a manager keeps asking for status by e-mail, the system is officially optional whatever anyone says.

Set aside the first month for changes and say so in advance. People report what bothers them only if they believe something will happen.

04What does not work

Training. A system needing a two-hour course to record a job has a design problem, and training will not fix it.

Punishing non-use. It produces compliance on paper — the data will be in the system and it will not be true, which is worse than an empty system.

Frequently asked

Why do employees not use a new system?
Usually because it is slower than what it replaced, because the brief was written without the people who do the work, or because nobody explained why it exists.
How early can failure be spotted?
Within two weeks. Watch how many records were created and whether most came from a single enthusiast.
Does training help?
Rarely. If a system needs a two-hour course to record an ordinary thing, the problem is in the design and training will not remove it.

More articles