WEBVTT

00:00:02.735 --> 00:00:04.606
[Music] Welcome to the
overview on Developing

00:00:04.606 --> 00:00:08.135
and Maintaining a
Districtwide Data System.

00:00:10.076 --> 00:00:12.766
Many districts collect
and work with data,

00:00:12.766 --> 00:00:14.196
but often it is fragmented,

00:00:14.196 --> 00:00:16.826
with four to six different
systems using different

00:00:16.826 --> 00:00:19.786
protocols, vocabulary,
and data structures.

00:00:20.246 --> 00:00:24.806
As a result, data often have
large gaps and many inaccuracies

00:00:24.806 --> 00:00:28.236
and are challenging to use for
instructional decision making.

00:00:28.716 --> 00:00:31.356
To overcome these
challenges, districts need

00:00:31.356 --> 00:00:33.626
to implement a high-quality
data system

00:00:33.626 --> 00:00:37.116
that integrates data together
for easy analysis and reporting

00:00:37.116 --> 00:00:40.246
to a range of audiences,
from district administrators

00:00:40.246 --> 00:00:44.116
and specialists to school
principals and teachers.

00:00:44.416 --> 00:00:47.036
A properly implemented
system is necessary

00:00:47.036 --> 00:00:49.716
to give all stakeholders
the information they need

00:00:49.716 --> 00:00:52.156
to improve student achievement.

00:00:52.706 --> 00:00:56.136
For a data system to meet
such a wide variety of needs,

00:00:56.136 --> 00:00:58.866
it's essential to involve
a variety of stakeholders

00:00:58.866 --> 00:01:03.046
in the system's planning,
design, and implementation.

00:01:03.466 --> 00:01:07.306
Districts can establish a
data system advisory council

00:01:07.306 --> 00:01:08.446
or similar committee

00:01:08.446 --> 00:01:10.916
of individuals comprising
representatives

00:01:10.916 --> 00:01:15.206
from key stakeholder groups,
such as administrators,

00:01:15.206 --> 00:01:18.966
principals, teachers,
parents, and students.

00:01:19.586 --> 00:01:21.756
In this way, a variety
of perspectives

00:01:21.756 --> 00:01:24.166
and needs can be considered
when a district seeks

00:01:24.166 --> 00:01:25.676
to implement a data system.

00:01:26.816 --> 00:01:28.696
The advisors can meet regularly

00:01:28.696 --> 00:01:31.546
to help the district make
key decisions regarding the

00:01:31.546 --> 00:01:35.406
selection and implementation
of a districtwide data system.

00:01:35.916 --> 00:01:40.226
Responsibilities may include -
Developing roles and structures

00:01:40.226 --> 00:01:42.756
to oversee the district's
commitment to data quality

00:01:42.756 --> 00:01:46.306
and use, - Communicating to
staff the importance of data

00:01:46.306 --> 00:01:49.786
in making instructional
decisions, - Providing guidance

00:01:49.786 --> 00:01:52.886
about the requirements and
design of the data system, -

00:01:52.956 --> 00:01:56.866
Overseeing system development,
- Serving as the liaison

00:01:56.866 --> 00:01:59.006
between the different
stakeholder groups,

00:01:59.006 --> 00:02:01.216
soliciting feedback
about concerns

00:02:01.216 --> 00:02:03.886
and possible improvements
to the system, and -

00:02:03.886 --> 00:02:07.106
Identifying professional
development needs.

00:02:07.736 --> 00:02:11.296
First, the district needs to 
determine the system requirements.

00:02:11.326 --> 00:02:13.766
each school can provide
representatives who work

00:02:13.766 --> 00:02:16.616
with the district council to 
communicate their school's vision

00:02:16.616 --> 00:02:19.966
for the data system's requirements
and desired functions.

00:02:19.966 --> 00:02:24.096
The district can then integrate 
these needs into its larger plan.

00:02:24.096 --> 00:02:27.396
The council will also need
to consider factors such as -

00:02:27.446 --> 00:02:31.466
Access and data security,
- Bandwidth requirements, -

00:02:31.626 --> 00:02:33.606
Identification codes for
students and teachers, -

00:02:33.786 --> 00:02:38.586
consolidation of old or
legacy systems, - Initial

00:02:38.586 --> 00:02:43.486
and maintenance costs, - Data
storage, quality, timeliness,

00:02:43.486 --> 00:02:47.766
and reporting, - Formats for
data sharing across systems,

00:02:47.876 --> 00:02:52.116
and - Professional development
needed for implementation.

00:02:52.386 --> 00:02:54.776
The council will need to
weigh all these concerns

00:02:54.776 --> 00:02:57.956
against the resources available
to the district (both human

00:02:57.956 --> 00:03:00.076
and financial) and
decide whether

00:03:00.076 --> 00:03:03.256
to adopt a premade data
system from a vendor

00:03:03.256 --> 00:03:05.036
or develop one internally.

00:03:05.266 --> 00:03:08.796
Either approach may have hidden
costs, such as the time required

00:03:08.796 --> 00:03:12.246
to build a customized system
or the need to purchase add-ons

00:03:12.246 --> 00:03:13.686
that will allow a vendor package

00:03:13.686 --> 00:03:16.946
to meet all the defined
system requirements.

00:03:17.046 --> 00:03:21.286
Once the district determines how
it will procure a data system,

00:03:21.286 --> 00:03:24.406
district personnel need
to plan a staged rollout

00:03:24.576 --> 00:03:27.496
and professional development
opportunities to prepare staff

00:03:27.496 --> 00:03:30.306
without overwhelming
them with new technology.

00:03:30.806 --> 00:03:34.286
Staged rollouts and pilot
tests give staff a chance

00:03:34.286 --> 00:03:36.386
to become comfortable
with the system,

00:03:36.386 --> 00:03:39.366
and provide opportunities
for feedback early enough

00:03:39.366 --> 00:03:43.176
in the process that necessary
adjustments can easily be made.

00:03:43.506 --> 00:03:46.516
Ideally, the rollout
plan would be long-range

00:03:46.516 --> 00:03:49.146
and include timelines
for maintenance,

00:03:49.146 --> 00:03:52.126
training, and end-user support.

00:03:52.626 --> 00:03:54.686
Learning activities
should be available

00:03:54.686 --> 00:03:56.996
that are tightly linked
with specific tasks

00:03:56.996 --> 00:03:59.216
that users will need
to accomplish as soon

00:03:59.216 --> 00:04:00.466
as the system goes live.

00:04:01.456 --> 00:04:03.826
For example, teachers
want to know how

00:04:03.826 --> 00:04:07.666
to access benchmark assessment
results and produce reports

00:04:07.666 --> 00:04:11.476
in visual formats such
as tables or graphs.

00:04:11.796 --> 00:04:14.596
On the other hand, the
attendance monitor might need

00:04:14.596 --> 00:04:18.076
to access daily attendance
rates and produce reports

00:04:18.106 --> 00:04:21.776
that show attendance trends
for individual students.

00:04:22.296 --> 00:04:25.496
Professional development can
also be differentiated based

00:04:25.496 --> 00:04:29.086
on individuals' skill
levels, organizational roles

00:04:29.086 --> 00:04:33.296
and responsibilities,
and instructional focus.

00:04:33.546 --> 00:04:37.216
Topics could include data
transparency and safety,

00:04:37.236 --> 00:04:40.596
system uses and capabilities,
and the use of data

00:04:40.596 --> 00:04:43.426
for modifying instructional
practices.

00:04:43.766 --> 00:04:46.706
Users may require ongoing
technical assistance

00:04:46.706 --> 00:04:49.116
and additional trainings
when system refinements

00:04:49.116 --> 00:04:51.466
and enhancements are introduced.

00:04:52.916 --> 00:04:55.796
A data system may seem like
an unnecessary luxury to some.

00:04:56.066 --> 00:04:59.006
But for districts that
understand the powerful impact

00:04:59.016 --> 00:05:02.566
that coordinated, comprehensive
use of student data can have

00:05:02.566 --> 00:05:06.066
on educational improvement
goals, a data system needs

00:05:06.066 --> 00:05:07.046
to be a high priority.

00:05:08.056 --> 00:05:10.976
To allay concerns over
high costs, the plan needs

00:05:10.976 --> 00:05:14.616
to describe how a data system
supports the district's goals,

00:05:14.686 --> 00:05:17.696
and in a way that clearly
demonstrates why a data system

00:05:17.696 --> 00:05:18.866
is needed.

00:05:19.536 --> 00:05:20.966
To learn more about Developing

00:05:20.966 --> 00:05:22.916
and Maintaining a
Districtwide Data System,

00:05:22.916 --> 00:05:24.236
please explore the
additional resources

00:05:24.236 --> 00:05:26.176
on the Doing What Works website.

00:05:26.516 --> 00:05:27.910
[Music]