Perspective · Public-Sector Technology

Enterprise Architecture in Government

Subbarao Mupparaju — Director of FI$Cal and California’s former State Chief Enterprise Architect — on what enterprise architecture actually means in government, and why it so often decides whether a large public system succeeds or struggles.

What enterprise architecture is — and isn’t

Enterprise architecture is the discipline of seeing how the many moving parts of an organisation’s technology fit into a coherent whole: how data flows, how systems talk to one another, and how you change one part without breaking the others. In government, where systems must serve everyone and endure for decades, that coherence is not a luxury — it is the difference between a modernisation that lasts and one that has to be redone.

It is often misunderstood as diagrams and standards documents. In practice it is a way of making decisions: what to build, what to buy, what to retire, and in what order — so that each choice strengthens the system rather than adding to its complexity.

Why it matters more in the public sector

Private organisations can often change course quickly. Government systems carry heavier constraints — legal, procedural, budgetary — and much longer time horizons. A statewide platform may outlast several budget cycles and the people who started it. Good architecture is what lets an organisation of that scale evolve without losing its footing: it keeps the foundations stable while the details change.

Subbarao Mupparaju began his California civil-service career as the State’s Chief Enterprise Architect at the Department of Technology, directing statewide enterprise architecture and digital-transformation initiatives, before serving as Chief Information Officer and, later, Director of the Financial Information System for California (FI$Cal).

Architecture and the book-of-record milestone

The value of an architectural mindset showed in one of California’s largest recent modernisations: moving the State’s official accounting book of record onto FI$Cal in 2026, a milestone mandated by Assembly Bill 127. Delivering it meant retiring legacy arrangements without breaking the countless processes that depend on them — precisely the kind of change enterprise architecture exists to make safe.

Good architecture is what lets a large organisation change without losing its footing.

Read more