Blog | CESA 6

Deploying Technology During the School Day: Lessons from Random Lake

Written by Michael Gilbert | Mar 6, 2026 3:02:23 PM

In K12 education, technology is everywhere. Interactive whiteboards, student information systems, classroom laptops, and district-wide communication tools are just the start. One of the most underappreciated challenges IT teams face is implementing major systems without disrupting learning.

On March 9th, attendees at the Brainstorm conference will hear from two experts who recently managed one of the most challenging scenarios in school technology. Gabriel Goebel, network administrator at CESA 6, and Lee Itson, District Technology Coordinator at Random Lake School District, will share the story of how they replaced an entire district phone system in the middle of a school day. They will discuss lessons learned and strategies that other districts can apply when planning complex technology deployments.

The Challenge: Change Without Chaos

Replacing a phone system in any organization can be disruptive. In a school district, the challenge is even greater. Phones are critical for teachers, staff, and safety operations. At Random Lake, the stakes were high. The district was in the middle of a referendum, and every school day carried extra pressure.

Gabe Goebel, who has eight years of K12 IT experience and certifications in 3CX, Verkada, and Fortinet, says, “We knew there was no room for downtime. Teachers needed uninterrupted access to phones. Office staff had deadlines. Communication is always critical. It was not just about replacing hardware. It was about keeping the district running smoothly during the transition.”

Lee Itson brought a combination of educational technology leadership and cybersecurity expertise. He emphasized that the system had to work in classrooms, offices, and hallways on day one. Lee shared that they had to consider every possible point of failure. It was not enough for the system to work in a test environment. It had to work in real time in a real district.

Strategic Planning

The success of the rollout began long before any hardware was installed. Gabe and Lee approached the project like a high-stakes operations plan.

Key steps included:

  1. Mapping the Current System: They documented every extension, call route, and department needs to make sure the new system matched the old one without disruption.

  2. Simulating the Deployment: A sandbox environment allowed the team to test call flows, voicemail, and features multiple times before going live.

  3. Creating Contingency Plans: Backup communication methods and temporary call reroutes were prepared in case of unexpected problems.

  4. Communicating With Staff Early: Teachers, administrators, and office staff were informed ahead of time about what to expect. This reduced stress and built trust.

The result was a smooth rollout with minimal disruption.

Collaboration as a Success Factor

Collaboration between CESA 6 and Random Lake was critical. Often technology projects treat the client as an observer. In this case, Gabe and Lee worked as a team. They combined technical skills, operational knowledge, and local context.

“Lee was a partner, not just a client,” Gabe explained. “His understanding of the district’s workflow, combined with our technical expertise, allowed us to make decisions quickly. That collaboration made the rollout possible during a school day.”

Lee noted that culture mattered as much as technology. In schools, trust is key. Staff need to know that IT teams are thinking about their work and their students, not just the technology. This approach highlights a core lesson for educational technology leaders. Technology is only effective if it supports the people who use it.

Lessons Learned

While the project focused on a 3CX phone system, the lessons apply to other technology initiatives in schools.

  1. Plan for Real-World Conditions: Test systems in sandbox environments but validate against actual workflows. Classrooms and offices often operate differently than test environments.

  2. Prioritize Communication: Keep staff and stakeholders informed. Transparency reduces stress and increases adoption.

  3. Build Flexible Contingencies: Identify risks and create backup options. Empower staff to act if problems arise.

  4. Partner Across Roles: Collaboration between IT teams, educators, and administrators ensures solutions are practical and sustainable.

Measure Impact Beyond Cost: While the new system reduced expenses, the most valuable benefits were improved service and staff satisfaction. Technology should support people’s work. 

Practical Insights for Other Districts

At Brainstorm, Gabe and Lee’s session, “How We Deployed a 3CX Phone System During a School Day and Improved Service While Saving Money,” will focus on actionable strategies. Attendees can expect to learn how to minimize disruption, maximize collaboration, and achieve technology goals even under tight timelines.

As districts modernize, the ability to deploy systems efficiently, maintain service continuity, and empower staff and students is increasingly important. The Random Lake story shows that careful planning, clear communication, and teamwork can make even ambitious technology projects successful.

Conclusion

Innovation in education often happens behind the scenes. Teachers and students may not notice the networks, phone systems, and security infrastructure that make learning possible. Gabe and Lee’s work demonstrates that thoughtful planning, collaboration, and human-centered technology leadership are what make innovation sustainable and replicable.

For those attending Brainstorm, this session will offer more than technical insight. It will provide a framework for tackling complex technology challenges, partnering effectively with district staff, and turning projects into lasting improvements for schools.