GDS Local have published the first iteration of their architecture for (digital) local government.

It looks at this stage like very high level, simplified enterprise architecture.

It will be interesting to see where it goes next. I worry about architecture being done for its own sake, and so understanding what the outcome this will help achieve is going to be key.

Phil’s accompanying blog post helps with some of that:

It makes it easier to describe applications, integrations, data and underlying capabilities, regardless of which products are in use. That supports clearer conversations with suppliers, internal governance groups, and central government. It also makes dependencies and risks easier to see.

For me there are two pragmatic outcomes that make sense here.

One develops the shared language thing further, translating between technology design and service design, so conversations can be had by both sides with everyone understanding what the others are referring to.

I think that probably lies in connecting this kind of technology architecture with service patterns, such as those being worked on in Wales.

Secondly, I wonder if the nailing down of a common language and definitions of what digital gubbins councils need to deliver their services might lead to interesting conversations about the delivery of that gubbins, and where capacity could be created in the sector by sharing a lot of the stuff that doesn’t really matter to most people. More on that in this post from ages ago.