Articles · District leadership · EdTech · Equity
Leading a one-to-one rollout: what every district should plan for
Devices are not the intervention. What every district should plan before a one-to-one launch: capacity, the use divide, connectivity, families, and pace.
By Dr. William Hickman · 5 min read
In 2013 and 2014, I served as area superintendent for the South Region of the Houston Independent School District, one of the largest districts in the nation. That was the period of PowerUp, a one-to-one technology initiative for high schools across the district. Later, as a superintendent in Mississippi, I was selected as a U.S. Department of Education National Ambassador for education and education technology.
I am not going to grade any one initiative here. What I can offer is the planning list I would put in front of any board before a single device ships. A one-to-one launch is like installing a new offense in the middle of a season: the playbook matters, but the reps, the coaching, and the timing decide whether it works.
The device is not the intervention
The history of educational technology is full of well-funded launches that changed little. Larry Cuban documented the pattern in 2001 in Oversold and Underused: schools bought computers and then used them far less, and far more conservatively, than the purchase implied. Teachers did not reject the machines. They absorbed them into the lesson they were already teaching, and the computer became a worksheet with a battery.
So decide, before launch, what you will measure. Device counts, logins, and minutes tell you the project happened. They do not tell you whether students learned. A better measure is what students made: essays revised, data analyzed, programs written, films edited. Put that measure in the first board presentation, so nobody is tempted to celebrate a count.
Plan for the use divide, not only the access divide
Access is the divide a purchase order can narrow. The 2024 National Educational Technology Plan names two more. The design divide is the gap in teachers’ capacity to design learning with technology. The use divide is the pattern in which students in under-resourced schools more often use technology for passive, drill-based tasks, while their better-resourced peers use it to create and analyze.
Read that twice. The laptop can be identical, bought on the same contract, and the learning it delivers is not. A plan that distributes devices equally and leaves assignments to chance can widen the gap it was meant to close.
The fix is to plan the work, not just the hardware. Describe the kinds of tasks you expect to see in every building. Then sort the usage report by school each quarter. If the same product is used for making in one building and for drill in another, you have found the use divide inside your own district.
Build capacity before you ship
Professional development that teaches teachers to log in is orientation. Capacity is something else: knowing how to read what a platform shows, when to follow it, when to override it, and how to design a lesson where the device does real work.
Build that before launch and keep building it after. One training day is not a plan. Coaching cycles, data inquiry teams, and a learning community that keeps meeting after the launch photos are taken: that is the plan. The investment has a payoff. In Hattie’s 2017 synthesis, collective teacher efficacy, a staff’s shared belief that together they can move students, carries an effect size of 1.57, among the strongest influences he lists.
And let teachers build something with the tools before they teach with them. Nobody wants to lead a lesson in front of thirty students on equipment she has never touched.
Scan readiness honestly
In The Intelligent Classroom I describe seven readiness dimensions for bringing AI into a system. They work just as well for any large technology rollout.
- Technology infrastructure: working devices, reliable connections, and compatibility with the assistive technology students already use.
- Data architecture: whether your systems can feed one student view without someone rekeying data into a spreadsheet.
- Governance: who approves tools, manages data agreements, and responds when something breaks.
- Professional capacity: whether teachers, leaders, and technology staff have the knowledge they need, and whether coaches exist to help them.
- Equity readiness: whether the plan names students with disabilities, multilingual learners, and students in under-connected neighborhoods specifically, or waves at them generically.
- Community trust: whether families know what is being used and why.
- Organizational readiness: whether leadership agrees on the goal and can hear bad news from a pilot without punishing the messenger.
Score each one high, medium, or low, and be honest about the lows. A district that scores high on devices and low on equity is not ready. Neither is one with strong teachers and no governance.
Plan for the hours after the bell
A device that goes home without a connection is an expensive notebook. Before launch, find out which students lack reliable internet at home, and plan for them: connectivity options, assignments that work offline, and homework that does not penalize a student for where she lives. Ask where your students actually spend the hours after school, and meet them there.
Plan for the ordinary logistics too, because they decide whether a program survives its first winter: charging, repairs, loaner devices, and what happens when a laptop breaks two days before a project is due.
Earn the trust of families
Every family should be able to answer three questions: what the device and its software do, what data they collect, and whom to call with a concern. Put the answers on one page in the languages your families speak. Hold sessions where parents can try the tools their children will use. A plan families understand earns support. A plan they first hear about secondhand earns suspicion.
Pace to capacity, not to ambition
The pressure to scale comes from everywhere: grant timelines, board expectations, vendor sales cycles, the district across the county that announced first. Scale anyway at the pace your coaching, infrastructure, and governance can absorb. Pilot for evidence, not applause. Report results by student group, not only in the aggregate, because an average can hide the students a program is failing. Then let the evidence decide what happens next: continue, modify, expand, or stop.
What to do this week
- Change the metric. Rewrite your technology goals so at least one measures what students make, not devices or minutes.
- Sort the usage report by application and by school. Place your five most-used applications on a simple line from consume to create.
- Score your readiness on the seven dimensions with a small team that includes special education, multilingual services, and a parent.
- Map connectivity. Find out which students lack reliable home internet before anyone assigns work that requires it.
- Write the family page in plain language, and translate it.