Loading article…
I have onboarded schools in Kigali, Musanze, Rubavu and Huye. Here is the actual day-by-day playbook — what works, what fails, and the one mistake almost every school makes in week one.
I've onboarded schools in Kigali, Musanze, Rubavu, and Huye. Some have gone smoothly. Some have been hard. The difference between the smooth ones and the hard ones is almost never about the technology — it's about a few decisions made (or not made) in the first three days.
This post is the playbook. It's the same one I send to head teachers and deputy heads when they ask “where do we start.”
Pick one person to own the rollout. Not a committee. Not “the IT department”. One named human being with the authority to make decisions and the time to actually do it.
In every successful rollout I've been part of, there was a single owner. In every failed rollout, there was no owner. Usually the owner is the deputy head, the head of academics, or the ICT teacher. Sometimes it's an enthusiastic class teacher. The role matters less than the fact that someone is responsible.
If your school can't identify an owner, don't start the rollout. Wait until you can.
The owner sits down with the head teacher and locks down five things:
This is the “technical” day. Most platforms (Ganzaa included) handle the heavy lifting. The school provides:
By end of day 2, every account exists in the system. Each teacher should be able to log in and see their classes. Don't move on until this is verified — “we'll fix the missing accounts later” is the start of every painful onboarding.
One-hour session per grade. Maximum five teachers per session — bigger than that and you lose the room. Cover four things and only four things:
That's it. Don't try to teach everything the platform does. The other 80% they'll figure out by using it. Trying to cover every feature in the training session is the second-most-common mistake in school onboarding (the first is no owner).
One thing I've learned: have at least one student demo the platform during the training. It's reassuring for teachers to see that a 15-year-old already finds it intuitive. It also signals that the platform isn't something teachers need to be the “experts” on.
Yes — students. Pick two per class who are tech-confident and well-liked by their classmates. Train them in 15 minutes. They become the in-class help desk.
This is the highest-leverage habit I've discovered for school adoption. When a classmate has a login issue, the student helper sorts it out in 30 seconds instead of paging the teacher. The teacher never gets interrupted. Adoption is faster.
The student helpers also become advocates. They tell other classmates “this thing is actually useful”, which is worth more than any teacher saying it.
Don't switch the entire school over at once. Pick one subject — math is the best first choice because the right/wrong answers are unambiguous — and run it for a week.
That week, the rule is: 30 minutes per day, in class, all students at once. The teacher walks around, helping kids who get stuck. At the end of the week the teacher pulls the class report and sees who did what and who scored what.
By week 2, you can add a second subject. By week 4, three. By week 6 the platform is part of daily routine and no one questions it.
The pattern I've seen across 15+ school rollouts: weeks 1–2 are bumpy (login issues, kids forgetting passwords, the WiFi being slow), week 3 hits a usability inflection point, and by week 4 teachers are using it without thinking. If you can survive the bumpy weeks 1–2, the rest is downhill.
They over-communicate to parents.
The default instinct is to send a long, detailed letter explaining the platform, the schedule, the login process, the privacy policy, the technical requirements. Don't. Send the shortest possible message.
The message that works in Rwandan schools, in my experience:
“Mwiriwe. We're piloting an online learning platform for [grade] starting Monday. It's free for the first term. Your child will use it for 30 minutes/day in [subject]. You'll get a weekly progress report by SMS. Reply with questions.”
That's it. You'll get five questions back. You'll answer them once. You're done. Anything longer than that gets ignored.
I want to be honest about this. Not every rollout I've been part of succeeded. Three patterns I've seen in the failures:
Most platforms targeting Rwandan schools — Ganzaa included — offer the first term free, no commitment. Per-student pricing afterward varies. For Ganzaa it scales down with volume; a school of 800 students pays a different per-student rate than a school of 80.
The free first term isn't a marketing trick — it's the practical reality that schools need to see results before committing budget. If you go through Ganzaa's school onboarding, the first term genuinely costs zero.
The schools I've worked with that committed to the playbook above typically see, within one term:
None of these are guaranteed. They depend on the rollout being done well.
If you're a head teacher or deputy head reading this, the next step is a 30-minute call. Book a school demo and we'll walk through your specific situation — your grades, your devices, your timeline. The call is free; the first term is free; the worst that happens is you decide it's not for you.
The hardest part of e-learning rollout in Rwanda isn't the technology. It's the decision to start.
I've tested the major learning apps available to Rwandan students. Here is the honest, opinionated review — what works, what doesn't, and what to skip entirely. With my biases declared up front.
S3 is the second turning point in a Rwandan student's life. Past papers are the highest-leverage tool you have — and most kids use them completely wrong. Here is how to do it right.
Ganzaa is Rwanda's online learning platform — free for individual students, with REB-aligned practice and past papers. Schools get the first term free.