Why K–12 Technology Leaders Belong in Strategic Decisions

Technology leaders are often asked to make a district initiative work after the most important decisions have already been made. A platform has been selected. A contract has been signed. A launch date is on the calendar. Then IT is asked to connect the systems, adjust the network, manage access, address privacy questions, support educators and students, and solve the problems nobody anticipated.

That sequence is backwards.

Technology leaders belong in the strategic conversation before a district chooses a tool, defines a workflow, or commits to an implementation plan. Their perspective can surface risks earlier, connect decisions to real user needs, and help districts move from “How do we make this work?” to “What are we trying to make possible?”

This was the central theme of a recent Follett Software practitioner conversation featuring Dr. Matthew X. Joseph, Wanda Terrell and Tracy Sokolowski. Their discussion offered practical guidance for district leaders, curriculum teams and technology professionals who want technology decisions to support teaching, learning, operations and long-term district priorities.

Implementation starts before launch day

When technology leaders enter a project late, implementation becomes a repair exercise. A new tool may not work on every device. Network changes may be required. Filters or permissions may need to be adjusted. Data privacy questions may surface after the purchase. Facilities teams may discover that wiring, power or physical access was never included in the plan.

The cost is more than inconvenience. Late involvement can affect the people who ultimately use the technology: teachers, students, administrators and families. It can delay the work the tool was intended to support and create frustration before anyone has had a fair opportunity to experience its value.

Early involvement changes the conversation. Instead of reviewing a finished decision, technology leaders can help shape the conditions for success: the district’s desired outcome, the users who need to benefit, the systems that must connect, the information that must be protected and the support required for adoption.

Start with the outcome, not the tool

A productive technology conversation does not begin with a favorite platform. It begins with a shared question: What do we need students, educators or district teams to be able to do better?

That distinction gives a district more options. If a preferred tool does not work within the district’s devices or infrastructure, the team can look for another way to achieve the same outcome. If teachers need a more accessible way to engage with content, the discussion can focus on access and participation rather than on a feature list. If the goal is to improve a workflow, the team can examine the workflow before selecting software.

This approach also brings educators into the work earlier. Teachers understand classroom realities that may not appear in a product demonstration. Students can reveal barriers adults might miss. A pilot can show where a tool helps, where it creates friction and what support is needed before a district expands its use.

The question is not simply whether a tool works. It is whether it works for the people and purpose the district is trying to serve.

Build the right decision team

Technology decisions rarely belong to one department. A stronger team brings the relevant perspectives together before the district reaches the procurement stage.

Depending on the initiative, that group may include:

• Technology leaders, who can assess infrastructure, integrations, access, security, data privacy and support requirements.
• Curriculum and instructional leaders, who can connect the decision to learning goals and district priorities.
• Teachers and school leaders, who can explain how the workflow will function in practice.
• Students and families, who can identify accessibility, communication and usability concerns.
• Special education and multilingual-learner leaders, who can help evaluate whether the solution supports the full range of learners.
• Finance, procurement and district administration, who can clarify budget, contract and sustainability requirements.
• Facilities teams, when the project affects wiring, rooms, devices, safety systems or building operations.

The exact roster will vary. The principle does not: the people accountable for the outcome should have a voice before the decision is final.

Make constraints visible early

A trustworthy implementation plan is candid about what the technology can and cannot do.

That means being clear about whether a project is a pilot, what access is included, which versions or integrations are available, and what support will be provided. It means identifying workarounds before teachers encounter them in the middle of a lesson. It means addressing data privacy and student information requirements before anyone starts sharing records. It means making time for training, testing and feedback—not treating those activities as optional after the purchase.

Honesty is not a barrier to adoption. It is part of adoption.

When people understand the boundaries of a project, they can make better decisions about where to invest effort. They can prepare for limitations, suggest improvements and decide whether the expected outcome justifies the work. They are also more likely to trust the leaders guiding the change.

Move technology leadership beyond the fixer role

Technology teams are often recognized when something breaks and overlooked when everything works. That makes it easy for a technology leader to be viewed primarily as a fixer rather than as a strategic partner.

Changing that perception requires more than an invitation to a meeting. It requires relationships and visible connection to district priorities.

Technology leaders can start by spending time in schools and observing how work actually happens. What appears to be a minor technical request may point to a larger workflow problem. A recurring support issue may reveal a training gap, an integration problem or a process that was never designed for the current scale of the district. A more connected operating model can make those patterns easier to see and address.

They can also frame recommendations around the people they are trying to help. The goal is not to make IT’s work easier in isolation. The goal is to remove obstacles for teachers, students, administrators and other teams so they can do their work with less friction.

Curriculum and district leaders have a role, too. Invite technology leaders into the first conversation—not the final review. Share the intended outcome before selecting a solution. Ask what the technology team needs to know, test or plan for. Treat their questions as part of responsible leadership, not resistance to change.

Start with one shared problem

Districts do not need to redesign every decision process at once. A practical first step is to identify one problem that crosses departments and matters to the school community.

Bring the right people together. Define the outcome. Ask technology leaders to assess the conditions for success. Invite educators and other end users to test the proposed approach. Then use what the team learns to improve the next decision.

A small, visible success can build trust across departments. It shows that collaboration is not a delay added to the work. It is how the district avoids preventable rework and gives people a better chance to succeed.

When technology is working, the learning stays at the center

The best technology partnership may not call attention to itself. In a classroom, the focus should remain on the learning, the conversation or the student—not on the fact that a system had to be configured to make the experience possible.

That does not make the technology leader’s role less important. It makes the role more strategic. Behind a seamless experience are decisions about access, infrastructure, privacy, support, data and sustainability. Those decisions are strongest when the people responsible for them are part of the conversation from the beginning.

Technology leaders should not have to wait for launch day to be heard. They should have a seat at the table before the contract is signed, the workflow is designed and the district is asked to change.

When IT is included early, schools have a better chance of turning technology investments into better school days.

Watch the on-demand webinar, “Beyond Implementation: Why Technology Leaders Belong in Strategic Conversation.”