The Oregon DATA Project
DATA QUALITY –
BY CHANCE OR DESIGN?
DATA IS IN DEMAND
Data driven decision making
Data teams
High Stakes Accountability
State collections
QUALITY DATA IS MANDATORY
Components of Quality Data
Accuracy
Timeliness
Security
Usefulness
Quality data is needed for quality decisions
FACTORS IMPACTING QUALITY
Technology
Timeliness
Utility
Security
Components
Hardware
Software
Network
Policies &
Regulations
Factors
Affecting
Data Entry
Environment
Accuracy
Quality Data
Training &
Professional
Development
By chance or design?
Standards &
Guidelines
Timelines &
Calendars
CONTROLLING THE FACTORS BY DESIGN
Data Entry Environment
Setting
supports data entry accuracy
Quiet,
free from interruptions, provides privacy
Training
Annual
review of data requirements
Data documentation (protocols, procedures)
Timelines
Data
calendar
Who is collecting what and when
CONTROLLING THE FACTORS BY DESIGN
Policies and Regulations
Confidentiality
Data
security
Standards and Guidelines
Data
entry performance standards
Expectations
Clear
expectations
for accuracy and following protocols
guidelines for process/responsibility
Technology
Supports
data entry, spotting/correcting errors
WHO HAS RESPONSIBILITY FOR QUALITY?
Quality Data
Directors
Superintendent
Board
Member
Roles
Principal
Technology
Support Staff
Teacher
Office
Staff
RESPONSIBILITY BY DESIGN
At an individual level
Creator
Takes
responsibility for data elements they create and
understands the impact of data accuracy
Confirmer
Understands
the importance of accurate data
confirmation to ensure data integrity
Consumer
Understands
how to use appropriate data in appropriate
ways to support instruction and student achievement
RESPONSIBILITY BY DESIGN
Leadership at the building/director level
Assumes
overall ownership for data quality
Controls
most of the factors that impact data quality
Technology
Policies &
Regulations
Data Entry
Environment
Hardware
Software
Network
Factors
Affecting
Training &
Professional
Development
Standards &
Guidelines
Timelines &
Calendars
RESPONSIBILITY BY DESIGN
Leadership at the building/director level
Assumes
overall ownership for data quality
Controls
Sets
most of the factors that impact data quality
expectation for data accuracy, security,
timeliness, and usefulness
Creates data steward oversight to maintain data
quality (participates in district DQOC mtgs)
Identifies (holds accountable) those who consume,
confirm, or create data at the building level
RESPONSIBILITY BY DESIGN
Superintendent
Sets
district benchmarks that use data
Expects
others to use data to drive decisions
Identifies
a district data steward
Establishes data quality oversight committee
(DQOC) – mtgs quarterly
Sets “data ownership” expectations
Building
principals,district leaders (special ed, ELL,
business, etc.)
A CULTURE OF DATA QUALITY
DATA QUALITY BY DESIGN
Create a culture of data quality within the
district
Use the concept map as a framework for
discussing and improving data quality issues
Insure that the responsibilities of a data
steward are met within the district
DEFINING A CULTURE OF DATA QUALITY
It is the belief that good data is an integral
part of the educational enterprise.
Everyone in the enterprise demonstrates
that shared belief by using appropriate data
to achieve the enterprise’s goal of student
achievement.
The enterprise is willing to invest resources
to obtain quality data
Everyone in the enterprise shows respect for
the effort taken to produce quality data
14
DATA STEWARD RESPONSIBILITIES
Coordinate data collection process
Provide training
Resolve errors
Establish audit procedures (data
certification)
Create Data Collection Calendar
Develop and disseminate data entry
standards
Interpret data entry manuals for end-users
15
DATA STEWARD RESPONSIBILITIES
Collaborate with others (directors of curriculum,
special education, assessment, etc.)
Collaborate with the IT Director to enhance
computer software for data entry, correction, and
auditing
Be the driving force for maintaining data accuracy,
utility, timeliness, and security
Be aware of the complexity and changing nature of
the data required for state and federal
accountability (State Collections, NCLB, etc.)
16
THE OREGON DATA PROJECT
Developed easy to follow activities that can
help build a culture of data
97 districts attended trainings across the state
All ESDs had representation at the trainings
www.oregondataproject.org
THE OREGON DATA PROJECT
An outside voice to begin the discussion
Provide consultation to district leadership on
building a culture of data quality
Facilitate activities
Available until August 2011
THE OREGON DATA PROJECT
Contact
Ron Hoppes, Technical Training Coordinator
ron.hoppes@state.or.us
0
