Tips for launching a one-to-one initiative

Second, listen to the “customers.” When it came down to determining what device we would use to support a one-to-one computing initiative, we vetted and interviewed several capable and highly respected providers. When we were down to the final choices, we handed the devices to our students—the end users, the customers, the ones who frankly would make this project succeed or fail. Our student panel chose the Dell Latitude 10 for its ease of use, Microsoft platform, and cost.

Third, don’t go about it alone. Developing and deploying a one-to-one computing initiative is not just a “technology” project. It requires buy-in, support, and sweat equity from a lot of people inside and outside the school district. We have the most talented and dedicated team of professionals, including personnel support from Dell and Microsoft, working through every technical, instructional, and financial detail to offer a truly personalized learning experience and initiative for students. We have called on our parents to help determine what anytime learning looks like at home from internet filters, parent responsibilities, insurance, and more. We will put together a team of students to help define Digital Citizenship for our school district and create the consequences of when it is not followed.

Finally, be patient. I’m assuming that if you are reading this, you might have some interest in how a one-to-one computing initiative can be done at your school district. Here’s the point I will try to make when it comes to the process of crafting a technology vision and initiative for a school district: there are no short cuts.

There is experience, vision, and purpose, and there are best practices and techniques, but there is no recipe, or answer to be found in the review of another school district’s choice. Much like a student’s learning, the value is in the process, and it is best done by a team. The solution is un-Googleable. Anyone who simply tries to replicate another district’s initiative on the notion of not “reinventing the wheel” likely will be disappointed. Rather, this should be a precision-engineered gear that needs to fit into a complex machine that’s a little different in every district. It must be designed, engineered, built, and installed. By all means, guidance should be sought—and we can all learn from others (Project RED is a great place to start)—but the solution does not have a SKU number.

When the focus is on something greater than any individual or department and the work challenges everyone to grow beyond their previous limits, honesty emerges and real teams are made. When you work on a project like this that centers on access and learning in your school district (and you will—it’s inevitable), may you have something unexpected happen to you as well.

Kevin Schwartz is chief technology officer for the Clear Creek Independent School District in Texas.

Previous 1 2