E-learning apps solved half a problem

The pitch for most education software is a library. Thousands of lessons, a video for every topic, a quiz at the end of each one. It is a real improvement on a textbook, and it has a shape that is easy to sell.

It is also only half of what a school does. A school is not a content pipeline. It is an organisation with a timetable, a roster, thirty-eight teachers, three hundred students, a department structure, and a term that ends whether or not anyone was ready. The moment a lesson is delivered, four questions appear that a content library cannot answer.

A class run on GoodJob, from the roster to the report

The four questions after the content

Did the class actually run?
Not "was it scheduled". Who opened it, who taught it, who was in the room or on the call — and what happened to the students who were not.
Who fell behind, this week?
A mark at the end of term is a post-mortem. A teacher needs the twenty-eight names in front of her and the two that stopped three lessons ago.
What does that mean one level up?
A department head cannot read six hundred lesson records. She needs the shape of the department: who is carrying what, where the quiet classes are.

Answer these and you are running a school. Answer only the content half and you are running a video library.

Motivation is not a feature you bolt on

The second thing a library misses is why anyone would come back on a Wednesday night. Motivation is not a motivational quote on a login screen. It is the feeling of a number moving because of something you did, a streak that is worth not breaking, a class that can see itself finish a unit together.

This is why we treat progress as evidence rather than decoration. A card counts when the work is done, not when the page was opened. A lesson shows 15 of 19 because that is the truth, and a student who is told the truth can act on it. Encouragement that is not connected to the work stops working by the second week.

2systems

learning and the management of learning, kept in one record instead of two products that never meet

5views

student, teacher, department head, school administrator and parent — each reading the same evidence at their own altitude

languages, because a Vietnamese university department and an international one should not need different software

What we chose to build instead

GoodJob started from the school rather than the course. Classes, rosters, attendance, who teaches what, which department owns which subject, and how a run of a course actually happens — and on top of that, the lesson itself, counted card by card, with the teacher and the head of department looking at the same numbers.

That choice makes the product less impressive in a demo and considerably more useful in September. It also means the platform has to be honest about a lesson that is not finished, and that a teacher's report has to show the class that has gone quiet even when nobody asked.

Content is the easy half, and it is already commoditised. The half that decides whether a semester works is the one nobody wants to build: the roster, the follow-up, and the number that tells the truth.

Source: GoodJob platform documentation and deployment experience, November 2026.

Contact: [email protected]