Systems are wonderful. You can sit down after the Christmas and New Year break, confident that you’ll be able to pick up exactly where you left off. With no problems.
Or can you?
Perhaps that’s not your experience. Perhaps – when you get back to your desk – there’s a moment of dread. A moment where you’re thinking ‘Oh no – not again…!’
Don’t worry. You’re not alone. The world is full of systems that were started for a perfectly good reason. And which have long since outlived their usefulness.
Just to be clear, I’m not talking about ‘old-fashioned’ systems. It’s very tempting to change a system simply because it seems a bit passé, but that, on its own, isn’t enough of a reason. Consider, for example, the fuss that was made about fax machines being used by the NHS. If you want a good example of 1980s tech, look no further. Fax machines were wonderful when they first appeared, but that was long before we had something called email. So surely it makes sense to use email instead?
Or does it?
When older is better…
In conversation with a friend who’s worked in the NHS I asked exactly that question. She grinned. ‘Of course email’s better. But not for everything.’
Surprised, I asked what she had in mind.
‘Simple,’ she said. ‘A nurse is writing a note – by hand – because it’s the quickest way to communicate an urgent request. She sticks it in a fax machine, presses a preset number to send it to a colleague, and the job’s done. It would take her twice or three times as long to send an email. And she doesn’t have the time. Even if she were allowed to use a smartphone in the operating theatre…’
So it may be old. But if it ain’t broke, don’t try to fix it. If it is broke, on the other hand…
Why systems go worng…
There seems to be a rule that the bigger the project, the more likely it is to go wrong. Without casting stones at any particular administration, that seems to go double for major government IT projects.
So why do they fail so often?
I like to think it’s a collision of good intentions. A consultant friend recently told me about his experience with HMRC’s very first self-assessment form, long before the days when there was handy software around to help him fill it out. It took him two weeks, during which he, as a full-time freelancer, earned nothing at all. ‘They should have been paying me to do my tax!’ he laughed. So what did he think was the problem with it?
‘When I looked at it, I could see that someone – perhaps a consultant like me – had tried very hard to make it clear, straightforward, and easy to complete. All the signs were there. My guess? I think that after that it went through about half a dozen different civil service desks. And every single one of them added their own feedback. They’d have pointed out all the little exceptions. All the tricky details. In fact, all those things that make our tax system totally unsuitable for self-assessment – unless you’re a tax accountant. And that form was the result.
‘So yes – that particular road to hell was paved with good intentions. And millions of people had to travel it. All I can say is “thank God for software.”‘
…what can you do if you’re faced with a similar chimera?
A good place to start is with comments and feedback from people who have to use your systems, but had no part in creating them. People coming to it with a fresh pair of eyes. If they’re told what it’s meant to do, they may very well come up with fresh ideas and fresh approaches for delivering the results you really want.
As opposed to delivering frustration, annoyance, and bad feeling.
And if you could use a little help – and another fresh pair of eyes – why not book a free initial consultation?