What actually happened when I sat down to review this interview
I found myself spending more time on the Costa Sarantakos interview than I expected. It came up again in my feed and I figured it would be another generic ed-tech puff piece. It wasn't. The discussion around how distance learning infrastructure actually gets built, and the kind of institutional friction that makes or breaks these programs, is something you rarely see outside of internal project meetings. That's partly why I kept going back to it. The interview covers several areas that matter if you're trying to set up or improve a distance learning program. Sarantakos talks about the gap between what institutions claim they're doing and what actually shows up in student completion rates. He references his own early work at the University of Nicosia, where the Open University model was being tested against traditional delivery. The key takeaway from that section isn't a theory. It's that the architecture of the learning management system matters less than the administrative workflows around it. You can run the best LMS in the world and still fail if your registration, proctoring, and credit transfer processes are paper-based. I remember running into this exact problem when our department tried to migrate a hybrid course to fully online during the 2020 transition. We had invested in a solid platform. The content migrated fine. What broke was the advising pipeline. Students who relied on walking into an office got lost. We ended up building a simple routing script in Python that flagged at-risk enrollments based on login frequency and assignment submission windows. It wasn't elegant. It worked. The interview touches on this kind of operational reality without getting bogged down in it, which is probably why it's worth reading rather than skimming.
What the interview gets right that others miss
Most distance learning coverage focuses on technology. Sarantakos keeps coming back to policy and access. He discusses how accreditation standards don't translate well across borders and how that creates a hidden barrier for students in certain regions. This isn't a small detail. It's the reason some programs look successful in one country and collapse in another even with identical technology stacks. There's also a section on assessment integrity that doesn't fall into the usual fear-mongering. He argues that remote proctoring software creates more fraud vectors than it eliminates because it's designed around suspicious behavior detection rather than learning outcome validation. I've seen institutions spend six figures on surveillance tools and get worse completion rates. The alternative he suggests is design-first assessment: structure courses so that cheating is unnecessary because the work can't be completed by someone else without obvious skill mismatch. It's harder to implement but cheaper and more honest.
Where the interview falls short
Not everything lands. The piece doesn't dig deep enough into faculty resistance as a structural problem. You can have the best policy framework and still face instructors who see distance learning as second-class or as extra work without recognition. I've been in meetings where this was the actual blocker, not technology or funding. The interview mentions it briefly but doesn't offer concrete mechanisms for addressing it beyond cultural change arguments. Another gap is the cost discussion. Sarantakos frames distance learning as cost-effective but doesn't walk through what that looks like at scale for underfunded institutions. A well-resourced university can absorb the upfront investment. A community college or a program in a developing region cannot, and the interview doesn't really address that divergence. If you're reading this looking for a blueprint to copy, you'll leave slightly disappointed. It's more of a landscape analysis than a how-to manual.
Get the Full Details
How to use this material practically
Take the accreditation section seriously if you're planning cross-border enrollment. Check whether your target institutions have reciprocal agreements before investing in marketing or platform customization. The compliance paperwork alone can add three to four months to a launch timeline if you're not prepared. If you're evaluating LMS options, stop looking at feature checklists. Look at how each platform handles grade passback to student information systems and whether it supports the assessment types your discipline requires. I've watched teams pick a platform based on UI reviews and then spend two years building integrations that should have been native. That interview reinforces that point without needing to spell it out. The assessment design ideas are the most actionable part. Start by mapping every graded component in your course and asking whether it could be completed by someone with a fundamentally different skill set. If the answer is yes, redesign it before you worry about proctoring software. This approach cuts monitoring costs and usually improves actual learning outcomes at the same time.
I've shared the interview link with colleagues who were considering a full pivot to online delivery. Some of them found it frustrating because it doesn't give a step-by-step answer. That's fair. But the frustration comes from expecting a checklist from something that's really a strategic overview. If you read it that way, it saves you from making the kinds of mistakes I've seen repeated across multiple institutions over the past decade.
.png "World Distance Learning Day")
