Already almost at the end of January and 2012 is racing by.
It’s been a busy return to the office post-Christmas and last week saw FutureGov hosting the first cross-council Technology Strategy meeting. This brought together colleagues from Staffordshire and Brighton to start talking about some of the big issues and areas of focus for Patchwork that will be worked through over the next few months. The aim is to make sure our partners are deeply involved in the process of determining the development of the technology behind Patchwork – as well as sharing their experience and expertise.
For a first meeting, we got a lot covered – and made some fairly fundamental decisions. Despite languages such as Ruby on Rails being in no way commonplace in local government, we agreed that Ruby was here to stay. Linked to that conversation, there was unanimous support for Patchwork to be externally hosted in the longer-term, either in the Cloud or another form of secured storage. Cloud itself is definitely seen as part of the future for both partners, although the details of the commonplace concerns over security are not fully worked through yet but we are beginning to work with a range of cloud providers to ensure we can make cloud a reality sooner rather than later.
As we move into gathering feedback from the users in both Brighton and Lichfield District, we agreed we would need to find a way to make this as visible and transparent a process as possible. Taking a user-led approach means that we want to be driven by the needs of frontline staff, and children and families, where we can – again within the limitations of Information Sharing and what is technically possible. There’s more thinking to be done about how we can start to do this with users from two different geographies, particularly in the potential scenario where their needs conflict and prioritisation of the development roadmap is needed. However we all agreed the importance of having as many channels for feedback as possible, making sure that we let users know what happens to their requirements whether they end up in the tool or not.
For me, Friday’s meeting was crucial element of co-design. We’re not only working extremely closely with the end users, but we’re also actively discussing the broader technology issues with our partner local authorities. These are things that the frontline staff my never see or indeed need to be aware of, but completely shape the direction of the product and how it will operate in the future. It was great to see two partners, both at similar stages of piloting, who are so engaged in the conversation.
No doubt the best bit of our job is getting to talk to and work closely with our partners. Friday a very good day indeed.