Why Most EdTech Pilots in New Zealand Schools Quietly Fail — and What No One Reports Back

Most EdTech pilots in New Zealand schools don’t fail in the boardroom. They fade in the staffroom — three weeks after launch, when the demo energy has worn off and no one has been told what comes next.

Few schools admit this publicly. Even fewer write a post-mortem.

What schools think is happening vs what is actually happening

What schools think is happening: A capable platform was selected, teachers were trained, students were given access, and adoption is now a matter of momentum.

What is actually happening: Adoption never had ownership. The pilot was scoped to a deadline rather than to an outcome. A handful of teachers logged in once. Students never returned. The data is too thin to call it a success or a failure — so the school quietly moves on to the next initiative.

Nobody reports this back. There is no formal post-mortem. The platform is slowly forgotten, and the next year, a similar pilot starts somewhere else in the same school.

Why this keeps happening

The pattern is not about effort or intention. It is about structure.

• No single owner. Nobody is explicitly accountable for sustained usage past week three.
• Implementation as an IT task. Schools treat the rollout as technical setup rather than an academic project that needs change-management.
• Wrong success metrics. “Did teachers like the demo?” replaces “Did Year 11 outcomes shift?”
• Vendor-led decision-making. Pilots are shaped by what the platform looks like in a polished walkthrough, not what the staffroom can sustain on a Tuesday afternoon.
• No protected time. The pilot is added on top of full timetables, parent evenings, NCEA reporting and CIE marking weeks.

When EdTech is bought without an operating model around it, even strong tools quietly die.

The consequences

The cost shows up — usually invisibly.

• Teachers add another login, another platform, another marking layer. Workload silently grows while leadership talks about “transformation”.
• Budgets are spent without measurable academic outcomes. Boards are told the pilot was “useful.” Nothing changes in the next budget cycle either.
• Students sense that the platform is optional. Engagement collapses, then becomes evidence the platform “didn’t work.”
• Leadership becomes cautious about the next EdTech decision. Genuine progress slows.
• Trust between teachers and “the next tool” erodes a little more each year.

This is the part that rarely makes it into a board paper.

What actually works

Schools that get sustained value from a pilot tend to build the implementation deliberately, not enthusiastically.

1. Define the academic problem first. Not “we want to try AI.” Instead — “Year 11 cohorts are missing 14% of past paper coverage” or “marking turnaround in NCEA Level 2 maths is 9 days too long.”
2. Assign one internal owner. Usually a Head of Department or Director of Studies, not the IT lead. The owner protects the pilot through the inevitable mid-pilot dip.
3. Set the success metric before the pilot starts. Engagement minutes, marking time saved, intervention triggered, topic improvement — pick what matters and commit on paper.
4. Build a 12-week routine, not a launch event. Weekly teacher review, fortnightly leadership check-in, and an explicit go / no-go decision at week 12.

This shifts a pilot from a trial to a project — and a project is much harder to quietly forget.

A note from working with schools

In our work with schools across New Zealand and the wider Asia-Pacific region, the difference between a pilot that sustains and one that quietly dies is rarely the platform itself. It is almost always whether someone owned the implementation and whether the school was prepared to keep that ownership through the first uncomfortable months — when the novelty has gone but the routine has not yet formed.

The schools that get this right look almost boring on paper: a clear problem, a single owner, a small pilot group, and a calendar of review checkpoints. That is the playbook.

If this sounds familiar…

If your school is currently exploring EdTech — or trying to make sense of a platform that is technically live but is not yet part of teaching and learning — it may be worth stepping back to evaluate the structure behind it.

We regularly work with New Zealand schools to:

• Assess what is working and what is not in current implementations.
• Define realistic, measurable success metrics.
• Structure adoption in a way that survives the first 12 weeks.

This is not about recommending a platform. It is about helping schools make the right decision for their context.

A short conversation

If this is something you’d like to explore further, we’d be happy to have a short consultation — just to understand your current setup and share a structured perspective on what is and isn’t working.

From there, if there is alignment, we can also explore how platforms like AI Buddy can be implemented alongside the right academic and operational support — so the next pilot in your school doesn’t quietly disappear like the last one.