Most of the platforms I’ve built optimize for something abstract — conversion, engagement, transaction volume. Building the learning management system for Doyen Academy optimized for something I could actually picture: a specific teacher, grading fewer things manually, going home earlier.
That’s a rare kind of client work, and I noticed how much it changed my own energy for the project.
The actual product problem
LMS platforms fail teachers constantly — too many clicks to grade an assignment, reporting that answers questions administrators care about instead of ones teachers do, mobile experiences that assume a classroom has reliable broadband. I sat with actual teacher workflows before writing a line of the grading module, watching how someone actually moves through marking thirty assignments in a free period between classes.
What I built differently because of that
A grading flow that keeps a teacher in one continuous keyboard-driven motion instead of clicking in and out of records. Offline-tolerant sync for the reality of Nigerian school connectivity, not the fantasy of a always-on fiber line. Reports that surface “which students are actually falling behind” front and center instead of burying it under vanity metrics nobody in a classroom asked for.
Why this one felt different
I keep coming back to something I believe past the point of being able to fully explain it in secular terms: education is one of the few places software gets to genuinely serve people instead of extract from them. Building tools that make a teacher’s Tuesday afternoon less brutal isn’t glamorous work. It’s some of the most honest work I’ve done — closer, I think, to the kind of quiet service I actually want my career to be known for, not just the flashy fintech logos.
Doyen Academy’s teachers will never see my name in the changelog. That’s fine. I know what got easier for them, and that’s the part that was ever actually the point.