Maintenance is the mission
We throw a party when a system launches. The hard part starts the next morning.
For public technology, the riskiest moment isn't the build — it's year three, when the launch buzz has faded, the budget has moved on, and the people who understood the system have often moved on with it. The ribbon gets cut once; the system has to keep its promises every day after.
The day-two problem
Software rarely fails all at once. It erodes. Data drifts, dependencies age, an integration quietly changes, a key person leaves, and the workarounds pile up until the system stops telling the truth. In a commercial product, that shows up as a churn metric. In a public system, the cost lands on the person with the least room to absorb it — the resident whose benefits stall, the family whose record can't be found, the community that can no longer trust the number on the screen.
Build for the people who inherit it
The antidote isn't heroics late at night. It's designing, from the first day, for the team that will run the system after the original builders are gone:
- Documentation a stranger can follow — not tribal knowledge living in one person's head.
- Reproducibility, so anyone can ask "why is this number what it is?" and get an exact answer years later.
- Boring, auditable architecture that doesn't quietly import obligations it can't keep honoring.
- Named owners and a maintenance budget, set before launch — not scrambled for after something breaks.
A public work isn't finished at launch. It's finished when there's a workforce and a budget to keep it true.
Fund the upkeep, not just the ribbon-cutting
Funders and agencies love a new build; few line items are less glamorous than maintenance. But for public systems, the maintenance is the mission. We treat it as first-class work — budgeted from the start — and we grow the workforce, through the public-interest technologists we train, that can keep these systems running long after the contract ends.
We don't expect roads, water systems, or libraries to maintain themselves. The software public life now depends on is no different. Treat maintenance as the mission, and the public keeps what it was promised.