No Single Model Defines State Data Leadership, Report Shows

States may be investing more in data than ever, but when it comes to organizing leadership around it, there’s no single playbook, according to a recent report.

The Beeck Center for Social Impact + Innovation at Georgetown University’s new report takes a closer look at how chief data officer (CDO) roles are structured across state government. Developed with the National Association of State Chief Information Officers and informed by the Beeck Center’s State CDO Tracker, the report outlines six distinct archetypes of state data offices. Rather than pointing to a single model, it highlights how differences in authority, resourcing, relationships and maturity shape how these roles function in practice.

At the center of the findings is a clear message: “There is no ‘optimal’ model.” Because each CDO approach is a result of trade-offs, with offices evolving in response to state priorities, illustrating that data leadership is context-dependent and adaptive.
That variation is rooted in how the role itself has taken shape. The report explains, “The [CDO] role has emerged less through deliberate institutional design than through a convergence of practical pressures,” including demands for data sharing, analytics and growing attention to data risk and AI. The result is an environment where states often expect similar outcomes — better data sharing, stronger governance and more effective use of data in policy and operations — but operate under very different conditions.

One of the most defining differences lies in where the role sits within government. The data shows a strong tilt toward IT, with 67 percent of state chief data officers reporting through a state CIO organization, while 22 percent are housed in departments of administration or finance. Smaller shares report directly to the governor’s office (7 percent) or sit within other agencies (4 percent).

That distribution reinforces what the report describes more broadly: “Most state CDO offices report to the CIO or equivalent technology leadership, while a smaller share report to administrative, financial or executive leadership.” And where the role is positioned has real consequences. According to the report, “reporting to IT supports execution and scale, but can limit the CDO’s seat at decision-making tables.”

Even with those structural differences, some challenges remain consistent across states, including inadequate funding, which is named in the report as a “persistent challenge,” regardless of how mature a state’s data program becomes.

Priorities, overall, show a mix of evolution and continuity. States earlier in their data journeys tend to focus on building foundational capabilities, while more mature programs shift toward advanced analytics and AI — yet certain core challenges and constraints persist across both groups.
To better understand these differences, the report introduces six archetypes, ranging from early-stage “Lone Builder” models with limited authority and resources to more established configurations such as “Internal Consultant” and “Governance Steward” offices. Others include “Policy Strategist,” “Network Weaver” and “IT-Aligned Executor.” Each reflects a different balance of mandate, capacity and influence, offering a framework for comparing how states approach data leadership without assuming a single path forward.

In practice, the most effective models don’t fit neatly into one category. The report points to offices that blend elements across archetypes, combining technical capability, policy alignment and cross-agency collaboration.

Ultimately, the report frames state data leadership as something still in motion. Structures continue to evolve as governments balance competing priorities around governance, innovation, centralization and flexibility. It stops short of prescribing a single model, instead offering a clearer understanding of why these roles look so different — and what conditions allow them to succeed.