legacy

📅 Daily note for 18 September 2024

Am looking into intranets at the moment for a customer. If you have any good stuff to share, please do let me know! Have already heard from Essex County Council and of course Eleanor’s wonderful post⬈ on the topic too. #

Also I’m really interested in stories from local government folk about their experiences trying to implement GOV.UK components like Notify, Pay and so on. Am keen to learn more about what sorts of things are more likely to work than others… #

Kate Tarling has a free email based course called “From silos to services⬈“. Sounds like something you’d be mad not to take advantage of. #

“3 non-tech principles for decommissioning legacy systems⬈”:

Decommissioning and replacing a legacy system is notoriously challenging. You need some serious technical credentials to navigate a complex legacy landscape and create a new solution that is both flexible and future-proof. All while maintaining business as usual for the people that use them.

But technical prowess is not the whole story. Replacing an existing platform is only as successful as the people who will be operating the new solution. And that’s often forgotten.

#

“Blame culture isn’t what I used to think it is⬈”:

Blame culture exists when people feel like they have to explain their actions, and always their failings, as caused by something outside of themselves. This thing happened because that person didn’t do something, they say. Or some other thing didn’t happen because that’s just how it is around here. None of this was caused by my actions, they suggest. That is a culture of blame.

The opposite of a culture of blame isn’t a culture of accepting mistakes, it’s a culture of accepting responsibility. You can see the absence of a culture of blame in the sense of agency people have. When people show initiative and take risks, when they approach problems with ways they can contribute to solving them, when they take control of things within their influence, that’s when there is no culture of blame.

#

Daily note for 6 November 2023

Happy new week!

Am hoping it is going to be a happier week for me, and that I can put the stresses of the last 7 days or so behind me a bit. Saw the GP on Friday about it all, he upped my Sertraline dose. Obviously that’s a sticking plaster rather than a fix, but hopefully it will give me a bit of space to make improvements elsewhere.

Lots of people have been in touch to check in with me. I am hugely grateful.

dxw’s Dave Mann on what needs to happen to improve digital delivery in government.

Lauren Pope’s sharing is just amazing. Take this latest belter as an example: Prioritisation for content teams: a guide.

Fab to see the Adur & Worthing digital bods blasting out more awesome work: Using Low-Code to build No-Code: Customer Enquiry Forms.

Understanding & tackling government’s true legacy.

Daily note for 14 September 2023

These notes have been a bit less daily of late.

I’m chatting to a couple of smaller councils at the moment who are looking to significantly refresh their websites. It struck me that there really ought to a be a go-to playbook on the steps to go through, to avoid utterly pointless wheel reinvention. Of course, there isn’t one, so I am recruiting people to help me put it together. Do please join in!

As an aside, it’s quite interesting using Trello as a means of doing pretty much everything in a collaborative project, including using specific cards as discussion threads, and so on. It’s a remarkably flexible tool, really good at almost everything (except managing projects, ho ho!)

I newslettered yesterday, mostly about the concept of ‘legacy’ in local government tech and what to do about it.

“Focusing on just outcomes leads to whacky tech decisions” – more along the ‘it’s not not about the technology’ lines.

“Lessons for implementing digital health technologies”

I quite like this distinction: “Federation vs Small Pieces Loosely Joined”

Lots of stuff coming out about how Chrome is increasingly unethical as a browser, what with its data collecting and whatnot. Mark, amongst others, is using Firefox, which as a suggestion feels delightfully old school to me. Handily, Mozilla have just published a guide to switching from one to the other.

LINK: “Understanding legacy technology in government”

“I think we have to accept that there’s going to be legacy stuff out there, and there’s going to be unsupported systems. So it would be better to accept that we’ve got that and come up with strategies for how we’re going to manage that.”

Original: https://gdstechnology.blog.gov.uk/2018/05/24/understanding-legacy-technology-in-government/