Yes, deciding to adopt a new technology has historically been a pain. An expensive, dull, prolonged pain nobody wants to deal with. The problem I have is that those adjectives belong to OLD tech. Putting nimble new technology in the same pile with 90s software is like mixing vodka with milk.
Here’s the gist of it: people need to be comfortable with the cost and potential risk of adopting new technology. How do you make them comfortable? By calculating these costs and potential risks. One simple guideline is the 10X rule: if you can expect a return of 10 times your investment, then it’s worth it.
However, with technology – especially if it spans across different departments – you must consider that your gains will come from any of several improvements, or a combination of improvements:
Admin processing speed
Mobilising the workforce
Your gains will be the sum of all factors. If adopting a new technology provides an improvement in one factor but it’s at the expense of another factor, it may not be worth adopting. This tends to limit everything to a financial view though. A far better formula includes non-financial factors, some of which will outweigh the financial ones. You need to also remember that some investments in new technology can require at least a year to show their true value.
Managing risk should also be incorporated into your analysis, but remember that you take a risk whether you adopt a new technology or not. The advantages a new technology provides may not be obvious – until a competitor adopts that technology and makes your competitive disadvantage clear. In that case, adopting a new technology reactively will put you on the back foot. Playing catch-up is never a good business move!
Risk reduction recipe
Admittedly, new tech is the unknown. The unknown is typically scary to humans. Working to remove that fear is key to successful tech adoption.
One sure way to reduce the risk is to go for a taster: a proof-of-concept implementation. Starting small & early allows you to identify problems early when they are far easier and less expensive to correct. It also makes it easy to start over if the proverbial hits the fan.
Existing process and changing culture
Also keep in mind that both organisational and process changes will be needed when bringing in tech. Procedural changes are very common. The reason why you are looking at that tech is typically to improve current processes you have found lacking. You must be aware that tech is here to improve not replicate. Trying to fit clunky processes on efficient technology is not only frustrating but a complete waste of time and resource. Changes to previous processes will need to happen and you will have to expect some resistance to those changes. Again, human nature.
The mark of good technology for me is its accessibility and great user experience across the board (from top to bottom, from left to right). Because you are effecting change (and that’s difficult enough), the very last thing you need is that change to come in the form of clunky, pain in the ass – MS-DOS looking software.
In my quest to empower people through tech, one problem I come across a lot is: “How much resource do I need from our side because we really cannot spare anyone?” This question is proof of a bad reflex left over from dealing with old tech. The type of tech that takes a year just to implement, another year to train for and another to realise it’s not right for you anyway even though it is costing you serious cash. The type of tech that is SO unlike what you know and love in your personal life, it might as well be alien. A vintage alien at that.
Clear communication will help overcome the organisational and process challenges. When people get that you are in fact trying to empower them to work better and easier, they will want to be part of that higher drive.
As Richard Branson says: “Screw it, let’s do it!” Move quickly, find out what works and what doesn’t. Stalling, procrastinating of burying your head in the sand are NOT ways to avoid a pain in the ass.