Technology As The Panacea

Photo by Alexandre Debiève on Unsplash

We think of technology as the simple fix. If I simply bought this piece of software, I could get this work done so much more effectively. If only we implemented that new piece of tech, we’d get this billing process absolutely sorted. 

Many times, though, when we actually get the funding, buy the tool and put the tech place, things don’t always go as planned. Lack of user uptake. Wrong data. Incomplete outputs. Manual workarounds. The list goes on. Why does this prove to be so hard?

Well, it turns out that technology isn’t a simple panacea for all that ails us. It can be, but it isn’t always.

Sometimes, the right tech for the problem we’re trying to solve doesn’t exist. Other times, the tech exists but we haven’t done the housekeeping needed to use it optimally, for example, layering good tech over a bad process.

Sometimes, we haven’t got our collective heads in place, in the form of buy-in or readiness. Other times, we’ve customized the tech to try and be too much to too many.

And, of course, sometimes, we simply don’t know how to best use the outputs of the tech in question. So the money goes to waste.

The problem (and benefit) is that “tech” is sexy, it’s in vogue. We’re all about great tech and how tech will solve our world’s problems. 

It will, but not all at once, and not as easily as we’d like. Implementing technology that moves the needle requires plenty of work - before, during and after the purchase.

Have we defined what we’re buying and why we’re buying it? 

What specific problem(s) are we trying to solve?

Does it require a fundamental rethink of how we do what we do to best use the tech? Or will it simply replace what we have (and is that a feasible option)?

Do we need to get the right ducks in a row before we can implement the technology (e.g. is our data in a form that can be readily utilized)?

How quick, easy and painless is the deployment? How much customization is needed for it to make sense?

Are the right folks bought in? (By the way, Tech Fatigue is a real thing.)

Is it easy to use? Does everyone need to use it? Will everyone use it?

Can we easily use the outputs or see the outcomes? Or does it need added work?

Will the benefits outweigh all of the above costs?

That’s not an exhaustive list, but it’s a starter for ten. 

The point is, technology is cool and everyone loves it, everyone wants it. 

But just because we want it, doesn’t mean we’re ready to get it.