This week I picked up a new phrase (thanks Ian); ‘technology sovereignty’. It’s a nifty way to explain a principle I’ve used in my work ever since I can remember.
Technology Sovereignty = While you might, and probably should in many cases, outsource your technology supply and maintenance needs to a specialist/s – you should not hand over complete control.
There’s obvious downsides if you do hand over your sovereignty; reduced ability to negotiate price or options, reduced flexibility, and more. You could even find yourself in the terrible position I once experienced.
At one workplace I inherited a setup where the website CMS, development contract and hosting were all with one supplier – then the company went into administration due to a hostile merger. I was forced to move suppliers without any real choice, unless you consider months of downtime a choice. The new supplier had significantly higher prices and no understanding of the CMS (among other things).
I learnt a lot from that experience. One thing I realised is how much I’ve leaned on my computer science background to help me at work. The benefit of being able to challenge and co-design solutions with suppliers has definitely helped me to keep more control and avoid all kinds of issues.
Recently someone told me they didn’t feel they should need to know this stuff to do their digital job. In reply I talked about car maintenance. I was taught about how a car engine worked in school. It didn’t mean I could build an engine – but I could describe how it should work. It’s meant I can challenge car mechanics where needed.
So should you outsource your technology?
Yes, at least in part. Outsourcing often means you can benefit from economies of scale that come with a supplier or platform having multiple clients. But make sure you know what you’re talking about and avoid having a single point of failure unless it’s an area where failure doesn’t matter.