The Implementation Gap: Why Buying EdTech Is Easy — But Making It Work in New Zealand Schools Isn't

Most New Zealand schools can buy an EdTech platform in a single board meeting.

Embedding it into teaching takes a year. The space between those two timelines is where most of the value of EdTech is quietly lost.

What schools think is happening vs what is actually happening

What schools think is happening: The hard part of EdTech is selecting the right vendor. Once that’s done, implementation is largely a deployment task.

What is actually happening: Selection is the easy part. The hard part starts the day after the contract is signed — and almost no school has explicit ownership for it.

The platform goes live. Teachers receive training. Students get accounts. And then nobody is responsible for the messy 90 days that follow, when routines need to actually form, workflows need to actually shift, and students need to actually return.

That 90-day gap is the implementation gap. It is where adoption either takes root or quietly dies.

Why this keeps happening

The implementation gap exists because schools are organised around teaching, not around change management.

• Procurement is well-defined; implementation isn’t. Every school knows how to evaluate, contract, and onboard a vendor. Few have a defined operating model for embedding a tool into the academic week.
• The decision-maker is not the implementer. The senior leader who signs the contract isn’t the one shaping the Year 10 routine on a Wednesday afternoon.
• Implementation responsibility is split. IT owns the technical setup, the curriculum lead owns the academic side, department heads own delivery. Nobody owns the integration in between.
• No protected time exists for the transition. Teachers are expected to absorb the new platform into a year that’s already fully scheduled.
• Success metrics aren’t anchored to the implementation. “Did teachers attend training?” replaces “Did teaching change?”

This is why even excellent platforms can produce disappointing outcomes — the school never closed the gap between buying and embedding.

The consequences

Implementation gaps don’t make headlines. They make the next budget conversation harder.

• Tools are bought, partially used, and quietly renewed because nobody wants to admit it didn’t land.
• Teachers carry the implementation burden informally, on top of full timetables.
• Students experience the platform as an add-on rather than as part of how learning happens.
• Department heads stop volunteering for the next pilot. Every new tool has a tax they end up paying.
• Senior leadership runs out of internal credibility for EdTech investment, even when the next platform might be the right one.

The frustration becomes general — “EdTech doesn’t work in our school” — when the issue is specific. Implementation never had a structure.

What actually works

Schools that close the gap tend to treat implementation as a project with the same rigour as a curriculum review.

1. Name an implementation owner before signing. A single person — usually a Director of Studies or Head of Department — accountable for outcomes, not just deployment.
2. Plan the first 90 days, not the first week. Map what teachers should be doing in week 4, week 8, and week 12. The launch is the smallest part of the plan.
3. Build review checkpoints into the calendar. Weekly within the pilot group, fortnightly at department level, monthly at SLT. Implementation that doesn’t get reviewed doesn’t survive.
4. Tie success metrics to teaching change, not access. Logins are a hygiene metric. The real question is whether marking time fell, whether feedback turnaround improved, whether intervention started earlier.

This isn’t more work than what schools already do. It is the work that should have been done at the start.

A note from working with schools

In our work with schools, the single most reliable predictor of EdTech success is whether someone is named, in writing, as the owner of implementation — and whether that person has 90 days of protected attention to focus on it. Without that, even strong tools tend to underperform. With it, even modest tools tend to deliver real outcomes.

Implementation isn’t a soft skill. It is a structural choice the school makes — usually before the contract is signed.

If this sounds familiar…

If your school is about to bring in a new platform — or is sitting on a tool that’s technically live but isn’t yet shaping teaching — it may be worth stepping back to evaluate the implementation structure before anything else.

We regularly work with New Zealand schools to:

• Define implementation ownership before procurement closes.
• Build a 90-day adoption plan tied to teaching change, not access.
• Set review routines that catch drift before it becomes drop-off.

This is not about pushing a particular platform. It is about helping schools make implementation a structured, repeatable practice rather than an unmanaged side-effect of buying.

A short conversation

If this is something you’d like to explore further, we’d be happy to have a short consultation to understand your current setup and share a structured perspective on where the implementation gap is opening up.

From there, if there is alignment, we can also explore how platforms like AI Buddy fit alongside the right academic and operational support — so the next implementation closes the gap instead of widening it.