One of the things about my current role is that I can’t really blog much about what I do at work – it’s mostly not suitable for sharing outside the company. That’s why I was pleased when my manager suggested I create a white paper outlining the technology standardisation approach that Fujitsu takes in the UK and Ireland. That is, in a nutshell, what I’ve been working to establish for the last year.
The problem is that, without careful control, the inherent complexity of integrating products and services from a variety of sources can be challenging and costly. Solution architects and designers are trained to create innovative solutions to problems but, all too often, those solutions involve bespoke elements or unproven technologies that increase risk and drive up the cost of delivery. At the same time, there are pressures to reduce costs whilst maintaining business benefit – pressures that run completely contrary to the idea of bespoke systems designed to meet each and every customer’s needs. Part of the answer lies in standardisation – or, as I like to think of it, creating consistency in solution architecture.
I’ll be moving on to something new in a short while (watch this space and I’m sure I’ll be able to talk about it soon), so it’s great to look back and say “that’s what I’ve been doing”.
2 thoughts on “Technology standardisation – creating consistency in solution architecture”