Making Sound Technical Investments

7 min read

Recently technical debt has been getting more discussion. That is a good thing. Just like in the "real world" strategic debt can be useful. Historically, investing in advanced education such as college or trade school has been a sound investment. Similarly investing in a primary residence has also been a sound investment. In both scenarios we often take on an amount of debt to create opportunity that would not normally have been available.

Similarly, we invest in technologies. When we can not afford the opportunity cost up front, or an ongoing development cost, we take on technical debt. If done properly and invested appropriately this can be a wise strategic decision. On the other hand if one takes on too much debt (financial or technical) one runs the risk of defaulting.

"Default may occur if the debtor is either unwilling or unable to pay his or her debt."
Wikipedia

Managing technical debt should come down to assessing debt on two initial criteria, willingness and ability.

Willingness

First, is this a debt I am willing to pay off? Initially one might think that the answer to this should be "Yes I am willing to pay off this debt." In regards to client needs and who pays down the debt then there is a certain amount of required diligence to inform the affected parties of the implications of failure. In that case this is an ethical issue and full disclosure of risk is important. However, don't get confused around where debt is accruing, and the type of debt that is accruing.

For example, when in a research and development phase financial debt (or some other debt) is accrued while avoiding technical debt. That is, during research and development new products and/or solutions with no immediate return on that investment are explored and/or developed. In this process ongoing costs(debts) such as; salaries, and electricity are likely being payed or accruing. If assessed through an improper lens it is easy to confuse where debt(or cost) is accruing. Here I claim R&D debt is non-technical in nature because there is no obligation of using any technology researched or developed in a production environment where there would be an obligation to manage any and all technical debt accrued as part of using said technologies. If the R&D process is successful technical debt has been avoided while likely creating some other debt. Unless, of course, the total cost of R&D was payed in full. The goal is that the value created via the technology developed is enough to pay off the non-technical debt or provide enough strategic value that the risk was worth the reward. However if R&D does not produce viable technology zero technical debt has accrued with (hopefully) the added benefit of progressing domain knowledge; even if that knowledge is what doesn't work. Every time the full cost is not paid in advance a certain amount of debt of a certain type is accrued. Similarly most, if not all, technologies have ongoing costs that need to be paid over time or technological debt will accrue. These situations should be duly noted and appropriate mitigation strategies should be setup to ensure staying ahead of the accruing debt.

Willingness to pay down debt comes down to assessing and identifying what types of debt would be accrued assuming certain actions. If certain types of debts are considered more risky than others then a shift in priorities to accrue less risky debts may be necessary. Alternatively, if it is an option, pay the total cost up front. This leads us to assessing risk, one way is by assessing our ability to pay down debt.

Ability

Accurately assessing ones own ability should effect willingness to accrue debts of a certain type. For example a financial investor assumes financial risk because that's what their asset allocation (ability) is. In other words, the financial investor has enough financial capital that the risk involved in accruing financial debt is often worth the reward. Technologists on the other hand have capital in their technical ability. When a technologist's technical ability doesn't appropriately match the type of technical debt that would accrue it is necessary assess the risk associated with moving forward with a given solution that may accrue debt. This is where ego can be most harmful. Technologists investing in a new, to them at least, technology are either paying the cost up front (eg. training, research, development) or they need to be aware of the risk involved (eg. site downtime, dissatisfied customers or clients, and data corruption) if the new tech doesn't pay off. In the event that the technical investment does not pan out the technical debt has accrued and without an appropriate willingness and ability to pay down that debt it is outstanding and someone will eventually pay for that debt. The reason why ego is most harmful is because an ego that is too fragile results in missed opportunities for learning and collaboration. Learning opportunities are created by acknowledging when there is a lack of knowledge and being open to the possibility that an accepted worldview or mental map may not necessarily align with reality. Similarly if one thinks they already know something, collaboration from others is often undervalued and not sought out. The result is stagnation and lack of investment in technological capital. This affects one's ability to pay down technical debt, and limits the technologists effectiveness.

"I am out of step with present conditions. When the game is no longer played your way, it is only human to say the new approach is all wrong, bound to lead to trouble, and so on. On one point, however, I am clear. I will not abandon a previous approach whose logic I understand ( although I find it difficult to apply ) even though it may mean foregoing large, and apparently easy, profits to embrace an approach which I don't fully understand, have not practiced successfully, and which possibly could lead to substantial permanent loss of capital."
Warren Buffet

Moving forward

In either scenario (willingness and ability) the tech community is often not held accountable for the technical debt that it has created. Think of the number of "rescue projects" that exist out there or the number of essential features that are punted to "later phases" of a project. There are a myriad of reasons why these things occur but if it is due to technical debt and an inability or unwillingness to pay down that debt we as a tech community are creating a lot of outstanding debt that someone has to pay down, often via other means. This is quite similar to the financial meltdown that occurred in 2007-2008, due to credit default swaps, and more specifically due to the amount of outstanding debt. The tech community needs to start preventing additional non-strategic debt and at the same time paying down existing technical debt. We do that by assessing the type of debts and our willingness and ability to pay down those debts. But, how do we start doing that?

  • Invest in technological capital. This should help build a solid ego. Look to build an appropriate amount of breadth and depth.
  • Work on personal ability to admit not knowing.
  • Read material outside the technical community, diversity is a good thing. This helps realize that the tech community is not special, we exhibit the same patterns and problems of other communities.

In this process it is helpful to read. It is especially helpful to read topics outside one's realm of expertise, and those viewpoints contrary to one's own. A solid ego is helpful to weather the vast amount of change and the ridiculous tides of hype in the tech community. Just make sure to build a healthy ego and not hubris.

Building An Application To Simplify Software Inventory

3 min read

In an earlier blog post, we described a process that could be used by schools and districts to inventory the applications used to support teaching and learning. This inventory covered details of contracting, educational rationale for the application, and the privacy implications of the application. Much of this evaluation will be identical across schools, so it doesn't make sense for different schools to sink time into doing indentical work across the country.

Since we put that post out, we have talked a lot internally about what it would require to build that application. We have also talked with educators, administrators, privacy advocates, vendors, and parents about the idea, and have received enough feedback where we don't feel like we are missing anything obvious. To round out the application, we would want to include some information about the text of privacy policies.

Maintenance

  • Date policy reviewed
  • Date policy was updated
  • Date policy was archived
  • Policy copy - text
  • Policy copy - image

The information in this section would allow us to do a few things. First, it would allow people to see how current (or out of date) a review was. Second, if a policy had been updated after a review, that would be a flag that the review was out of date and needed a touchup. Third, the text archives would allow us to maintain a verifiable changelog of policies over time, as policies are often changed with no announcement or explanation. Fourth, maintaining a text version onsite would allow us to automatically check for changes in the policy, which would in turn alert us to the need to revisit or update a review.

When the application was done, schools or districts could pass the application a list of names, and would receive a complete dataset of reviews. As described in our earlier post, they could augment these reviews with the contracting and pedagogical rationale that was specific to their use. However, this application makes it possible for districts to research apps more quickly, and document their technology use more thoroughly.

The project would be built on the following assumptions:

  • Code that runs the site would be open source;
  • Data that is stored in the site would be openly licensed;
  • Compiling the reviews would be the largest initial hurdle. Based on conversations I have had with various schools and districts, though, there is no shortage of people who need this information, and are tackling it on their own. Ideally, we would work with interested partners to help facilitate the review process;
  • Over time, maintaining the reviews will require additional time from people reviewing updated terms and new apps, and people reviewing the reviews;
  • Over time, maintaining the software will require ongoing outreach to make sure that we are measuring things that answer questions people care about (or should care about);
  • Maintaining project infrastructure will also be an ongoing expense.

If you have any ideas/feedback on this, please, let us know.

, ,

Taking Inventory of the Tech Schools Use

10 min read

This post was originally published at Educating Modern Learners.

Anyone working in or around education technology in the last two decades has likely experienced the tension between district-level technology policies and classroom-level technology implementation.

In very general terms, district-level decisions tend to minimize risk, often at the expense of teacher autonomy and creativity. On the other end of the spectrum, classroom-level implementations – where a teacher brings in an application outside of district- or school-level approval processes – can get teachers the resources they want to use with less hassle. However, over time, classroom-level implementations that sidestep school- and district-level review often result in a patchwork of applications, with little or no review for privacy, security, or effectiveness. Complicating matters even further, district-level reviews and contracting processes aren’t always adequate – and even if they are, district policies are often not explained in terms that make sense or are relevant to teachers.

Disconnects Within Educational Systems

The disconnect between classroom needs and district needs increases when district review schedules do not align with classroom schedules. Because of this longstanding and inherent tension between a district’s need for stability and a classroom teacher’s need for flexible and timely adaptation, we create a situation where districts are not fully informed of software use at the school level, and district security needs are not understood at the classroom level. The fallout from broken processes often results in students, parents, teachers, school administrators, and district staff all having an incomplete and inaccurate vision of the technology used while learning.

The fallout from broken processes often results in students, parents, teachers, school administrators, and district staff all having an incomplete and inaccurate vision of the technology used while learning.

The good news is that this broken communication can be fixed with a simple inventory, and taking inventory of software used to support teaching and learning within a school is not rocket science. It requires time, and the process of documenting software used to support teaching and learning will almost certainly uncover shortcuts in the contracting and vetting process, but we can’t continue to allow the mistakes and habits of the past to shape the learning environments of the present.

Inventory To The Rescue

In this post, we will create a replicable process that can be used by students, teachers, school administrators, and/or district staff to document the technology used in your learning environments. One of the barriers to implementing pedagogically sound technology programs is a clear sense of what is being used, and why. An inventory, evaluation, and privacy review of existing technology needs to be part of how we implement software used in learning. The point of documenting software and technology currently in use is not to be retroactively punitive

In all likelihood, there will be holes in what can be documented initially at both the school and district level. If people at the school level are fully forthright, there will almost certainly be apps used within schools that violate district policy – and depending on the context, that could be attributable to district red tape, school-level intransigence, and/or teachers being under pressure to get their work done. If people at the district level are fully forthright, the inventory will reveal shortcomings in both the contracting and review process. However, the point of documenting software and technology currently in use is not to be retroactively punitive, and “success” does not require all schools and teachers to fall in line with district policies. The goal here is to establish a baseline, and learn how to do better – including questions to ask ourselves, our vendors, and our students – as we move forward. “Doing better” requires changes in district policies, school implementation, teacher practice, and vendor policies. All stakeholders have a role to play.

The process of taking a complete inventory will highlight places where all stakeholders need to improve. School and district staff need to tighten up contracting processes, and do a more thorough job evaluating software and systems for privacy and security. Teachers need to triage applications for privacy and effectiveness. Vendors need to clean up their privacy policies and terms of service and stand fully behind their product, and ensure learners that their work today is not getting fed to a data broker tomorrow – and teachers, students, parents, and administrators need to demand responsible and safe behavior from vendors.

Steal This Process!

The core of any inventory system starts with a list. To jumpstart this process, we created a Google Spreadsheet that you can copy and modify for your local use. The structure of this spreadsheet could also be starting point for a more structured database.

The process of taking inventory includes four steps:

  • General information – a list of software or services, with contracting information;
  • Purpose: What Does It Do – a description of how the software or service supports learning or administrative needs;
  • How: Types of Records, and Data Collected – a description of the data collected by the software;
  • Privacy: How Is Data Protected (or Not Protected) – an overview of basic privacy details

General Information

  • Name: Name of Application
  • Web Site: Web site of the company
  • Authorized By: Who brings in the application, or authorizes its use? (District/School/Teacher/Other)
  • Contract: Does the application require a contract to use?
  • Contract Location: If yes, where is the contract?
  • Contract Duration: What is the duration (start and stop dates) of the contract?

Purpose: What Does It Do

This section summarizes what the app does, and why it is useful or effective.

  • Description: what does the application do, and/or how does it support learning? Is the application used/supplied by the district to manage student, parent, and teacher data? Example applications here could include a gradebook, a student information system, a system designed to manage IEPs, systems designed to support communications about snowdays, etc. Is the application used to support learning? Examples here range from a district-supplied textbook from Pearson to a schoolwide use of IXL to a math app or a music app used by an individual teacher.
  • Access: How do students access this application? Is the application a web site available online, a program that is downloaded, an iPad or tablet app, a Chromebook app, or any of the above?
  • Indicators: what indicators show that the app is effective, or supports the goals it aims to achieve?

How: Types of Records and Data Created

This section provides an overview of data collected by the app, and where the data is stored. It is likely that some vendors will not support or share some of the information outlined in this section. If a vendor does not support a feature or describe their data process, the column can be marked “unknown” or “unsupported.”

Also, this section contains two questions related to the Family Educational Rights and Privacy Act, or FERPA. This only applies to the United States; if you are outside the US, omit these questions and delete these columns from the spreadsheet.

  • Data Stored: What data is collected and stored by a learning application? This field can be a link to a detailed data specification, or a general list of data points that can often be found in privacy policies.
  • FERPA: Does the app create educational records as defined by FERPA? It’s worth noting that many apps will collect data that is considered an educational record under FERPA, alongside data that is not considered an educational record. The data that is not part of an educational record would therefore be governed by a vendor’s terms of service. The point here is to get a sense of what the legal obligations are with respect to the data collected in the application. The US Department of Education provides some solid resources around FERPA.
  • Other Data: Does the app collect data that is not considered an educational record under FERPA?
  • Student Review: How can students and parents review, modify, correct, or delete data collected by the application?
  • Storage: Where is data collected by the app stored? Is it on a local server controlled by the school or district, on a server controlled by the vendor, or in another form of remote storage?
  • https: does the app use https at all times? In this doc we try and avoid absolutes, but if an app collects data and is not using https it should not be used.
  • Security Measures: how is data protected? Many apps contain some details about this in their terms of service of privacy policies.

Privacy: How Is Data Protected (or Not Protected)

This section highlights some elements of how vendors will use or transfer data, as defined in their privacy policies and terms of service. To complete this section of the inventory, you will need to read and review the terms of service and privacy policies of software and services. See here for tips on triaging privacy policies and terms of service.

  • Privacy Policy: What privacy policies govern use of the application? Link to the policy.
  • Terms of Service: What terms of service govern the use of the application? Link to the terms.
  • Additional Terms: Are there additional terms or conditions that govern how the application can be used? Link to any applicable terms or policies.
  • Opt Out: How can students and parents opt out of using a specific application?
  • Affiliates: Do the privacy policies and terms of service allow for data to be transferred to partners or affiliates?
  • Business Transfer: Do the Privacy Policies and Terms of Service allow for the sale or transfer of data in case of an acquisition, merger, sale, or bankruptcy? Most apps currently allow this, and this is an area where vendors can improve their current practice. The effect of allowing sales in case of merger or bankruptcy means that we can’t predict where data collected in an educational setting will end up, or how our student’s data will be used over time.
  • Cancellation: If the teacher, school, or district ends the contract, does all school/district data get deleted?
  • Data Sunset: Does the vendor have data sunsets (a period of time after which user data will be permanently deleted)?
  • Portability: How can parents or students download data collected and stored by the application?
  • Parent/Student Deletion: How can a student or parent fully delete their information from the application?
  • Changes w/o Consult: Can the vendor change the terms without consulting users?

Closing

As mentioned earlier, the spreadsheet and the process described in this writeup are intended for you to take them and use them. Modify them as needed. If there are things you feel should be added here, please let us know.

Once the inventory has been completed, the list can be made public so school communities have a clear sense of what technology is used, and the privacy protections in place with each service. Getting the details documented lets us start the conversation from an informed place. We can’t build on or improve current practice without a clear sense of what current practice looks like.

, ,

Scale

1 min read

Adopting openly licensed resources is arguably the most complicated part of the process.

With this in mind, I get the sense that, when we talk about scale, we are getting it wrong. In general, conversations about using OER at scale focus more on high levels of adoption of a relatively smaller set of resources. In this context, "scale" means hundreds of thousands or millions of adoptions of hundreds of resources.

This is attributable in part to the work required to adopt a text, and the semi-porous silos used to author and distribute this work. If we did a better job stripping down openly licensed materials to their component parts, we could rethink our conceptions of scale. Reducing the amount of work required to adopt OER would allow for more flexible remixes from more varied sources.

If we could rethink and redefine "scale" as tens of thousands of adoptions of tens of thousands of resources, we could create an open ecosystem that met people where they are at, and provided them the content they needed, when the needed it, in the format they required.

, , ,

Semi-porous Silos

3 min read

Over the years, we have seen a slow but gradual shift from fully closed content silos to content repositories or sources of information that have made some initial steps toward being more open. However, even the best of these silos are only semi-porous. They allow information and data to leak out via API calls, xml formats, LTI, SCORM, ePub - all the Frankensteins of interoperability - but these leaks retain the bedrock assumptions upon which the data was built, or published, or distributed.

And this is not a bad thing - content needs to be written for a purpose, and semi-porous is light years ahead of fully closed. But, embedded assumptions get in the way of reuse. Embedded assumptions - in the form of css that supports a visual effect in one web site, in the form of a learning objective that is not universal, in the form of semantic markup that might not be relevant in different uses - create a nest of cruft that needs to be removed or reworked if content is going to be modified, adopted, or remixed in a new environment.

If the process of cleaning up content for reuse and adoption was the same across platforms, we'd be having a different conversation. However, the cleanup required to adopt content varies between systems, and can even vary based on different authoring methods within systems. For example, some older content might use multiple methods to embed videos. Most openly licensed content has inline css in content that make no sense outside the original system. As a result of these and other foibles, the cleanup process varies widely. Adopting content is an unpredictable combination of undoing assumptions, redoing some sections, and - in some sections - starting from scratch and authoring something new.

And for each piece of adopted content, the amount of undoing, redoing, and new work will vary. Every. Single. Time.

The solution here is a sane starting point, as devoid of assumptions as possible. If openly licensed content was broadly available as a collection of text, with related binaries and links, we could start on a more even foundation. When we think of the elements within a page - including the assumptions that get added to the content to make it more useful within a specific context - as decoupled elements that can be readily reassembled, we eliminate the need to discover what we will need to undo. We also eliminate the guesswork around what we will need to edit, and what we build from scratch.

The process of adopting openly licensed content is really a process of ownership and responsibility. The person or organization adopting the material actively works with it, shapes it, and makes it their own. Right now, though, our toolkits interfere with that process. We have done some work on solving this problem over the years as part of our internal development roadmap. Our internal project name for this is "Sally" and the project has taken multiple forms as our thinking on the barriers to OER adoption have evolved. But for the last few years, we have been circling closer toward a tool that strips away the assumptions that leak out of semi-porous silos.

,

Portland Public Schools and Privacy Practices of the School Climate Survey

4 min read

UPDATE, February 5, 1015. The privacy policy for this survey has been updated. Details available here. END UPDATE

On January 20th, Portland Public Schools released their School Climate survey. The goals of the survey are great - the district is making a focused effort to reach out to a broad range of parents with kids in Portland Public Schools. However, there are some issues with the survey and the associated privacy policies.

The problems start at the point of account creation. While the registration form states that personal info will not be tied to responses, there is no link to any privacy policy or terms of service.

Additionally, the survey site does not run behind https.

This screencast demonstrates the issues with login and https. Other issues are detailed after the screencast.

Moving on from the issues with login and taking the survey, we can only see the privacy policy when we go to http://oregonskitchentable.org/privacy-policy/

The policy gets off to a bad start when it states that the privacy policy can be changed, at any time, with no notice.

This policy may be updated from time to time without prior notice, so please check back periodically. If you continue to visit our Site and use the services made available to you after such changes have been made, you hereby provide your consent to the changes.

Continuing through the policy, we learn that "consultations are conducted in conjunction with DHM Research, a non-partisan public opinion research firm located in Portland, Oregon. They act as a third party consultant and aggregate all Personal Information to ensure that your responses will be kept confidential and anonymous."

From this, it's unclear who stores the data: the organization behind Oregon's Kitchen Table, or DHM Research. It appears that both Oregon's Kitchen Table and DHM Research can access responses, but unclear who can access lists of respondents.

Continuing on, the privacy policy states that data collected via surveys administered by Oregon's Kitchen Table can be combined with other data from just about any source.

Information obtained in connection with the Site may be intermingled with and used by the National Policy Consensus Center, its partners, or DHM Research in conjunction with information obtained through sources other than the Site, including both offline and online sources.

While I understand that Oregon's Kitchen Table helps facilitate policy research, the terms here are far too broad. They need to be narrowed to respect the privacy of people who are making the time to share information. Ideally, the privacy policies would be tailored to the needs and goals of the surveys.

The policy continues with a "Security" section, which includes this language:

Oregon’s Kitchen Table, The National Policy Consensus Center and our partners are committed to using our best efforts to maintaining the security of your Personal Information. To prevent unauthorized access, maintain data accuracy, and ensure the appropriate use of information, we have put into place physical, electronic, and managerial procedures to help safeguard and secure the information we collect, including an industry-standard firewall security system.

Given the absence of https on login, the claims made here fall pretty flat.

To be clear, there is nothing nefarious going on here. This clearly feels like a situation where policies were crafted to support research needs. However, in the pursuit of supporting the needs of researchers, respondents are left unnecessarily exposed. There are many changes that need to be put in place; the following list would be a decent start. Once the items on this list were in place, a full security audit that examined data collection, storage, data handling, research needs, and policies would be the next priority.

  • Specify what entity has responsibility for storing data collected in a survey;
  • Specify what entities can access survey responses, and what entities can access personal information;
  • Link to a privacy policy that is specific to the survey, and ensure that the privacy policies align with the goals of the survey;
  • For the PPS school climate survey - which appears to have a dual function of gathering information about school climate and supporting future parent outreach - specify that data collected will not be shared outside PPS without explicit opt-in;
  • Remove the language that specifies that privacy policies can be changed without notice, and update it to allow for end users to be notified of changes;
  • Add https to the user registration page.

If I'm missing anything here, or if I've gotten anything wrong, please let me know in the comments or on Twitter.

, ,

Context Is a Technical Issue

3 min read

The ability to remix and adapt openly licensed content is one of the key advantages of open educational resources - or OERs - over proprietary, traditional textbooks. However, there are still barriers to remixing that get in the way of more people making better use of this core element of open content.

For better or worse, most (all?) OERs are authored for use within a specific context. So are traditional textbooks, for that matter, but the context of a traditional textbook is the traditional school setting. There is a case to be made that the structure of traditional texts - and our familiarity and comfort with that structure - is one of the impediments to changing the structure of school as we know it. But that's a different post.

Many OERs were written to address a specific, localized need, and were published in specific systems and tools that made sense within that specific use case. These tools and contexts impose a range of structures. The more obvious structures include instructional design choices - for example, some texts embed learning outcomes at the beginning of every section. Other structures manifest in the data architecture - for example, some pieces of content require a summary alongside the main text, or treat images, video, and sound files in different ways. Another structure for web content gets added to the text itself - most OERs that have been published on a platform include css and other markup that is used to display the content in its original context, but is both meaningless and a barrier to accessibility outside that context.

This is where we run headlong into misunderstandings about what it means to "adopt" an OER. In many cases, "adopting" a text is defined as taking content that displayed in one place, and getting it to display in another. However, this approach is incomplete, and doesn't go far enough to ensure accessibility and continued reuse.

Adopting a text should mean that past assumptions - which make themselves felt in structures that surround content - are stripped from the content. When that is done, we can then reuse that content as flexibly and as quickly as possible in as many different contexts as needed. Far too often, the notion of adoption stops at the point of a single display, and that's more akin to distribution than adoption. If we limit our notions of reuse to simple distribution, we are playing the game of traditional texts, and failing to use the potential of OER to transform how we think about the roles of teachers, learners, and schools.

, ,

Who Is Going To Be The Next ConnectEDU?

3 min read

In May, during the bankruptcy proceedings for ConnectEDU, the Federal Trade Commission stepped in to stop the sale of student data as part of the bankruptcy proceedings. ConnectEDU had gathered data - including test scores, GPAs, goals, contact information, college plans, learning differences, and other detailed personal information - on millions of students as part of its services.

However, the FTC's recommendations to protect student data never happened because ConnectEDU didn't have any employees to carry them out. In December, 2014, millions of detailed student records were sold, with notification to the affected people largely happening after the fact.

Cue the rhetorical questions: what could ever happen to learner data if other companies went out of business, or were bought?

Fortunately, we don't need to wonder. The privacy policies of EdTech companies state, very clearly, that learner data is an asset, and that it will be sold.

Three examples show this pretty clearly. These examples weren't difficult to find. They were the first three policies I looked at.

Schoology

We may disclose your or your child’s personally identifiable information in connection with business transfers and purchases. As we continue to develop our business we may buy or sell business divisions or companies, we may merge or combine with another company, or our company itself and/or all or a significant part of its assets may be acquired by another company. We may provide any information we have to a potential counter-party in any such potential transaction. If such a transaction is completed, your or your child’s personally identifiable information may be one of the transferred and shared business assets.

Edmodo

If Edmodo, or some all of its assets were acquired or otherwise transferred, or in the unlikely event that Edmodo goes out of business or enters bankruptcy, user information may be transferred to or acquired by a third party.

Coursera

Coursera may disclose and/or transfer your Personally Identifiable Information to an acquirer, assignee or other successor entity in connection with a sale, merger, or reorganization of all or substantially all of the equity, business or assets of Coursera to which your Personally Identifiable Information relates.

So, who is going to be the next ConnectEDU? Or more accurately, who is going to be the next ConnectEDU we read about, because EdTech companies are going out of business all the time. A more accurate question is probably, "How many other student data transfers happened in 2014 that we never read about?"

,

Remind Steps Up Their Game

2 min read

In late 2014, Remind updated their privacy policies and terms of service. While I haven't read through the updated terms in detail to see the precise changes to the terms, there is a lot to like in their updates.

  • List of partners - this is a great step other companies would do well to follow, and it's a level of transparency that I haven't seen anyplace else. If other orgs are doing this, please let me know in the comments or on twitter. This list could be improved by being more specific about the data these companies get, but with that said, the fact that Remind created and shared that list is a huge step in the right direction.
  • Community guidelines - while these aren't legally binding, they do a good job setting clear expectations around user experience. These guidelines are well written, and help define what people should and shouldn't be doing with Remind.
  • Data sunsets of inactive accounts of under 13s - ClassDojo also implemented this, although ClassDojo goes a step further and deletes the data from student accounts that have been unused for a year.
  • Plain-language summaries as part of the Terms of Service and Privacy Policies. This is something that came up in discussions of ClassDojo's policies, and that ClassDojo also implemented last fall.

As I said earlier, I haven't read through the updated policies to see what the new terms are like, but the steps that Remind and ClassDojo are taking move things in the right direction. When companies are clear about the data they collect and how they use it, their users can make more informed choices. The steps taken by Remind and ClassDojo should become industry norms. While there is still additional work to be done, these are positive changes that help illustrate good practices. Other EdTech companies: are you listening?

, , ,

EdCamp Monsanto

3 min read

Earlier today, I found out Monsanto - yes, that Monsanto - is sponsoring EdCamp St. Louis. This makes perfect sense for Monsanto, and is part of Monsanto's corporate strategy, but it raises some questions about whether it makes sense for EdCamp.

What does it mean for an organization like EdCamp - that explicitly references a distributed model with respect for local control - when local camps agree to take money from an organization that has made billions destroying local agricuture?

What does it mean for an organization like EdCamp - which is the most visible face of the locally run events - to have local chapters preparing co-branded materials with companies that are, at best, ethically challenged? While this specific instance is about Monsanto, I imagine an EdCamp sponsored by Altria, with the EdCamp logo smoking a cigarette. Or maybe EdCamp Boulder can get sponsorship from a dispensary?

Can an organization like EdCamp claim to be about global connections when local EdCamps can create co-branded sponsor relationships that completely ignore the global connections and misdeeds of sponsors?

Given that EdCamps grew to prominence via small, non-corporate, locally run events, can they retain their authenticity if they are increasingly sponsored and co-branded by large multinational companies? What does it mean for the future of EdCamps if the rhetoric of their events drifts from the sponsorship of their events?

The EdCamp foundation can help by providing publicly accessible sponsorship guidelines. The following two changes would help dispel some of the confusion.

  • Clarify that sponsorships should favor local small businesses (potentially defined by numbers of employees, for example, 50 or under) first. If EdCamps are about elevating local voices, that should extend to sponsorships as well. The camps can have a process for handling exceptions that documents if and why an exception to these sponsorships get made.
  • Define what sponsors get. Do they get access to attendee contact info? Do they get to display a logo at the event? If they are buying lunch, do they get the chance to pitch and hand out swag during lunch? Right now, these guidelines appear to be nonexistent, which leaves local sponsors exposed to, at the least, cranks on twitter sounding off.

Now that EdCamp has a foundation and some funding, they should fill in this infrastructure. They will be facing some obvious tensions as they attempt to grow EdCamp in a way that doesn't sell out or destroy the locally developed feel that made EdCamps work in the first place.

, , ,