One thing you wished people knew when implementing platform based technology in the public sector

Deborah Oxley, expert in Government and Public Sector, Baringa 

Research conducted earlier this year by the Productivity Institute found that between 70 to 80% of services businesses in the UK private sector have adopted some form of platform based technology, and those that have reported significant improvements in the efficiency and innovation of their businesses.

But as the recent state of digital government review highlighted, UK government has been slower to break its traditional habits of developing custom built and organisationally owned technology and moved towards the platform in subscription based models that have become prevalent in other sectors.

I asked some of our Baringa team working in this field what would be one thing they wished more people knew about the adoption of platform based technology in the public sector.

Adam Brocklesby, Partner, expert in Government and Public Sector Baringa

While platform based technology offers many advantages, it's important to recognise that no platform is entirely plug-and-play, and ignore the sales people who will try to convince you otherwise.

The suitability of a platform-based solution depends on several factors, including specific user needs, flexibility, upfront investment, speed to value, and integration with the existing technology estate. Often, an architecture that combines custom built solutions and platform technology is the most effective approach.

When introduced thoughtfully though, platform based technology can become a long term strategic asset, transforming how your services are delivered, governed, and iterated.

However, this requires time and investment. While technology can scale outdated processes and siloed teams cannot. Therefore, it's crucial to invest time in aligning your operating model, organisational structure, and capability before rolling out new technology.

Leo Tagg, expert in Customer and Digital, Baringa 

For me it’s probably around the risks and the cost of customisation. Many projects and programs start with good intention, but as time passes, stakeholders conclude that out of the box functionality isn't going to work for them and they build it anyway.

Every tweak will feel harmless until your knee deep in technical debt project cost and time scales that are spiraling. You should invest time upfront, understand which of your processes are ripe for platforms and which need unique requirements and customisation.

Design your organisation's strategy for customisation and platform features at the very start, and stick to it.

Ilze Skujina, expert in Government and Public Sector

Good practice that I've seen is when the programs that are introducing platforms engage and upskill the key people in the business on the new tech and the new toolkit they will have at their disposal.

These could be process, service or product owners. These people don't have to become technology subject matter experts, but they need to learn enough about the toolkit to have the creativity and problem solving skills to deal with future challenges and drive continuous improvement.