Federal Government Data Maturity Model
Federal Government Data Maturity Model
Federal Government Data Maturity Model
Data
I s-
3� Data use is uncoordinated Data use is by request
Culture rf and ad-hoc. Quality issues Quality programs are
�� 3 limit usefulness nascent
UI
8 5.
� I»
.., G)
Data managed in silos. Data managed in silos;
Data
Management
ca documentation sparse;
standards not regularly
some documentation exists;
standards not regularly
fc applied applied
0�
C
el if
��
Data r-· No dedicated personnel Some siloed data teams;
Personnel ii cB performing data duties no clear career path for data
c5" C personnel
i1S1. I3:
!!!. I»
0 ::::,
Systems/ ::::, I» Data is stored in siloed Data are stored in siloed
3:CC systems; data are frequently systems; some data can be
Technology 3
(D
�
I»
-·
copied to facilitate use programmatically accessed
::::, (D
::::,
na
(Q -
Data
,,
I» -
::::,-
Loose affiliations of Bureau-level collaboration,
=::::S(D-
er
I»
C
el
Low Capability
C"
Some data and analytics lnfar.egancy 0
are routine and have quality
programs supporting key
High demand for data across
agency. Drives decision communities d I
shar8 analy9as, en i.o· �
iii
making S" ::I ::I
assets practicas UI
::I a,
'i
a
::I
Q)
C.
c.
Data are managed with Data are managed a. )> ::I
Data managed across the
agency; documentation is cross-functional applications considering agency-wide y,
)> 0
8�
Q)
i
unifonn; some standards in mind; documentation is needs; documentation is C
C
::I
are applied unifonn; standards regular1y unifonn; standards are 6" C.
agJ>lied unifonnly applied C" :s::
3 -·-·
!a
-·�
- UI
UI
0 -·
t
::I
Agency level collaboration, Agency�evel organization Multi-agency advancement
data ownership and accountable for data of data ownership and
stewardship governance stewardship (1)
C.
High Capability
Finally, the model provides a common language and framework organized ideas and suggestions to help agencies consider what
to help promulgate common solutions and best practices across works best for them as they carve out a path to success.
federal agencies toward advancing data-driven decision making.
This document contains helpful guidance within each of the lanes
that address numerous organizational dynamics when creating
Outcome Measure
organizational change. The top lane of the model, ':A-nalytics Capability'' should be consid
ered an outcome measure for capability. This lane provides a contin
uum of demonstrated capability from the simplest summary reporting
How to Use this Model to the most complex prescriptive analytics requiring a vast amount
It is important to note that the purpose of this model is not to provide of data and supporting processes. The other five lanes all help to
a rigid or prescriptive "one size fits all" approach to improving data support and enable greater capability, and are essential to achieving
capabilities within federal agencies. Nor does it maintain that all lasting change across an organization.
agencies need to reach or complete all milestones within all lanes to
achieve optimal data capabilities. It simply provides a framework of