What teachers actually want from a school management app

When we started building Tetademic, we assumed we knew what teachers wanted from school management software. We were wrong about several things.

We interviewed 60 teachers across Lagos, Ibadan, and Abuja — primary and secondary, public and private, experienced and newly qualified. We asked open questions: what takes the most time in your administrative work? What do you wish you could do faster? What has frustrated you about software you have used before?

The answers were not what we expected.

What we expected to hear

We expected teachers to ask for better analytics, more detailed student performance tracking, and richer communication tools. These are the features that appear in most school management software marketing materials, and we assumed they reflected genuine teacher demand.

They did not come up much.

What teachers actually said

"I just want to enter scores once." This was the most common theme. Teachers described entering the same scores in multiple places: their personal record book, the class mark sheet, the exams officer's spreadsheet, and sometimes a separate system for continuous assessment. Every additional entry point is another opportunity for error and another demand on time that teachers do not have.

"I want it to work on my phone." Most teachers do not have a dedicated work computer. They use their personal smartphones for everything, including school administration. Software that requires a laptop or a fast internet connection is software that does not work for most Nigerian teachers. The request was not for a mobile app with full feature parity — it was for a mobile experience that handles the core tasks: entering scores, taking attendance, viewing the timetable.

"I want to know when something is due." Teachers described missing deadlines not because they were disorganised but because the deadline was communicated once — in a staff meeting or a printed memo — and then forgotten. A simple notification system that reminds teachers when score entry is due, when reports need to be submitted, and when parent meetings are scheduled would, in their words, "remove so much stress."

"I don't want to learn a complicated system." Several teachers described previous experiences with school management software that required training sessions, had confusing navigation, and felt like it was designed for an administrator rather than a classroom teacher. The request was for something that could be used without a manual — where the task you need to do is obvious from the screen.

"I want to see my students' history." This surprised us. Teachers wanted to be able to look at a student's performance across previous terms — not for complex analysis, but for simple context. "If I know this student was strong in maths last term and is struggling now, I want to know that before I call their parents." This is a pastoral care use case, not an analytics use case.

What teachers did not ask for

Almost no teacher mentioned dashboards, charts, or data visualisation. The teachers who had used systems with these features described them as "nice to look at" but not useful in their daily work.

Very few teachers asked for parent communication features. This was not because they do not value parent communication — they do — but because they see it as the school's responsibility, not theirs individually. They want the school to communicate with parents; they do not want to manage that communication themselves.

Nobody asked for gamification, badges, or student engagement features. These are popular in edtech products aimed at students, but teachers were clear that their job is teaching, and they want administrative software that supports that — not software that tries to be a learning platform.

What this means for software design

The teachers we spoke to are describing a very specific kind of software: fast, mobile-first, focused on the tasks they actually do (score entry, attendance, timetable), and reliable enough that they trust it to hold their data.

They are not describing a platform. They are describing a tool.

The distinction matters. A platform tries to do everything and ends up doing many things adequately. A tool does a small number of things very well. For teachers, the small number of things that matter are: entering data once, seeing it reflected immediately, and being reminded when something is due.

The trust question

One theme that cut across all 60 interviews was trust. Teachers described previous experiences where data they had entered disappeared, where the system was unavailable during exam season, or where scores they had entered were overwritten by someone else. These experiences had made them cautious about relying on any software for records they considered important.

Building trust with teachers means being reliable above all else. A system that is available when they need it, that saves their data correctly, and that does not surprise them with unexpected changes is more valuable to a teacher than any feature on a product roadmap.