Big Data, Education Policy, and the General Audience

3 min read

One of my major motivating factors in writing a book on data and education policy through the lens of inBloom is to make the details of education policy more accessible to a broader audience.

It should surprise absolutely no one that many discussions about educational issues take place among people who are deeply immersed in education or edtech, and that the people engaging in these conversations have deeply ingrained beliefs that are unlikely to change. When I talk with people outside this bubble, they express a degree of confusion and horror - confusion about what the actual issues are, and horror at what appears to be the intractability of vaguely defined yet strongly held convictions.

From watching - and participating in - many education policy discussions over the years, I'm no longer surprised when these conversations take place in an ahistorical present. This does everyone a disservice; no one wins when we don't at least acknowledge what the current situation is, or the legislative and policy choices that led us here. One large and obvious example is data collection and privacy - when inBloom came on the scene in 2011, there was an enormous outcry about governmental overreach, student privacy, and handing student data over to vendors. Yet, while these reactions all had a degree of validity, they ignored the facts: by 2011, every state had a datastore of student information; these records had been collected for years as part of federal accountability reporting; the federal government has been giving grants to states since 2005 to support building these datastores; and many of these datastores were built by and managed by third party vendors. The furor over what inBloom might do could just as easily been a furor over what every state in the country was already doing - and had been doing for years, and are continuing to do in inBloom's absence.

The issues discussed as part of education policy discussions are complex, but they're not as complicated as the passions that shape the conversations. inBloom provides an ideal lens for examining education policy, and the role of educational technology. By looking at inBloom, we quickly run into:

  • data use,
  • parental involvement,
  • student privacy,
  • state and federal data collection,
  • accountability reporting,
  • equity,
  • issues of race and socioeconomic status,
  • appropriate technology use in schools,
  • Big Data,
  • the role of the wealthy and powerful in shaping education policy,
  • data security,
  • the Common Core standards, and
  • what it means to learn in the era of a real "permanent record."

To be clear, the above list is by no means complete.

We need more people getting involved in the conversations about education. We might not all agree - and I would even say that universal agreement is unlikely, and probably a sign that we're glossing over the details. In looking at the subject of inBloom, we're really looking at a primer on education policy, and how the conversations have evolved over the last three years. My book is intended as a starting point for getting more people involved in the conversation, and for providing current participants with more background on how we arrived at the conditions of the present.

, , ,

What We Talk About When We Talk About Data

4 min read

One of my goals in writing a book looking at how education policy and privacy decisions evolved over the last three years is to examine and clarify the different potential meanings of data within education.

When we talk about data, we often skip the specifics. When it comes to discussing issues and concerns related to data collection and privacy, a lack of specificity at the outset leads to confusion and miscommunication as the conversations progress. Within education, "data" means many things.

This Might Be What We Talk About

When we talk about data, are we talking about the data that is required for school report cards, as required by federal law? Are we talking about data that supports federal accountability reporting? And of that data, how much - and what information, exactly - is stored in state-level longitudinal databases? How does this compare to school-level student information systems, and district-level portals?

Outside of the data required by law for accountability, there are other commonly used practices and applications in schools that result in both students and teachers creating data trails. Many of these services are sold to schools by vendors, and the data generated by their use can be stored in indeterminate locations, accessible by indeterminate partners and affiliates. A short, incomplete list includes:

  • Vendors that support school services, like cafeteria and bus routes;
  • Vendors that provide productivity software - everything from Google Apps, Microsoft 365, Adobe, and other general use software;
  • Vendors that maintain hardware at the school, district, state, and federal level;
  • Vendors selling mobile devices, like iPads, Android-based devices, Chromebooks, tablets, etc;
  • Apps used on mobile devices (generally bought from marketplaces like Apple's App store, Google Play, etc);
  • Vendors that sell curriculum or other resources, like Discovery Education, Pearson, McGraw Hill, Macmillan, etc;
  • Middleware or data warehouse providers - systems like Clever, or services that provide single sign on/integration between multiple applications;
  • Student Information Systems - Powerschool, Infinite Campus, etc.;
  • IEP authoring software;
  • LMS or adaptive learning platforms, from Moodle to BrainHoney to Khan Academy to iReady to Edmodo.

Within the various types of data - ranging from time an app was accessed, to links clicked, to the actual physical location of the learner, there are additional concerns: what's covered under FERPA, COPPA, or PPRA? What is the best way for schools and districts to review data collection and use within these apps and services? How should these decisions be communicated to students, teachers, and parents? Additionally, when we talk about data, we often cite the benefits of anonymized data sets without considering any potential for re-identification.

This Is Always The Subject

But really, whenever we talk about data in education, we are talking about people watching other people doing things - and this is where data collection and analysis ties in with privacy, equity, and power. What learners are more observed than others? What groups of people get to interrogate the "how" and "why" of data collection? What populations are sold the idea that constant observation through data collection is being done for their benefit? When and how do people get to review information that has been collected about them? Who gets to opt out of being observed, in whole or in part? Who determines what gets collected? Who determines how long the data is retained?

To be clear, intelligent use of reliable data can allow us to do important things. For example, data lets us quantify that black preschoolers get suspended at alarmingly disproportionate rates. Used well, data can be used to get support to students before small issues become large issues (although this line of thought also assumes schools are adequately funded, and have ample resources and support staff).

But it bears asking: is privacy part of the price of a public education? Attending a charter school like Rocketship Academy, attending a school that uses Google Apps or Office 365, enrolling at a school that has an iPad program, or stores data in Schoolnet, or uses Edmodo, or connects apps via Clever, or warehouses data in Schoolzilla, or uses Khan Academy - any of these situations require that the process of a student's learning is collected and archived as a condition of learning. What does privacy look like in this situation? Who is given a choice about how privacy can be maintained?

When we talk about data, we rapidly bump into questions of who has the right to use data, and when people have the right to avoid observation. In this way, data collection and privacy become tightly related to personal and community empowerment.

Over the last few years, these issues have become more visible. If you want to support work that helps clarify these issues, and makes them accessible to people outside tech and education circles, please consider supporting the project.

, , ,

inBloom Text

4 min read

On August 3, 2011, Vicki Phillips of the Gates Foundation announced the launch of the Shared Learning Collaborative. She compared the project to "a huge app store - just for teachers - with the Netflix and Facebook capabilities we love the most." She described the work in highly auspicious terms:

There are few times in life when we are fortunate enough to be part of something amazing. I believe this is one of those times, and I am especially excited because the “something amazing” is being led by states.

The Shared Learning Collaborative (or SLC) started with $87,000,000.00 from the Gates Foundation and an additional $3,000,000.00 from the Carnegie Corporation. When the SLC was announced, http://slcedu.org/states-districts/pilot-districts">nine states - Colorado, Illinois, Massachusetts, New York, North Carolina, Delaware, Georgia, Kentucky, and Louisiana - had agreed or were in talks to partner with the new organization. The software built by the SLC promised to simplify data collection, and to http://slcedu.org/content/marketplace/opportunites/content-providers">streamline the process of districts and states using student data with vendors to build educational tools.

In February 2013, the Shared Learning Collaborative incorporated as the non-profit inBloom. The organization had a https://www.inbloom.org/providers">raft of industry partners on board. Big data and education technology were hot. inBloom had a formal launch party at South By Southwest. Things looked rosy. (image from http://www.edlio.com/blog/2013/03/sxswedu-2013/ )

Fast forward a year, to April 22, 2014: inBloom announced that they were winding down their organization. In 14 months, all of their customers had backed out.

To understand the forces leading to the failure of inBloom is to understand the passions and arguments that punctuate current education policy discussions. inBloom can be understood as a technology, as a business strategy, and as a philosophical vision about what some people think education should be.

The story of inBloom - the concept, the launch, the hype, the crash - ties in with the story of educational technology and education activism. In 2011, four days before the launch of inBloom, thousands of teachers marched in Washington, DC, to protest the growing influence of corporations and billionaires in shaping education policy. On the tech front, the iPad2 was poised to revolutionize education. Sal Khan was either a messiah or a demolitionist, but both options were good. Six weeks after the SLC launched, Secretary of Education Arne Duncan announced federal waivers giving states flexibility in meeting the terms of No Child Left Behind.

On paper, the demise of inBloom appeared unthinkable. The organization had close to 100 million dollars. They were backed by the Gates Foundation, and their development partners included a Rupert Murdoch-owned company run by the politically seasoned Joel Klein. The software inBloom was building - according to some - promised to simplify or eliminate longstanding pain points felt by districts. Supporters of inBloom cited the inefficiency of current data systems and the potential of individualized learning; detractors voiced strong concerns over privacy, and derided inBloom as another tool to replace teachers with technology in the name of educational reform.

A close look at inBloom leads us directly to issues around data use, parental involvement, student privacy, state and federal data collection, accountability reporting, equity, issues of race and socioeconomic status, Big Data, and the role of the wealthy and powerful in shaping education policy - to name a few. Understanding why inBloom failed can help us make headway on longstanding differences - differences in policy directions, questions related to teacher autonomy, questions related to student learning, and social issues that affect how people learn. These issues existed before inBloom, and will continue to persist in its absence. Regardless of how one feels about inBloom, their presence elevated the visibility of concerns that had been primarily the domain of tech geeks and policy wonks. While inBloom is a story about the failure of an educational technology company, the arc of inBloom encompasses far more than just technology.

With your backing, I can write this book. While I have already written about inBloom, student rights, and education policy, telling a more complete story requires additional time and research. Writing this book requires interviews and conversations with people across the ideological spectrum. I know people who are ardent supporters of inBloom, I know people who have spent hundreds of hours organizing in opposition to inBloom, and I want to talk with as many people as possible. Including diverse viewpoints - and representing them fairly - is a key component to the success of the book.

Thank you for backing this project, or considering backing this project.

Defining The Change We Want

2 min read

In talking about education, it's very easy to get bogged down in the rabbit holes of policy debates, who supports what and how fervently, and other details that circle around education, but aren't directly tied to education.

To break that pattern of thought, I started asking myself these questions relative to some of the work we do, related to how learning and teaching environments are created and sustained:

  • What does an hour of learning look like? How about a day?
  • What does teaching look like, and is "teaching" even the right word to use?
  • What does school look like, and is "school" the right term to use?
  • For someone supporting learners, who do you talk with while planning?
  • For learners, who do you talk with while learning?
  • If someone asks you to explain why you are doing a specific thing, or what questions you are trying to solve, how would you respond?
  • If someone asks you to prove that it works, how would you respond?
  • How does this type of learning support people from/with different cultural backgrounds, different levels of affluence, different religious beliefs, different educational goals, different racial identity, LGBTQ populations, special learning needs, different physical abilities, and rural or urban settings?
  • If you were setting up this program for 30 people, what would you want to set up? Would it differ if the setup was for 300, or 3000, or 30,000?
  • If you were stepping foot as a learner into this program, what would you want to do?

As you think about this, use action-oriented language whenever possible. What would people be doing? What types of interactions and experiences shape the day? How do these interactions unfold over a week? A month?

Avoid using any of the language that roils and derails ongoing discussions. Avoid references (pro or con) to the Common Core, testing, etc, etc. Keep the conversation grounded in what people do, and avoid buzzwords and jargon.

While I recognize that there are multiple systems that approach learning in this way, avoid adopting the vernacular of any one system.

In the interest of actually defining the change we want, instead of defining the things we oppose, how can we describe the ideal type of learning we'd like to see, experience, and support?

,

Thoughts on "This Is Not A Test" from José Vilson

5 min read

I've spent the last few weeks reading and re-reading This Is Not A Test by José Vilson. In my past life, as an English teacher, I would churn out responses like no one's business. It was a simple pattern - read --> cogitate --> time and caffeine --> pronto! Occasionally, though, the pattern wouldn't work - with books where I got stuck on the corners - books where I kept returning because there were pieces of the conversation (and yes, I see all text as an invitation to a conversation) that I missed. These books - the ones that keep calling you back, the ones that push you - are, over time, the most enjoyable.

This Is Not A Test defies easy categorization - the text is equal parts essay, coming of age story, history lesson, and primer in what it means to teach - and each facet is equally necessary. Reading through the text, I kept returning to the idea that our concept of "normal" derives from what we know, and that we all - turle-like - carry our own "normal."

Vilson describes experiences as a student, a learner, an aspiring teacher, a working teacher, and a teacher-advocate. Often, people describe transitions as a journey from place to place - arriving at one place means leaving another. But as Vilson describes the various stages in his life to date, his transitions are best defined with an "and" - as he moves from student to teacher to advocate, he retains key elements from all these experiences.

In the beginning of the text, he reflects on the his elementary school experience.

As an adult, I once looked in the paper and found PS 140 (the school Vilson attended) on the list of persistently dangerous schools in New York State as of 2007. Even after it was removed from the list in 2009, I couldn’t believe it. In the eighties and nineties I had always felt it was safe and believed I was getting the best education possible.

As I re-read this description, I wondered how kids feel if or when they look at the current school report cards, currently required in all states. What does it mean for a kid going to school now to be able to look and see that the place they go to learn is rated sub-par by the government? Do learners benefit from being told that their environment is sub-par? Who does benefit from this? And for the student, their learning, their school, their normal experience, is what they know.

The text covers Vilson's transition and growth through his academic career, and the non-school experiences that occurred in parallel. These details loop around each other, sometimes connecting in abrupt ways. Some of the strongest writing in the text occur when Vilson addresses issues of race and identity.

Thus, in our school, any discussion about who was “nice” in ball had a racial component. The ball teams we saw on TV were predominantly Black with white coaches. Xavier’s basketball team looked like the coaches didn’t want to let go of their Hoosiers fantasies.

And it's in the details - often dropped in as asides - that the stories unfold. By reflecting on his transitions from student to teacher to advocate, Vilson shows us that education plays out over time. For those who have never spent time in the classroom, it's worth remembering that learning - occupying space in the state of being called "student" - is a process of becoming. The person struggling with subject X in your classroom for Y minutes a day has come from somewhere, and is going to somewhere, and the time you get to share with them may or may not be equally meaningful to all involved. Understanding what passes as "normal" is critical.

The street has taught us not to “snitch” - not because we want to protect the offenders, but because the deaths of people like Amadou Diallo show that even our supposed protectors have something against us.

This is normal.

Understanding the role race, class, and inequity play in defining the career of teaching and the current state of education is an essential element of understanding how to make things better for our students. Vilson's book helps build that foundation, tying together his lived experience, and the experience of his students, against the backdrop of what's currently required in schools.

I survey the students: most of them completed the test about twenty minutes ago. Some heads rest on their graphite-scuffed desks, snores blowing against pencils that drop to the floor. The creatives use the backs of their tests as canvases while the drummer from the school band taps his pencil against the desk to the tune of LMFAO’s “Party Rock Anthem”

In descriptions like this, against the backdrop of testing, we see students getting what they need, in the cracks between the requirements set in front of them. What would an assessment look like that evaluated the doodles left by students on assessment materials? By including details like this - the "not-test" part of the test - we see students learning, whether we plan for it or not. Our role in that learning is up for grabs. But the constancy of that learning - the never ending processing of experience - is not.

This Is Not A Test is available from Haymarket Books. If you buy a copy by Saturday, May 10, 2014 (the end of Teacher Appreciation Week) you can get 30% off by using the code "NOTATEST" at checkout.

,

Accountability, Over 18 Holes

2 min read

As is now painfully obvious, Oregon wasted milions of taxpayer dollars on the failed Cover Oregon site. A sizeable amount of these millions went to Oracle, the main contractor on this failed build that didn't sign up a single person for health coverage.

President Obama showed his outrage at this incompentence and waste of taxpayer money by playing a round of golf on Oracle CEO Larry Ellison's private golf course this February. Nothing says "I'm outraged!" like leaving an extra divot on the green.

Let's contrast this with the position of the Federal Government on teachers who are not performing:

But, yes, I do believe at the end of the day if a teacher is just not making it and, despite help, despite support, despite mentoring, is not improving, I think we owe it to our children to make a change there. And quite frankly, it’s better for the teacher to find another line of work where they can be more successful.

Finally, I have this straight. If a software company bilks a state out of millions of dollars and delivers nothing, that's okay - provided we can get 18 holes out of it. But if a teacher doesn't raise test scores, they're out. It's taken me a while, but I think I understand accountability.

, ,

Federal Brinksmanship: Secretary Duncan Pulls Washington's Waiver

2 min read

On April 24th, Washington State became the first state in the country lo lose its No Child Left Behind (or NCLB) waiver. The state lost the waiver because the Washington State legislature refused to tie teacher evaluations to student scores on standardized tests.

The letter, and the attached conditions, make for an interesting read. The implications also point to additional showdowns in the near future. The adequate yearly progress goals of NCLB, broadly criticized as unrealistic, will result in many schools that have been considered successful to become failures overnight. Randy Dorn, Washington State superintendent, describes the situation as follows:

"You have to write the letter to everyone that you're a failing school," he says. "You're supposed to have 100 percent of students at proficient grade level. If you have one kid that's not proficient, you've got to send out the letter."

He guesses 90 percent of Washington state schools will have to send out that letter this summer.

So, in the next few months, an enormous majority of parents will receive a letter stating that their kids' school is failing not because of anything that happened within the school, but because of the attitude of the Federal Government about standardized tests.

The terms of Washington State losing its waiver is a huge boon for the opt out movement. With 90% of schools being called failures out of the gate, schools have no motivation to comply with standardized testing requirements. The fact that a school gets defined as failing due to political posturing helps reinforce the view that school ratings are both arbitrary and politically motivated. Schools have nothing to lose by refusing to test - and weeks of instructional time and flexibility to gain.

And, of course, it should surprise no one that the schools with the least money will be affected first. Or, to put it another way, because of how federal education policy is being implemented, the schools with the fewest resources will feel the hit first. If unions - and schools with more resources - step up and take steps to minimize the impacts of the lost waiver, they will have an opportunity to show how they put kids - and equity - first. If they fail to do this, then unions will have demonstrated that they are in it for the politics first.

, ,

A Short And Incomplete List Of Actions That Would Improve Privacy

3 min read

In conversations about privacy in schools, it's easy to get mired in the details of what isn't working. The incomplete list below provides some starting points for making things better. This list isn't comprehensive by any means, but it's intended as a starting point for people looking to dig deeper. In an ideal world, we could round up funding to bring together a team of people for 2 two day work sessions (a total of four days) to begin working through this list. All work would be released under a Creative Commons Attribution Share-Alike license.

  1. For non-lawyers, finding and accessing the text of federal privacy laws can be a challenge. The ideal would be to create online versions of FERPA, PPRA, and COPPA that are collected in a single location, and are linkable at the paragraph (or subpoint) level. This would allow people to search, read, and link to specific sections.
  2. In December, 2013, the Fordham Center on Law and Information Policy released a study on privacy and cloud computing in public schools within the US. This report included a "Document Coding Checklist," included in the study as Appendix B (pdf download). The background knowledge and process required to use this matrix effectively could be documented. If step 1, above, is in place, we could link to the specific sections of privacy law addressed by the matrix.
  3. With the matrix defined in step 2, above, we evaluate publicly available terms of service and privacy policies of web sites and services marketed to schools.
  4. In addition to the matrix, we could use the rating criteria shared at http://tosdr.org to evaluate and document terms of service and privacy policies. These reviews could then be submitted to http://tosdr.org.
  5. Evaluate data collection and retention policies of content filtering companies. Given that both schools and libraries getting E-rate money are required to use content filters, we should have full disclosure of any data collected by filtering companies, how they use it, how they share it, and how long they retain it. Filtering companies - along with apps installed on mobile devices - are a great example of data black holes, where the terms of use and privacy policies are opaque and unclear.
  6. Create a data primer that breaks down the difference between personally identifiable information, other data that isn't tied directly to an identity but still can be used to infer a person's identity, displaying ads, using data to tune algorithms, and processing data but not showing ads against it. This data primer could also be used to help provide background information for the evaluation tools described in steps 2 and 4, above.
  7. Document and define what successful contract documentation looks like; ie, save copies of click-wrapped terms of service, etc. This would be a recommended organizational structure that districts could apply to ensure that they are tracking their contracts/obligations accurately.

As mentioned above, this list is incomplete. Please, feel free to add to it in the comments, or give me suggestions on Twitter.

In the absence of policy change around data collection at the federal or state level, and/or improvement from tech companies on respecting the rights of students and schools, the steps outlined here would empower school and district staff to make more precise demands - and more informed choices - when negotiating the terms under which information is handled. If the resources described in this post were created and available under a Creative Commons license, districts and schools could benefit from these resources at no cost.

,

New York Pulls Out Of inBloom. Ho Hum.

6 min read

NOTE: An earlier version of this post included language from a draft version of a NY Assembly bill. Thanks to Paige Kowalski for pointing this out. END NOTE

Earlier this week, New York State pulled out of inBloom. While this has been hailed by some as a victory for privacy, it's worth noting that the data points that are collected - and have been collected for the last several years - haven't changed. The federal accountability requirements driving much of the data collection that currently occurs haven't changed. In New York, the withdrawal from inBloom means that districts are right back where they started: managing data collection and accountability reporting on their own. And it's worth noting here that all of the student data that was going to be stored in inBloom is already collected and stored in a statewide data repository, and that none of these conversations address data collection taking place via other apps and services.

Districts deserve the ability to control where their data is stored, what tools are used to store and manage it, and where the servers containing that data are located. While many districts do not appear to be doing a particularly effective job of exercising this control at present, that doesn't mean that districts should just cede this responsibility outright. New York's approach to the inBloom rollout was top down and paternalistic. inBloom, for it's part, failed to respond to and counter the narrative that the entire purpose of inBloom was to collect as much data as possible, and then sell that data to marketers, advertisers, and other corporate ne'er do wells.

New York State backing out of inBloom is less a victory for actual privacy than it is a change in software procurement. As discussed above, the data collected by schools has not changed, and the fact that it is stored in a single statewide source has not changed. The software used to store it, however has changed. It's comparable to a district banning the use of Microsoft Word - it doesn't mean that people won't create text documents; they'll just use different software to do their work.

The majority of the coverage - and most of the ongoing discussions about data collection and privacy - ignores the reality that data collection and management is a zero sum game. There are a limited number of vendors that can manage state and district level data storage, so not using one option means choosing another. As noted earlier in the post, New York State's decision to pull out of inBloom isn't a shift in data collection policy, it's a shift in what software and tools are provided to districts. As they have done in the past, districts are now outsourcing data storage to vendors, or maintaining solutions in-house. In New York, removing inBloom at the state level creates opportunities for the existing players - Pearson, eScholar, Infinite Campus, Agilx, Clever, etc - to sell directly to districts and regional educational agencies. So, the push to move away from inBloom to keep student data out of the hands of vendors creates opportunities for student data to flow directly to other vendors. Outsourcing data handling to vendors also requires adequate contracts to safeguard data, which many districts fail to do. And, even if districts get the contracting right, and/or maintain their own service, data compromises are, unfortunately, commonplace - as of March 27, 2014, over 725 data breaches have been reported in K12 and Higher Ed since April, 2005. Many of these breaches have occurred because of human error or interference, not because of hacking.

To be clear: the approach inBloom and New York took was incredibly flawed. But, unlike every other option that exists, inBloom provides an open source option that could have been adopted independently by districts, or regional service providers, or state educational agencies. It's possible to use inBloom - the software - without interacting with inBloom, the organization. inBloom provided a real alternative that could be used to break the dependency on vendors managing and storing student data. The fact that so few people understand the implications of this is probably the single biggest failure of inBloom, the organization.

Looking at this nationally, New York pulling out of inBloom is only good news for the other players in the space. inBloom had the potential to shift the dynamic in how states and districts managed their data. If inBloom had focused on supporting states and districts setting up their own hardware - rather than setting up a hosted solution where inBloom managed the servers - we might be having a different conversation now. However, with New York out of the picture, inBloom is pretty heavily tarnished, which helps the pre-existing players continue to expand their control over the market. One of the major concerns cited about using inBloom was that it would allow student data to be used to develop adaptive learning. However, if a student is using an electronic text from a textbook publisher, this is likely already happening. Pearson's partnership with Knewton shows exactly what this looks like. The move away from inBloom is a move to "protect" students from what is already happening.

But really, all of this is misguided. The lens of "privacy" is at least partially broken, as it relegates students to an observed object in system where they have limited input. Our considerations of privacy will remain divorced from learning (remember learning? It's why we do this whole school thing) until we recognize and acknowledge that students (or their parents) need to be the ones to control and reflect on any information that is collected about learning. Now, the emphasis is on building systems that collect data on students, to push content at them. We're not seeing much work on systems that empower students to reflect on their learning over time, and selectively share that information. Our data collection policies and habits reflect the reality that our educational system is more outcome-centered than student-centered. If we corrected this misplaced emphasis, we could do a better job educating all children, and improve privacy concerns along the way.

, , ,

GoNoodle, HealthTeacher, Privacy, and the Long Game

8 min read

Last night, I went to the Portland Public Schools Board meeting. Shortly before that meeting, while perusing the meeting materials, I learned that the meeting would feature a demo of a service called "GoNoodle."

It was around 5 PM when I read about GoNoodle. I was hungry. I like noodles, generally. My curiosity had been piqued.

Company History and Pivots

GoNoodle is part of HealthTeacher. HealthTeacher evolved and pivoted from VerusMed, which became ConnectivHealth. During these transitions, the companies received several rounds of venture capital (VC) funding. A high level chronology is laid out below:

The Formula

A quick and dirty search shows a common formula: approach a community, partner with a local hospital, and have local health care systems defray the cost of giving the service free to the district.

Using this business strategy allows a VC funded company to have non-profit organizations pay for curriculum development, R and D, and to have it's brand inserted into health education within the pubic school system. An incomplete list includes schools and districts in Arkansas, Minnesota, Idaho, Georgia, Arizona, New York City, and Miami.

Portland's deal with HealthTeacher sounds pretty comparable to the deals they struck with other districts: local healthcare systems pay for access and curriculum development, so the school district doesn't need to show any cost for the service. However, when we look at the terms of service later in this document, we'll revisit the cost of "free". And it's worth noting that, in Portland, local health systems are paying $600,000.00 to support this program.

This formula helped bootstrap the development of the HealthTeacher's "learning" game.

As did this partnership.

And this one.

From reading through the press releases, and cross-referencing them against the VC funding announcements, it sounds like HealthTeacher has figured out a way to have private foundations give money to a VC funded company to support a branded app getting pushed into public schools to push out health teachers and a locally relevant health curriculum.

Health or Test Prep. Or, Health AND Test Prep

The recent language from HealthTeacher materials suggests a pivot from working with health curriculum into trying to position the company as a means toward improving scores on standardized tests. The material prepared for the Portland School Board meeting emphasized "Common Core alignment," and this lesson brings the point home more succinctly than I ever could.

The lesson includes reminders like this:

Practicing healthy habits can help you do better on standardized tests.

This nugget explains how to make teaching to the test more effective:

Repeat this each day leading up to the standardized test

  • Since teachers are encouraged to give students practice tests leading up to the actual test day, use this exercise prior to the practice test.
  • Ask students how they felt about their success on the practice test after they exercised.

Given that real, actual exercise and activity would cut into valuable test prep time, we can use HealthTeacher to fake our way through the exercise!

Privacy?

So far, this has been a pretty run of the mill edtech story, complete with VC Funding, multiple rebrandings, and marketing hype outstripping product reality. But where it really gets interesting is in the terms of service.

As we get into privacy, it's worth remembering that this service is presented to many teachers as a district vetted service brought to them free of charge due to the largesse of the local health care community.

Within that context, I would be surprised if many teachers signing up for the site read the Terms of Service to see how, by virtue of signing up for the site, they give the site owners the right to do just about anything with their user information:

By submitting User Content, You also grant HealthTeacher the right, but not the obligation, to use Your biographical information, including, without limitation, Your name and geographical location in connection with broadcast, print, online, or other use or publication of Your User Content.

Additionally, HealthTeacher can change the terms whenever, to whatever:

HealthTeacher may, at any time and in its sole discretion, revise, modify, or otherwise change the terms and conditions of this Agreement. Modifications shall become effective immediately on being posted on the Site. You are responsible for regularly reviewing the terms and conditions of this Agreement and if You object to any changes Your only recourse is to terminate this Agreement and stop any use of this Site. Continued use of this Site following any such changes shall constitute Your acknowledgement, review and acceptance of and agreement to the Agreement and its modifications.

The combination of these two clauses means that HealthTeacher can use the information you provide to do just about anything. If the company is sold, your data is likely part of the sale. The only possible remedy that could fix these terms is if districts negotiate different terms for their teachers, but given that teachers need to create accounts, they could end up agreeing to the regular terms regardless.

This is where the long game comes in: VC funding dries up. Funding from health systems expires over time. Subscription models to teachers and districts require sales. But, going back to at least 2009, HealthTeacher has been collecting teacher information with few limitations as part of a district-sanctioned service. In the EdTech world, user data and usage patterns create a gift that is pretty timeless.

Disrupting Health

Seen in isolation, GoNoodle isn't an awful service. Teachers who use it say that kids seem to like it. Moving in class is good.

But taking a step back, things get less pretty. There is a serious disconnect between the hype and the reality. The implied promise of the Healthy Activity Breaks To Get Ready For Testing is that GoNoodle and HealthTeacher will increase standardized test scores. Additionally, when viewed through the lens of healthy social and emotional development, the idea of supporting standardized testing as a health activity also is ludicrous. In this light, the claims of Common Core alignment of GoNoodle and HealthTeacher materials seem equally absurd, and bring to mind Morgan Polikoff's recent study debunking claims of Common Core alignment among publishers.

But taking an additional step back, using a service like GoNoodle allows districts to make the claim that they are "teaching health across the curriculum" and "embedding healthy lifestyle choices in the classroom." The GoNoodle presenter at the PPS Board meeting used the term "deskside activities" to describe the exercises. And, the optics are good: it looks good to see a room full of kids out of their desks, doing something that looks like moving. But we shouldn't kid ourselves that this is the same, or as good as, a health teacher, a PE teacher, or actual extended exercise time outside of the classroom. A video on a screen showing to a room full of kids for three minutes is not the same as - and shouldn't be seen as a replacement for - a caring, trained adult teaching a full length class. Given that PE was recently on the chopping block, it would be good to see investment in sustainable health and physical activity programs.

Open Educational Resources Would Fix This

From the high-level overview of the agreement (pg. 4), it looks like two local health systems contributed a total of $600,000 to fund this effort. This funding includes money for curriculum development. It's unclear who will own the content after the agreement expires, or whether PPS will be able to access or modify this material free of charge after the agreement expires. It's possible that PPS rented access to beta-quality content while securing R and D funding for a VC funded company, and handed over teacher contact info and usage habits as part of the bargain.

If, however, the $600,000 had been donated to support the development and implementation of an openly licensed curriculum, everybody could benefit - in Portland, and beyond. And here, it's worth remembering that HealthTeacher has formed a collection of relationships, all working in isolation and in parallel, solving similar issues. How many more people would be able to benefit - both in the participating districts, and outside them - if Health System Foundation resources spent on building the content library of a VC funded company had gone into creating content that was openly licensed and freely available. In Oregon, the 600K donated by Dornbecher and Legacy would have had a statewide benefit. Just looking at this from the perspective of return on investment, if the same 600K could benefit kids in one city, or kids in the entire state, why think small?

And, of course, when we look at this through a social justice/equity lens, creating openly licensed materials makes even more sense. Using openly licensed materials would allow us to invest in local skills and local talent that isn't timeboxed by an external service.

, ,