The Technology Worked. The Rollout Didn’t.
The new system went live on Monday.
The data migrated. The integrations worked. Single sign-on worked. The vendor hit the deadline. From a technical project-management standpoint, the implementation was a success.
By 9:15 a.m., the help desk was buried.
Teachers couldn’t find the workflows they had used for years. Office staff had developed workarounds nobody knew about during planning. Principals were answering questions they hadn’t been prepared to answer. Some employees were quietly returning to the old process wherever they still could.
Nothing was actually wrong with the technology, but the rollout was failing anyway.
This is one of the most important distinctions in education technology leadership: getting a system to work is not the same thing as getting an organization to change.
The 2026 Blaschke Report on K–12 technology change management makes that distinction clearly. Project management delivers the technical solution. Change management helps people understand, accept, use, and sustain it.
We are generally pretty good at the first part. We build implementation timelines. We review privacy agreements. We configure systems, migrate data, test integrations, assign licenses, schedule training, and pick a launch date. There are tasks, owners, deadlines, and usually a very satisfying collection of green checkmarks showing that the project is on track.
Then we get to launch day and discover that people do not change because the project plan says they should.
Training Isn’t the Same as Readiness
One of the most common mistakes we make is treating change management as a synonym for training.
Training matters. People need to know which buttons to push and how a new process works. But knowing how to do something does not mean someone understands why it is changing, believes the new approach will improve their work, or has the conditions necessary to use it successfully.
Imagine a district replacing a learning management system. The technology team may know exactly why the change is necessary. Perhaps the old system is expensive, difficult to support, or missing critical functionality. But what does the teacher know?
If the first meaningful communication a teacher receives is an invitation to a two-hour training session, we have skipped several steps. From that teacher’s perspective, a familiar tool may simply be disappearing and being replaced by something that requires more work. And … then we respond by providing more training.
But if the barrier is trust, time, workflow, unclear expectations, or lack of understanding about why the change is happening, another webinar on where to click will not solve it.
Start Before the Purchase Order
Good change management begins much earlier than launch. Before asking, “How do we roll this out?” we should be asking, “What problem are we solving?”
That sounds obvious, but education is as susceptible to shiny objects as any other industry. A new tool enters the market. A neighboring district adopts something. A compelling demo creates excitement. Suddenly we are discussing implementation before we have clearly articulated the problem.
A documented need gives the change a foundation. It also gives leaders something essential to communicate. People are much more likely to engage with a transition when they understand what is driving it.
That also means involving the people whose work will actually change. Teachers, support staff, administrators, families, and students will experience the same implementation differently. A process that makes perfect sense from the district office may create three extra steps at a school. A security improvement may unintentionally complicate a workflow. A new platform may eliminate an informal practice nobody thought to document.
Find the People Others Trust
This is why change champions matter. The most valuable change champions are often the people their colleagues trust enough to tell the truth. They can explain what is happening, but just as importantly, they can bring concerns back to the implementation team.
If our “champions” exist only to convince everyone that the decision was wonderful, we have created a marketing team, not a feedback loop. Real engagement leaves room for someone to say, “This isn’t working for us,” and for leaders to investigate whether the problem is resistance to change or a legitimate flaw in the implementation.
Sometimes the users are telling us something we need to hear.
Launch Is the Middle, Not the End
Perhaps the biggest shift is simply changing how we think about the launch date. For project management, go-live can feel like the finish line. For the people experiencing the change, it may be the starting line. That is when real working conditions collide with everything we planned.
Can people actually perform the new process? Where are support requests clustering? Which groups are adopting quickly, and which are struggling? Are people using the new system as intended, creating workarounds, or quietly reverting to old practices?
Those are not signs that the project team failed. They are information. The goal after launch should not be to defend the implementation. It should be to learn from it.
This requires continued communication, support, feedback, and sometimes adjustment. Different groups may need different things at different times. One group may still be asking why the change was necessary while another is ready for advanced training.
Change rarely moves through an organization in a neat, synchronized line.
Two Tracks, One Implementation
None of this diminishes the importance of strong project management. We need the technical work to be excellent. The system has to function. The data has to be secure. The integrations have to work. The budget and timeline still matter.
But there are really two tracks running alongside every major technology implementation. One is about the technology. The other is about the people who have to live with it. We create problems when we meticulously plan the first and assume the second will take care of itself.
So before the next rollout, add a few questions to the implementation plan: Do people understand why this change is happening? Have the people most affected had a meaningful opportunity to identify problems we may not see? Do they have what they need to perform differently, not just knowledge of the new tool? Where will feedback go after launch? And how will we know six months from now whether the change actually stuck?
Successful implementation is the moment the technology works and the people it was intended to serve can work successfully with it.
Media Literacy Minute

Social Media and Kids: A Parent’s Guide
A Tufts child-development expert argues that banning social media is hard to enforce and that open conversations, modeling healthy habits, and media literacy may serve kids better. This Tufts Now interview offers practical steps for families, including keeping screens in shared spaces, setting device-free times, and teaching children to recognize advertising.
Tech Tips for Parents this Digital Parenting Week
Rather than relying only on restrictions, the Electronic Frontier Foundation encourages families to build a shared digital safety plan together, starting with open conversations about the apps kids use. This EFF post also covers privacy settings, photo-sharing rules, password managers, and using parental controls as a starting point for family discussion rather than a final answer.
Protecting Students in a Digital World
One major organization is urging districts to limit personal device use during the school day, citing research on distraction and cyberbullying while also calling for stronger media literacy education. This NEA action guide is a thought-provoking read for anyone weighing when devices support learning and when they get in the way, and what role media literacy should play either way.
We Can’t MFA Our Way Out of a Staffing Problem
MFA works.
We should use it. We should secure email. We should patch systems, filter malicious traffic, manage identities, train employees, monitor networks, and implement every reasonable safeguard available to us. But we need to stop pretending that adding another security control solves the underlying cybersecurity challenge facing many school districts.
The newly released State of K-12 Cybersecurity 2026 report from CIS, the MS-ISAC, and CoSN tells an interesting story. Eighty-three percent of surveyed schools and districts report implementing multi-factor authentication and email security protections. At the same time, 51% reported experiencing a cyber incident in the previous 12 months. For 34%, an incident affected school operations.
The lesson isn't that our security tools aren't working, it's that tools are only part of the job.
Who Is Watching All of This?
Here's the number that caught my attention: 66% of districts have just one or two people responsible for cybersecurity. Not necessarily one or two people whose only job is cybersecurity. One or two people responsible for it.
Think for a minute about what we are asking those people to protect.
Student information systems. Payroll. Financial systems. Transportation. Food service. Learning platforms. Employee accounts. Student accounts. Thousands of devices. Cloud services. Third-party vendors. Network infrastructure. Sensitive student and employee data.
All of that is connected to thousands of human beings who click things, forget passwords, try new apps, log in from home, share information, and occasionally make mistakes.
The work of the school district depends on the network.
Yet in many organizations, the people charged with protecting that environment are also managing infrastructure, troubleshooting devices, responding to help-desk tickets, reviewing contracts, dealing with vendors, supporting classrooms, managing accounts, and handling whatever crisis showed up at 7:42 that morning. Then we wonder why cybersecurity feels reactive.
The Tools Don't Do the Work by Themselves
MFA can make a compromised password much less useful to an attacker. It cannot review the risk in your next vendor contract.
Endpoint protection can identify suspicious activity. It cannot decide whether that activity requires shutting down a system that payroll needs tomorrow morning.
A security awareness platform can send phishing simulations. It cannot build a culture where an employee feels comfortable immediately admitting, “I clicked it.”
Backups can help restore data. They cannot lead a superintendent, communications team, legal counsel, technology staff, school leaders, and potentially law enforcement through the first chaotic hours of a major incident.
Those things require people. They require expertise, judgment, relationships, planning, practice, and time.
And time may be the resource we underestimate most.
We Have Made Progress. Now We Need Capacity.
I don't want this to become another cybersecurity message that tells school districts everything they're doing wrong.
The fact that 83% of responding organizations report MFA and email security protections is worth recognizing. Schools are implementing stronger defenses, often with very small teams and constrained budgets.
Another 2026 CoSN survey found that 65% of education technology leaders considered their cybersecurity function understaffed.
We can keep raising the technical expectations for districts—and many of those expectations should rise. But every additional tool, requirement, monitoring system, compliance obligation, incident-response procedure, vendor review, and security control creates work for someone. At some point, cybersecurity maturity depends on having the capacity to do that work well.
That doesn't mean every district needs a large internal security team. For some, the answer may include shared services, regional partnerships, managed services, state support, automation, or other approaches that put expertise within reach.
“Someone should be doing this” is not a cybersecurity strategy. Someone actually has to have the capacity to do it.
Cybersecurity Is an Organizational Question
For years, we have worked to convince leaders that cybersecurity isn't just the technology department's problem. That's true. If cybersecurity belongs to everyone, that cannot become an excuse for it to belong adequately to no one.
Teachers have a role. Administrators have a role. Boards have a role. Vendors have a role. Every employee who handles district information has a role. But shared responsibility still requires dedicated expertise.
Nearly 80% of respondents in the 2026 CoSN State of EdTech report said they need more cybersecurity support, resources, or guidance. We should listen to what they are telling us.
The next step in strengthening K–12 cybersecurity is asking whether the people responsible for protecting increasingly complex school systems have the time, expertise, support, and resources to do the work we are asking of them.
Keep the MFA. But let's make sure there's someone on the other side of it with enough capacity to protect the rest of the system.
Big Ideas: The Secret Lives of Small Creatures

Spiders that nap like we do, bees that act like middle schoolers, and fish that dress up as seahorses. The animal kingdom is weirder, and pettier, than the nature documentaries let on.
Spiders Sleep, and They Might Even Dream
Turns out the spider in the corner of your ceiling may be catching some REM. Researchers at the University of Bonn found that the Australian jumping spider Portia fimbriata sleeps in two distinct stages, one of which looks remarkably like human REM sleep: eyes moving, legs curling, muscles twitching. When the team disrupted the spiders’ rest, the spiders made up for it the next night with about 80% more REM-like sleep, the arachnid version of sleeping in on Saturday. Before anyone starts imagining spider nightmares about vacuums, the researchers are careful to say twitching doesn’t prove dreaming. It does suggest that complex sleep shows up in animals with nervous systems wildly
Honey Bees Are the Playground Bullies of the Flower Bed
The bees on every “save the bees” tote bag have a dark side. A two-year study by Anglia Ruskin University researchers around Cambridge, England, found that honey bees routinely chase, shove, and intimidate other pollinators off flowers. Other insects steered clear of honey bees in roughly a third of encounters, and on bramble, doubling the honey bees was linked to a 14% drop in bumblebees. The lone holdout is the ivy bee, the only species that reliably stood its ground. The researchers also warn that warmer weather makes the competition fiercer. The point isn’t to give up beekeeping; it’s that “saving the bees” means all the bees, not just the famous ones.
Meet the “Sea Muppets”: Seahorse Lookalikes Nobody Has Ever Seen Alive
Deep in the ocean live three tiny fish that look exactly like seahorses. They’re not seahorses. A new study found these thumb-sized oddballs belong to an entirely separate evolutionary group, which means nature invented the seahorse shape more than once. They’re known from just seven preserved specimens, and no one has ever seen one alive, which officially makes them “lost species.” It’s convergent evolution in action, and proof that sometimes evolution gets a good idea and decides to use it twice.
Spiders nap, bees bully, and fish cosplay. The animal kingdom is basically middle school with more legs.