Lead a teacher usage review after a pilot

A pilot ends and everyone wants one number that tells them what happened. Usage data gives you that number, but a login count or a weekly active percentage never explains a classroom. Your job as the account executive is to walk into the usage review with the data, the teacher accounts, and the criteria the district agreed to at the start, and use all three to help the school decide what to look at next.

Why this conversation goes wrong

A usage review turns bad the moment someone treats one metric as a verdict. A superintendent sees that only half the pilot teachers logged in weekly and calls the pilot a failure before anyone asks why. A principal sees a high login count and calls it a success before anyone checks whether teachers used the tool the way it was designed. Both reactions skip the same step. Neither person asked what the number actually measures or what conditions produced it.

You feel pressure to let the easy read stand. A quick verdict closes the meeting and gives everyone a clean story to tell their board or their staff. But a verdict built from one chart ignores the fact that two schools may have run the pilot under different schedules, with different training, and different levels of principal support. If you let the room settle on the wrong explanation, the district makes its renewal decision on bad information, and you inherit the consequences at the next contract conversation.

How to prepare

Walk into the meeting with the usage report, but do not walk in with only the usage report. Pull the weekly active numbers by school, not just the district average. A single blended number hides the fact that one school used the tool three times as often as another. Pull the support log too. Note which schools got a live training session, which got a recorded video, and which got nothing beyond a login email.

Talk to your implementation contact before the meeting and ask what teachers said in office hours or support tickets. Write down the actual complaints, not a summary of them. "Teachers wanted more examples" is vague. "Three teachers said the sample lessons did not match their grade level" is something the room can act on.

Reread the evaluation criteria the district agreed to when the pilot started. Most pilots set a goal like weekly use in most classrooms, or a specific skill improvement teachers could observe. If the room does not have that document in front of them, they will grade the pilot against whatever number is easiest to remember, which is usually the wrong one.

What to say

Assistant superintendent Val opens the meeting by asking, "Only half our pilot teachers used the tool each week. Does that tell us the pilot failed?"

Account executive Mina answers, "That number is a starting point, not an answer. Before we call it a failure, I want to know what made regular use easier for some teachers and harder for others. What did teachers tell your team?"

Val says two of the four pilot schools lost planning time to testing during the pilot window, and several teachers asked for more example scripts before they felt comfortable running a live session.

Mina asks, "Did the pilot group agree on a shared weekly target, or did each teacher set their own pace?"

Val admits expectations were never lined up across schools. Some principals told teachers to use it twice a week. Others left it open.

Mina responds, "Then the fifty percent figure is really an average of two different pilots running under two different sets of expectations. Let us break the usage numbers out by school, add the support each school received, and put both next to the goals your team wrote down at the start. That gives us a real basis for deciding what to fix before you decide whether to continue."

Notice what Mina does not do. Mina does not defend the product. Mina does not argue that fifty percent weekly use is actually a normal result for a pilot. Mina asks for the second layer of information the raw number cannot supply, and asks Val to supply it, because Val is the one with access to what actually happened inside the schools.

Mistakes to avoid

Do not defend the number. If you jump to explaining why fifty percent weekly use is normal for a pilot, you sound like you are protecting the sale instead of helping the school understand its own results. Ask questions before you offer any interpretation.

Do not accept the first explanation either. If a district leader blames low usage entirely on teachers, ask about training and schedule constraints before you agree. The honest explanation is usually a mix of causes, and your job is to help the room see the mix, not just the first one someone names.

Do not run the review alone. Bring your implementation contact if you have one, and ask the district to bring a teacher who was actually in the pilot along with a curriculum lead. A usage review without a teacher in the room is a meeting about teachers held without one present, and it produces weaker conclusions.

Do not let the meeting end without a specific next step. A vague agreement to look into it further wastes the work you just did pulling school level data. Leave with one clear question the next phase needs to answer and a name attached to who will answer it.

How to practice and score it

Pick one usage chart from a real or recent pilot and write three questions that chart cannot answer by itself. A weekly active percentage cannot tell you why usage varied, whether the schools had equal support, or whether the teachers who did not log in even received training. For each question, name the person in the district who could actually answer it.

Then run the scenario as roleplay. Have someone play a buyer who wants to call the pilot a success or a failure based on one metric, and practice steering the conversation back toward the agreed criteria and the evidence that is actually available. Score yourself on whether you asked before you explained, whether you separated the data by school instead of accepting a blended average, and whether you left the meeting with one clear next question instead of a closed verdict.

Education practice conversations cover this kind of review alongside related conversations an account executive runs during a pilot, including how to Discover the work behind a technician pipeline request when a rollout depends on IT capacity, and how to Help a student plan for textbook access when adoption questions reach the classroom level. Running the review inside DealSpeak lets you rehearse the exact moment a buyer reaches for a single number, before you face it with a district that is deciding whether to renew.

Where this leaves the pilot

A good usage review does not hand the district a verdict. It hands them a short list of what to check next and who should check it. Do that consistently and the renewal conversation gets easier, because nobody is arguing about whether one number was allowed to speak for the whole pilot.