Ethiopia's edtech problem is not access. It is fragmentation.

For a decade the story about technology in Ethiopian education was a connectivity story. Not enough network, not enough devices, not enough electricity. Much of that is still true in places. But it is no longer the binding constraint, and continuing to talk as though it is has become a way of avoiding a harder conversation.

Read that table carefully, because it holds two opposite truths. Coverage is broad and mobile data use is now at fifty million people. And smartphone penetration is around 15%, with women at 6%. A product that assumes a smartphone in every parent's hand is designing for a minority. A product that assumes no reachable network is designing for a country that no longer exists.

Shega's reporting on Ethiopian edtech names the problem plainly. Implementation remains fragmented. Entrepreneurs navigate a maze of government offices across education, ICT and finance to certify content and register platforms. Ministries and institutions launch parallel initiatives without shared frameworks or interoperable data systems, producing duplicated effort and stretched resources.

Inside a school this shows up as something very concrete. Attendance lives in one system. Fees live in a spreadsheet. Marks live in paper marklists. Report cards get typed again from those marklists. The regional bureau wants a report in its own format, so somebody types the numbers a third time. Each transcription is a chance to introduce an error that nobody will ever trace.

The intent exists on paper and is reasonably well specified. Ethiopia's education partnership documents call for a fully digitised Education Management Information System, accessible through web applications on computers, tablets and smartphones, with track-and-trace so that students and teachers carry unique identifiers. They also call for EMIS to integrate with GIS, SMIS and TMIS so the systems can read across each other.

Alongside that, examination administration is being digitised. UNOPS and the Ministry of Education signed a $2 million project to build a national examination administration system, and the Digital Ethiopia strategy has carried education workstreams including digitalised student assessment.

The gap is not vision. It is that unique identifiers and read-across integration are exactly the things that fail when each initiative is procured separately, on its own schedule, with its own data model.

If you run a school, you cannot fix national coordination. You can refuse to buy into the problem. These are the questions that separate a system you can leave from a system that owns you.

The argument being made across Ethiopian edtech commentary is for cohesion: shared standards for what a student record contains, how identifiers work, and how systems exchange data, so that a school's choice of software stops determining whether its data can ever be read by anyone else.

That is not a technically hard problem. It is a coordination problem, which is harder. Until it is solved centrally, the practical defence available to an individual school is to buy systems that assume they might one day be replaced, and to treat any product that makes leaving difficult as a liability rather than a feature.

This article was last checked on 9 August 2026. Exam windows, fees and policy move, so if you are reading it much later, treat the dates as a starting point and confirm them against the sources below.