Data, Data, Data... and the associated pressures

Just a quick thought or two on some recent conversations I had related to data quality in our student information systems. Working around K-12 education, I reflect at times on how different things are - or how different they seem - since I was in school. There's data on everything and there's a well-intentioned desire to use that data to improve learning, assess better teaching, have a healthier school environment and things of that sort.

As that data gets analyzed, we see examples all around where the knowledge that this data exists causes changes in behavior. This school security site discusses school crime reporting... and under-reporting. As the link points out, what is my incentive to report every violent incident? Unfortunately, there's quite a bit of incentive to under-report and show that violent incidents are decreasing. No one wants to look like their school is a war zone; consequently, there are whispers that violent incidents should not be reported. That can lead to teachers having their hands full in the worst of cases with students who need to be reported and know that they will not be reported.

Another example I've heard about is the confusion around "in-school suspension". I've been told that districts are to track these suspensions in their student information tool. However, I've also talked to a couple of contacts who gave me an example where a student might have been pulled out of class... not for a 'suspension', but because they're behind in another subject and need additional time for homework or tutoring. That sounds noble, but I was hearing from a teacher who pointed out that she had good students asking her why they should do their homework. Apparently, these students saw that others were - in their eyes - simply being given more time or another chance to complete an assignment. In this case, the school didn't want to flag the students as a 'suspension', nor did they want to give the child a zero on a homework assignment.

I suppose my question is 'how do we get truly accurate and useful data when the overriding concern by some is that the data simply look good'? Perhaps if we weren't so punitive in our discourse and were simply concerned with accuracy, we could get some data that could be relied upon more often.
[Image: http://teflbootcamp.com/tefl-skills/student-discipline-efl-classroom/]

Data Quality and the Responsibility Parable

Our leadership and CIOs have been talking quite a bit lately about data quality. When talking to CIOs about it, the responses are all over the map. This is partially due to the varying authority and expectations placed on them by the local district's administration. One task in the effort to ensure high-quality data is to increase awareness, and there's been quite a bit of that taking place. Somewhere along the way, though, awareness has to be converted into action. The whole situation reminds me of the "responsibility parable", which you can find all over the web and is stated something like this:

Once upon a time, there were four people;
Their names were Everybody, Somebody, Nobody and Anybody.
Whenever there was an important job to be done, Everybody was sure that Somebody would do it.
Anybody could have done it, but Nobody did it.
When Nobody did it, Everybody got angry because it was Everybody's job.
Everybody thought that Somebody would do it, but Nobody realized that Nobody would do it.
So consequently Everybody blamed Somebody when Nobody did what Anybody could have done in the first place.

I think it's worth keeping this in mind, whether your issues relate to data quality or any technology initiative. This could be applied to proper technology planning and evaluation, open work orders that the whole department knows about or just about any task or great idea that's brought up in a group. We all have so much going on that it's easy to assume that just because everyone is "aware", then "someone" must be taking care of it. Are they?
[Image: I got it from http://fyimusic.ca/wp-content/uploads/2010/08/Blaming-each-other.jpg]