A learning system should be judged partly by how it treats the possibility that a learner will leave it.
That is an uncomfortable question for institutions and platforms alike. Retention is easy to measure. Continued use can look like satisfaction. A learner who stays may indeed be finding value.
But staying is not the same as being well served.
People change schools, jobs, communities, devices, languages, and circumstances. They outgrow a program. They need a pause. They discover that another setting fits them better. Sometimes they leave because a system has failed them. None of those possibilities should require them to abandon the evidence of their effort or the ability to make sense of what they have learned.
The provisional claim is simple: a learning system should help learners leave with more agency than they had when they entered.
What should travel with the learner
At the most basic level, learners should be able to take their work with them: writing, projects, feedback, records of progress, and the sources that shaped an inquiry. But portability is not only a download button.
A folder of files can be useless when it has no explanation. A score can be portable while the reasoning behind it remains hidden. A recommendation can follow a learner without giving them any way to understand, contest, or build on it.
What matters is intelligibility. Can the learner explain what they worked on, what feedback they received, what they revised, and what remains uncertain? Can a future teacher, mentor, employer, or collaborator understand enough to respond well? Can the learner correct an error or ask for a different account of their progress?
These are not merely technical questions. They are questions about dignity. A person should not have to remain inside one organization’s interface to make their own learning legible.
Dependency can hide inside convenience
Convenience has real value. A platform that remembers context, organizes materials, and offers timely support can reduce friction for learners who already face too much of it. Shared tools can make a community’s work easier to sustain.
But convenience can turn quietly into dependency when the system becomes the only interpreter of a learner’s history. If the only meaningful record is a proprietary dashboard, departure becomes costly. If feedback cannot be understood outside a product, the learner’s next teacher inherits a blank slate. If an AI assistant’s memory is the only place a learner’s questions have accumulated, the learner may lose not just data but a developing account of their own thinking.
The answer is not to reject useful tools or demand that every learner manage complicated records alone. Some people need more structure, more continuity, or more assistance to navigate transitions. A requirement that every record be self-managed can become another barrier.
The better aim is supported portability: systems should make it practical for learners to carry forward what matters, with help when they need it and clear limits on what cannot responsibly travel.
Leaving can strengthen relationship
This may sound like an argument against commitment. It is not.
Healthy relationships do not hold people by making departure impossible. A good teacher wants a learner to carry a question beyond the classroom. A good mentor hopes their guidance becomes less necessary over time. A strong community can remain meaningful even when someone moves away, changes roles, or chooses a different path.
Institutions can work the same way. They can offer continuity without claiming ownership. They can preserve a learner’s record while protecting privacy. They can make handoffs thoughtful rather than bureaucratic. They can invite people back without making return the only condition for belonging.
AI systems raise this question sharply because they can create a powerful sense of continuity. They can remember preferences, summarize a history, and become the easiest place to ask for help. Those features can be valuable. But a learner should be able to see what the system knows, revise it, export what is appropriate, and continue learning with people and tools beyond it.
No system can make every transition seamless. Privacy, safety, consent, and the needs of other people set real limits. Some records should not move freely. Some context loses meaning when removed from its community. Portability must never become a pretext for exposing sensitive information or flattening a learner into a transferable profile.
Still, those limits strengthen rather than weaken the question: what should a learner be able to take with them, why, and who gets to decide?
A test of educational purpose
When a system is designed around retention alone, it is tempted to make itself indispensable. When it is designed around learner agency, it asks a harder question: how will this learner be better able to navigate the world when our direct support is no longer present?
That question changes design choices. It favors clear records over opaque summaries, explanation over unexplained prediction, interoperable work over locked-in artifacts, and human handoffs over silent disappearance. It also makes room for an important kind of accountability: a learner who can leave can compare what they received with what they were promised.
The tension is real. Systems need stability, trust, and sustained participation to support communities well. A shallow form of portability could encourage institutions to withdraw care too quickly or transfer burdens onto learners.
How can learning systems make leaving possible without making learners carry alone the support and relationships that made learning possible in the first place?
Leave a Reply