The first 30 days: helping teachers adopt a new platform

This plan is for the principal or academic head who has decided to adopt a platform after piloting it in a few classes and now has to bring the rest of the staff along. Thirty days is enough to get the platform working in classrooms, as long as each week asks for one clear thing.

The Education Endowment Foundation's guide to implementation in schools, in its second edition (December 2019), names two things that can sink any change in a school: the change becomes an “add on” task on top of the day-to-day work and fades as priorities compete, and teachers applying it for the first time feel awkward and “incompetent”, experienced ones included. In The Decision Lab's 2022 study of more than 225 edtech decision-makers in US school districts, as reported in an EdSurge article sponsored by ISTE (June 2024), a lack of buy-in from the people involved and resistance to change are among the barriers at the purchase stage. The plan below is built on that: one small task each week, and for every new job, an old one that stops.

Definition

Teacher adoption of a platform: Teachers using the platform in their real work with students without being reminded — not each of them having an account or attending a training session.

Week zero: what to set up before teachers start

• A list of what stops. For every job the platform takes over, an old task stops on the same day. If the weekly quiz moves to the platform, do not also ask for a paper copy in the teacher's file. The EEF guide asks a plain question at the preparation stage: what can we stop doing to create the space, time and effort for the new work? Write your answer down and announce it at the first meeting.
• A champion in each department. Choose someone colleagues trust and already go to with questions, not necessarily the most technical person. The same guide suggests recruiting the school's opinion-leaders, and advocates who champion a change by modelling it and helping others use it. We suggest relieving each champion of one duty a month in return for their time.
• Accounts ready and tested. Each champion logs in with an ordinary teacher account and does all four weeks' tasks before colleagues do. A fault one champion finds alone is a fault a whole department does not find in the middle of a lesson.
• Twenty protected minutes a week. Take them from a meeting that already exists, such as the department meeting. Do not add a new one.
• One support channel. One person or one group for questions, and a promise of an answer the same day.
• One sentence on why. Why this platform, and which problem it solves in this school. The sentence written at the start of the pilot will do.

The plan, week by week: one task each week

Why one task a week? Because training alone, the EEF guide says, is unlikely to be enough to change what a teacher does in class; it needs follow-on support inside the school, and the guide names coaching and mentoring that provide ongoing modelling, feedback and support. A small task makes that support possible: each week the champion knows what to ask about, and the teacher knows exactly what is expected.

Note the order of weeks one and two: teachers make something on their own before they stand in front of a class with it. We put them in this order because, in our view, the awkwardness the guide describes is lighter in front of a screen than in front of thirty students.

The one number to watch every Thursday

Watch the share of teachers who used the platform for a real lesson this week, out of all the teachers the plan covers. This is a number we suggest, not a published standard, and we choose it because it measures what you actually want: the platform reaching the classroom.

• Counts: a quiz students answered, a worksheet printed and handed out in class, slides used in a lesson, homework that reached students.
• Does not count: logging in, anything made in the training session, material that never reached students.

Collect it the simplest way: the champion asks colleagues one yes-or-no question every Thursday, or you read it from the platform's usage report if that report separates what was made from what reached students. The EEF guide notes that simple, quick measures find more acceptance among staff than complicated ones, and that clear, achievable short-term measures show the early signs of success.

Show the number by department, never by teacher name; the point is to see where support is needed, not to announce who is behind. We know of no published benchmark for this share, so what matters is its direction week on week. If it stays flat or falls in a department for two weeks running, sit down with that department's champion before you add any new task.

How to hear objections without starting an argument

You will hear objections, and some of them will be right. The EEF guide separates technical problems, which a school's usual routines can solve, from unfamiliar ones that need dialogue, involvement, negotiation and an answer worked out with the people concerned. So hear the objection first, then sort it.

1. 1

   Collect objections in writing, in one place

   A sheet or a form that reaches the champion and the principal together. An objection voiced in the corridor and never written down is never fixed or answered.

2. 2

   Sort each objection into one of four kinds

   A fault fixed within days; a training gap the champion closes with a short session; a real cost, meaning the platform added work, which is only solved when something else stops; or a question that needs a written answer.

3. 3

   Spend ten minutes with the most doubtful teacher

   Ask: what would make this worth your time? Then write the answer down. The doubtful see what the enthusiasts miss.

4. 4

   Answer every objection within a week, in writing

   Say what changed because of it, or why nothing did. Silence reads as a no.

5. 5

   Keep objections out of the whole-staff meeting

   That meeting is for the next task and the number. Objections are discussed with the person who raised them, or in the department meeting.

When thirty days is not enough

• Thirty days is a start, not full adoption. The EEF guide asks schools to plan for sustaining a change from the outset, and to take regular “pulse checks” so the strain of implementation does not wear down the school's readiness. At the end of week four, write the task for month two, and keep the Thursday number.
• If after three weeks the number is still only the champions, do not add a task. Look for the cause in the task and in the platform before you look for it in the teachers, and go back to the problem log and to what the doubtful teachers said.
• A platform does not save everyone time. In a Gallup and Walton Family Foundation survey of 1,952 US K-12 educators, published on 14 October 2026, 29% of those who used AI tools in the 2025–26 school year said it made no difference to their time, and 7% said it cost them time. Those figures are about AI tools in the US, not about your platform, but the lesson holds: measure the time yourself, as in how to measure the teacher time a tool really saves.
• A mandate does not replace a plan. You can require everyone to use the platform, but what brings it into the classroom is the small task, the support close at hand, and the old task that stopped. If you have not yet settled between one platform and several tools, start with one platform or many tools: how a school decides.

Written with String's editorial team: we use AI for research and first drafts, and a person checks every fact and every source before anything is published. How we write