Meatware
JC pontificates about technology
An occasional series.
|
Those mortal flesh sacks sitting in front of the telescreen, weeping bitter tears and wishing things could be otherwise.
You and me, brothers and sisters.
The main problem with many millenarian tech implementations. It's all great, in theory. But you have to deal with luddites, morons, charlatans — and perfectly likeable, sensible people who are just used to working in a certain way, and quite like it. Technology impresarios cannot control the meatware, believe it to be fundamentally flawed — Human, all too Human, after all, and therefore feel justified in ignoring the meatware altogether when manipulating their equations.
This is a tremendous mistake, for [[you can lead the meatware to the application, but you can’t make it reliably fill out the metadata you want]].
On the difference between humans and machines
Role reversal: A favourite confusing of millenarian punters and change managers is confusing the things machines do well (accurately and quickly following rules) with the things humans do well (figuring our what to do when something unexpected happens; making decisions; exercising judgment). It’s surprising how often risk management is conferred on a computer system, and the users are asked to simply enter formulaic data into it. If you don’t think your humans are up to good enough at making decisions or wise judgments, the answer isn't to buy a computer to do that for you. Computers will be worse. The answer is to hire better people.
- “Ahh, yes, but better people are more expensive, you see.”
- “But computers can’t figure out what do do when there are no rules.”
- “But they are much cheaper and faster at doing it.”
Over-Ambition: Implement computer solutions to save on repetitive manual tasks, allowing your people more time to do what they do best: manage risk and look after your clients. Over-engineered technological solutions are slow, inflexible and unwieldy to use and to maintain. they need a runbook. The more complicated the system is, the less likely humans are to use it properly. The less often they use it, the less often they will spot glitches. The harder it is to maintain, the more quickly its runbook will get out of date. The less effective the runbook, the more exceptions it will throw up. The more exceptions you have the more you need humans to handle them. A computer system that no-one uses is an expensive paper-weight.
- Think global: act local: Yes, management information is why you need the system, and no, people at the coal face couldn’t care less about it. But they do care about information: that’s what they do all day: process information. Your people are already capturing all the data they need. Rather than throwing out their existing practices, analyse what they do and look for localised “tricks” to make these tasks easier for your staff to collect and process the information they need. Spend your it resource building ways to mine those enhanced information systems.
Aesop’s dog: Remember the fable of the dog with the bone: before you spend large, consider the information and the resources you already have available to you. Could they be reconfigured to better present information they're already capturing? Could you overlay reporting on existing systems? There are some powerful workflow tools sitting idle in many organisations.
See also
- IT strategy
- Artificial intelligence (being a kind of wisdom not possessed by the meatware.