Government Technology Is Not Broken. Government Leadership Is Afraid.

Six agencies. Three decades of excuses. One conclusion: the tools were never the problem.

I’ve been sitting on this one for a while. Not because I wasn’t sure about the argument — I’ve been sure about this argument for twenty years. But because saying it plainly, in public, feels like a risk. That’s exactly why I’m saying it. If you’ve worked in federal technology and you recognize what I’m describing, share it. If you disagree, I want to hear that too. Either way — let’s stop pretending the problem is the procurement rules.

For thirty years, we’ve accepted a comfortable lie in federal IT: that legacy systems, compliance frameworks, and procurement rules make real modernization impossible. That AI governance is too complex to act on. That change takes a decade, requires a task force, needs more study.

It doesn’t.

I’ve run technology at six federal agencies — across defense, immigration, public health, international broadcasting, and the arts. Every time I walked into a new organization, I found the same thing: the tools existed, the legal authorities existed, the talented people existed. What was missing wasn’t resources or runway. What was missing was a leader willing to make a decision and stand behind it.

At USDA, we had food safety inspectors training on VHS tapes. We fixed it — not with a multi-year program of record, but with a decision. At DHS, I built the first federal hackathon and stood up a DevOps organization inside an agency that had declared DevOps impossible. At Voice of America, we built AI-powered transcription, a streaming platform, and 20 mobile apps inside a bureaucracy most people had written off. Not because the rules changed. Because we decided to lead instead of waiting for permission.

Here’s what I’ve learned: the policy is rarely the problem. Policies can be changed — you are the policymaker. Procurement rules can be navigated — people do it every day. Compliance frameworks like FISMA and the NIST RMF are not obstacles to modernization; they are the architecture of responsible modernization, if you actually understand them. The problem is that too many federal technology leaders have learned to use compliance as a shield.

“We can’t do that — it’s too risky.” “We need more authority.” “We’ll revisit that next fiscal year.”

These are not prudent statements. They are abdications.

A dramatic editorial illustration of a crumbling neoclassical government building facade, massive marble columns with a single jagged fracture running floor to ceiling, warm amber light glowing from within the crack, deep navy blue atmosphere, architectural perspective grid receding to a vanishing point, the word "AFRAID" barely visible etched into the stone, cinematic chiaroscuro lighting, flat graphic design aesthetic, no people, minimal composition, high contrast, editorial magazine cover style, dark background

AI has made this worse. Every agency now has an AI policy, an AI council, an AI working group. Most of them are elaborate exercises in delay dressed up as governance. Real AI governance isn’t a committee — it’s a decision architecture. You define the use cases, assess the risks, acquire the tools, train the people, measure the outcomes. Then you iterate. That’s it. The agencies actually doing this aren’t the ones with the biggest budgets or the cleanest systems. They’re the ones with leaders who decided that responsible action beats indefinite analysis.

The transformation of government technology is not a technical problem. It never was. It is a leadership problem. And leadership problems have a solution: leaders who are willing to be wrong, willing to be accountable, and unwilling to let bureaucratic inertia become a permanent excuse.

It can be done. It has been done. The only question is whether you’re willing to do it.