As part of the work putting together a Technology Strategy (think IT + digital) for my current employer, I came up with six principles of good technology. The idea is that each of these principles must be met by any piece of technology the organisation wishes to buy or to build.
(The purpose of the strategy is to develop what was a fairly traditional IT team into a rebranded ‘Technology Services’ team; and to bring them out of ‘maintenance mode’ and into more proactive space, where technology can be used to drive improvement and efficiency in the way that services are delivered. To my mind, IT in this sense cannot be worked around or ignored in a JFDI sense if you’re serious about transformation in your organisation – it must be tackled head on, otherwise you’re doomed to failure. More on this in a future post.)
Anyway, here are the principles, in case they are useful.
Cloud native – to ensure all the systems we use are designed for the internet age
Core to the Technology Strategy is for the Council to become a ‘cloud native’ organisation, making use of commoditised utility computing wherever possible. A district council has somewhat limited resources, and those resources are best spent where we can add most value, and to my mind, that isn’t in upgrading firmware or patching servers.
Our preferences when investing in systems is as follows:
- Software as a Service – where possible, we prefer to use a SaaS solution to minimise the responsibility we have to support and maintain a system’s infrastructure
- Platform as a Service – for bespoke workflows and requirements, we develop using a cloud-hosted, capability-based, off the shelf PaaS
- Infrastructure as a Service – where the market is yet to deliver an acceptable SaaS solution and the requirement is too complex to deliver via PaaS, then a more traditional application will be hosted within a public cloud environment such as Amazon Web Services or Microsoft Azure
Mobile ready – to ensure all the systems we use can be accessed anywhere, from any device
Legacy software was built for desktop based computing and thus doesn’t work well with the new style of devices that have emerged in the last decade.
We want staff to be able to make use of easy to use devices such as smartphones and tablets while working away from the office.
Any software we purchase, renew or develop must be enabled for mobile working out of the box, without the requirement for middleware or extra investment in specialist hardware.
Interoperable – to ensure the data our systems use is easily shared between people and applications
Legacy software makes exchanging data between systems difficult and expensive.
Cloud native systems and software offer freely accessible and publicly document application programming interfaces (APIs) and web services, which can be used to link systems together very simply, often with very limited programming required and use of ‘drag and drop’ style interfaces.
We will insist that all technology we invest in offers this ability to share data across systems.
Flexible – to ensure we make good use of shared platforms and capabilities across our services
Many of the systems we use are made up of the same common capabilities – booking , reporting, managing cases, payments, assessments and so forth – however they are trapped in service specific silos.
We wish to tackle this inflexibility by investing in flexible, generic capabilities that give us the building blocks to design our services, and the systems then run on, in the way we want to, and not be beholden to system suppliers.
Enabling customers – to ensure all the technology we deploy helps our customers enjoy a consistent journey across our services
We want to put our customers at the centre of the way we do things. This means two things:
- Any system we purchase or develop must have online self service as a foundational part of its design, to ensure as many as possible choose to take this option
- Service and system design should be based upon evidence generated through user research and take a customer-centric approach
Proportionately secure – to ensure that the Council’s and our customer’s data is as safe as it needs to be to enable us to deliver our best work
Information security is extremely important and we must be vigilant in looking after the data we hold, particularly that which belongs to our customers.
However, with our move to internet based technology, we can follow best practice guidance from central government to classify our information assets to enable us to work flexibly when it is appropriate to do so.
We want to encourage colleagues to think for themselves around information security, rather than relying on one size fits all policies that often are not adhered to.