05/01/2025
If you read nothing else of mine, read this!
In the most challenging writing I've yet tackled as a data scientist (almost two years in the oven!), I have a 3-parter of articles coming out on the ICMA - International City/County Management Association Blog.
I work through my professional acquaintance with "software trouble" - big and overly complex technology deployments that cost way too much (often 300-500% as much as initially advertised), take commensurately too long, and deliver too few benefits assuming they ever launch at all. All of this, while leaving a human tragedy of resignations, early retirements, and burnout in their wake.
A blunder of the scale of software trouble cannot plausibly be forgiven through good deeds elsewhere in a municipal career. Framed more positively, quietly sidestepping software trouble is one of the most valuable, if unsung, things a city or county leader might ever do.
In Part 1 (link in comments), I find that the headwaters of software trouble are further upstream than typically acknowledged. I keep landing on a poorly controlled brainstorming process as a root cause of software trouble and provide some concrete suggestions for using disciplined winnowing and passionate internal champions to prevent it.
I'd love to hear what you think.