Every August, schools roll out new devices, software subscriptions, and polished slide decks for professional development days. Teachers sit through sessions on the latest learning management system, a flashy new assessment tool, or a coding platform the district just bought. They leave with handouts, login credentials, and a vague sense of obligation. By October, most of those tools are gathering digital dust. The problem isn’t the technology. It isn’t even the training. The problem is that training alone was never designed to change practice.
I’ve spent over a decade in classrooms and instructional technology roles, and I’ve seen this cycle repeat across districts, grade levels, and subject areas. A one-day workshop, no matter how well-designed, can’t address the real barriers teachers face when they return to their rooms: the bell schedule, the spotty Wi-Fi, the fear of looking incompetent in front of students, the curriculum map that leaves no room for experimentation. What actually shifts practice is something slower, messier, and far more human: coaching.
The Limits of Standalone Training
Training events are built on a simple assumption: if we show teachers how a tool works, they’ll use it. That assumption falls apart the moment a teacher tries to log in and gets an error message, or realizes the activity they planned requires twice as many devices as they have, or discovers that half their students can’t navigate the interface independently. Training gives teachers the what and the how, but it rarely addresses the whether, the when, or the what if.
Consider a common scenario. A middle school science department receives training on a data visualization tool that lets students graph lab results in real time. The trainer demonstrates the features, teachers practice with sample data, and everyone leaves feeling reasonably confident. Two weeks later, only one teacher has tried it. The others hit predictable snags: the tool doesn’t integrate with the gradebook they’re required to use, the Wi-Fi in their wing of the building is unreliable during third period, and the lab activity they had planned doesn’t produce the kind of data the tool needs. Training didn’t anticipate these context-specific problems. It couldn’t, because training is generic by design.
This isn’t a failure of teachers. It’s a failure of the professional learning model. When we treat technology adoption as a knowledge-transfer problem, we ignore the fact that teaching is a situated practice. Tools get adopted when they fit into a teacher’s existing workflow, solve a problem the teacher actually has, and feel safe enough to try in front of thirty students who will notice immediately if something goes wrong.
What Coaching Provides That Training Cannot
Coaching operates on a different logic. Where training is an event, coaching is a relationship. Where training delivers content, coaching builds capacity. Where training assumes a common starting point, coaching meets teachers where they actually are—in their classrooms, with their students, facing their specific constraints.
An effective technology coach does several things that a workshop facilitator cannot. First, the coach observes. They sit in the back of the room during a regular lesson, watching how the teacher manages transitions, how students interact with existing tools, where time gets lost to administrative tasks. This observation isn’t evaluative. It’s diagnostic. The coach is looking for points where a small technological shift could unlock a disproportionate amount of instructional time or student engagement.
Second, the coach co-plans. This is where the real work happens. Together, the teacher and coach identify a specific lesson or unit where a new tool might help. They don’t start with the tool. They start with the learning goal. What do students need to understand or be able to do by the end of this lesson? What’s currently getting in the way? Only then do they ask: is there a technology that could remove that barrier or deepen that learning? The tool serves the goal, not the other way around.
Third, the coach co-teaches or models. This is the moment that separates coaching from training. When a teacher sees a coach use a tool with their actual students, in their actual classroom, with their actual Wi-Fi quirks, the abstract becomes concrete. The coach can pause mid-lesson to explain a decision, troubleshoot a glitch, or redirect a student who’s off-task. The teacher watches not just the tool but the management of the tool. Afterwards, they debrief: what worked, what didn’t, what would we change next time?
Fourth, the coach follows up. This is the step most professional development models skip entirely. The coach returns a week later, or sends a quick message, or stops by during planning period. They ask: how did it go when you tried it on your own? What new questions came up? This follow-up signals that the work matters beyond the one-day event. It also catches problems before they become reasons to abandon the tool altogether.
The Difference Between Support and Coaching
Many schools believe they already have coaching because they employ instructional technology specialists. But the title doesn’t guarantee the practice. In too many districts, technology specialists are consumed by troubleshooting: fixing projectors, resetting passwords, updating devices. That’s support work, and it’s necessary. But it’s not coaching.
Support is reactive. A teacher puts in a ticket because the interactive whiteboard isn’t calibrating, and someone shows up to fix it. Coaching is proactive. A coach reaches out to a teacher and says, “I noticed your students are doing a lot of collaborative research. Have you thought about using a shared digital workspace so they can see each other’s contributions in real time?” Support solves technical problems. Coaching solves instructional problems, sometimes with technology and sometimes without.
This distinction matters because schools often measure the wrong things. They count the number of tickets closed or the number of workshops delivered. Those metrics tell you nothing about whether teaching and learning are actually changing. A better metric: how many teachers invited the coach back for a second conversation? How many tried something new in their classroom and then reflected on it with a peer? Those numbers are harder to collect, but they measure actual growth.
Building a Coaching Culture in Schools
Shifting from a training model to a coaching model requires more than hiring a coach. It requires building a culture where coaching is expected, respected, and protected. This is where leadership matters most.
First, administrators must model the posture they want teachers to adopt. When a principal openly shares a practice they’re working to improve and invites feedback, it signals that growth isn’t remedial. It’s professional. A principal who says, “I’m trying to use data dashboards more effectively in staff meetings, and I asked our coach to help me think through that” is doing more for coaching culture than any policy mandate could.
Second, coaching must be separated from evaluation. Teachers won’t be honest about their struggles if they fear that vulnerability will show up in their performance review. The coach’s notes, observations, and conversations must be confidential. This firewall is non-negotiable. Without it, coaching becomes just another form of surveillance.
Third, coaching needs time. Not just the coach’s time, but teachers’ time. Schools that are serious about instructional change build coaching into the master schedule. They provide common planning periods where coaches can meet with grade-level or content teams. They use substitute teachers strategically to free up teachers for observation and co-teaching cycles. They recognize that one-off training days are cheaper in the short term but far more expensive in the long term, because they produce so little lasting change.
Fourth, coaching must be differentiated. A first-year teacher struggling with classroom management needs something very different from a twenty-year veteran who wants to redesign an entire unit around project-based learning. The coach’s role is to diagnose where each teacher is and provide the right level of challenge and support. This requires deep knowledge of both pedagogy and technology, plus the interpersonal skills to navigate a wide range of relationships.
What Effective Technology Coaching Looks Like in Practice
Let me describe a coaching cycle I facilitated with a high school English teacher, Ms. Alvarez. She was teaching argumentative writing to tenth graders. Her students could state a claim and find evidence, but their reasoning was consistently weak. They’d drop a quote into a paragraph and then move on, never explaining how the evidence connected to their claim. Ms. Alvarez had tried modeling, sentence starters, peer feedback—nothing stuck.
When she invited me into her classroom, I watched students write for a full period. I noticed they were composing in Google Docs, but they weren’t using any of the collaborative features. Each student worked in isolation. The only feedback they received came from Ms. Alvarez, days later, after she had graded thirty essays. By then, the thinking was cold.
We sat down during her planning period and mapped out the real problem: students needed to see models of strong reasoning, and they needed feedback while their thinking was still warm. The technology question came last. I suggested we try using the comment feature in Google Docs for a structured peer feedback protocol. Students would share their drafts with a partner, and each partner would highlight the evidence sentence and write a comment asking, “What does this evidence show? How does it support your claim?” The author would then reply to the comment with their reasoning.
I co-taught the first session. I modeled the protocol with a student volunteer while Ms. Alvarez watched. Then we both circulated as students practiced. There were glitches: some students didn’t know how to share documents, others wrote vague comments like “good job” instead of the prompt. We paused, re-taught the comment structure, and continued. By the end of the period, every student had received specific feedback on their reasoning, and every student had written at least one revision.
Ms. Alvarez tried the protocol on her own the following week. She emailed me: “It worked. They actually explained their evidence. And they were talking to each other about their writing, not just waiting for me.” That moment—a teacher discovering that a tool, used strategically, could solve a real instructional problem—is what coaching produces. A workshop could not have done that.
Common Pitfalls in Technology Coaching
Even with a coaching model in place, there are predictable ways it can go wrong. Being aware of these pitfalls helps coaches and administrators avoid them.
Pitfall 1: The Tool-First Approach. A coach walks into a planning meeting excited about a new app and spends the whole time pitching it. The teacher nods politely and never uses it. Effective coaching always starts with the learning problem, not the technology. If the coach can’t articulate what instructional need the tool addresses, they shouldn’t bring it up.
Pitfall 2: Biting Off Too Much. A teacher agrees to try something new, and the coach designs an elaborate, multi-step project that requires students to use five different tools. The teacher becomes overwhelmed, something breaks, and the whole thing collapses. Start small. One tool, one lesson, one success. Build from there.
Pitfall 3: Ignoring Classroom Realities. A coach recommends a tool that requires 1:1 devices, but the teacher shares a cart with three other teachers. Or the tool relies on audio, but the classroom has no headphones. Coaches must understand the material constraints of each teacher’s situation before making suggestions.
Pitfall 4: Abandoning the Teacher After the First Try. The coach co-teaches a lesson, it goes well, and the coach moves on to the next teacher. A month later, the first teacher has stopped using the tool because a new problem arose and there was no one to help troubleshoot. Coaching is a cycle, not a single event. Follow-up isn’t optional.
Pitfall 5: Treating All Teachers the Same. Some teachers need foundational tech skills before they can think about integration. Others are ready to redesign entire units. A coach who applies the same approach to everyone will frustrate beginners and bore experts. Differentiation is as important for adult learners as it is for students.
Measuring the Impact of Coaching
If coaching is an investment, schools need ways to know whether it’s paying off. Standardized test scores are too blunt and too slow. Better measures are closer to the classroom and more frequent.
One useful metric is the quality of student tasks. When technology integration is working, students spend more time on higher-order thinking: analyzing data, constructing arguments, creating original work, collaborating on complex problems. A coach can track this by periodically reviewing lesson plans or student work samples with teachers, using a simple framework like the SAMR model or Webb’s Depth of Knowledge.
Another metric is teacher self-efficacy. Do teachers feel more confident trying new tools on their own? Do they seek out the coach for increasingly sophisticated requests? A simple end-of-semester survey can capture this shift, but so can the coach’s informal notes: are teachers initiating contact, or is the coach always pushing?
A third metric is spread. Does effective technology use stay isolated in a few early-adopter classrooms, or does it migrate? When a teacher presents at a staff meeting about a tool they used successfully, that’s a sign of a healthy coaching culture. When a grade-level team decides collectively to adopt a practice they saw a colleague use, coaching is working.
What This Means for School Leaders
If you’re a principal, instructional director, or superintendent, the implications are clear. Stop funding one-day technology workshops and start funding coaching positions. Protect those positions from being consumed by tech support tasks. Give coaches the time and access they need to build relationships with teachers. And hold coaches accountable not for the number of workshops they deliver, but for the depth of the instructional change they facilitate.
This isn’t a call to eliminate training entirely. Sometimes a whole department needs to learn the basics of a new gradebook system, and a workshop is the efficient way to deliver that information. But training should be the starting point, not the whole strategy. The real work of integration—the work that changes what students do and what they learn—happens in the classroom, over time, with a coach alongside the teacher.
Technology will keep changing. New tools will arrive every year. The goal isn’t to train teachers on every new product. The goal is to build teachers’ capacity to evaluate tools, to integrate them thoughtfully, and to adapt when things go wrong. That capacity isn’t built in a workshop. It’s built through sustained, job-embedded, collaborative inquiry. It’s built through coaching.
Frequently Asked Questions
What is the difference between technology training and technology coaching?
Training is a one-time or short-term event focused on teaching the features of a specific tool. It’s typically delivered to a group and follows a set curriculum. Coaching is an ongoing, individualized process where a coach works alongside a teacher in their actual classroom context. Coaching focuses on instructional goals first, then identifies technology that can support those goals. It includes observation, co-planning, modeling, and follow-up support over time.
How much time does effective technology coaching require?
Meaningful coaching can’t happen in occasional drop-in visits. A typical coaching cycle—observe, co-plan, co-teach, debrief, follow-up—might span two to four weeks for a single focused goal. Coaches need regular, scheduled time with teachers, ideally during common planning periods or through strategically arranged coverage. Schools that see the strongest results often allocate at least one full coaching day per week per grade-level team or department.
Can a school have technology coaches if it has a limited budget?
Yes, but it requires creative staffing. Some schools designate an experienced teacher as a part-time coach, reducing their teaching load by one or two sections. Others share a coach across two or three small schools in a district. The key is protecting the coach’s time from non-coaching duties. Even a part-time coach who spends 80% of their time on coaching cycles will have more impact than a full-time specialist who spends 80% of their time on tech support and workshop delivery.
What if teachers resist coaching?
Resistance usually comes from one of two sources: fear of evaluation or past experience with ineffective professional development. Address the first by ensuring coaching is strictly confidential and separate from performance review. Address the second by starting small. Offer to help with something the teacher already wants to improve, using technology only if it genuinely helps. Build trust through follow-through. Once one teacher has a positive experience, word spreads.