LMS 3.0 · The eLearning 3.0 ProjectThe next generation of the learning management system
The LMS that ran the last thirty years was a course shell. The LMS that runs the next thirty is an orchestration layer — AI-native, standards-open, and conducted in real time. This is the working hub for the architecture, the operating model, and the institutional decisions that get us there.
Updated — with Learning Orchestration System primer + LMS-at-30 cross-links
Why "LMS 3.0" — and why now
LMS 1.0 was the course shell — Blackboard, CourseInfo, WebCT, Moodle. LMS 2.0 was the extensible platform — Building Blocks, LTI, an app marketplace grafted on top of the shell. LMS 3.0 is something different in kind: an AI-native orchestration layer that treats curriculum, tutoring, assessment, credentialing, and analytics as services to be conducted, not pages to be authored.
The category is being rewritten in real time by three forces at once — generative AI in the classroom, the lifelong-learning economy moving inside higher education, and a credentialing market that no longer fits inside a course. None of those forces are served by extending the 1997 architecture one more time.
This hub is also the working home of the eLearning 3.0 Project — the open, in-public effort to specify what the next generation of online learning actually is: its architecture, its standards posture, its operating model, and the institutional decisions that move a campus or a platform from LMS 2.0 into LMS 3.0. "LMS 3.0" and "eLearning 3.0" name the same shift from two angles — the platform and the practice — and this hub treats them as one program of work.
It collects the architecture, the reference designs, the field notes, and the talks behind that program. It is being written in public. New artifacts land here automatically — see the LMS at 30 companion hub for the history of how we got here.
"The next LMS isn't a better course shell. It's a conductor — orchestrating curriculum, tutors, assessment, and credentials as one continuous system around the learner."
A program of workSpecifying what comes after the course shell — in public.
eLearning 3.0 is the practice side of LMS 3.0: the architecture, the standards posture, the operating model, and the institutional decisions that move a campus or a platform from an extended 2.0 shell into an AI-native, orchestration-first system. This hub is its working home.
The platform thesis
Three pillars that distinguish a true LMS 3.0 from a 2.0 shell with AI bolted on the side.
Three pillarsThe practice thesis
Four movements being written in public — from course shell to orchestration, the six-layer stack, the operating model, and reference architectures institutions can ship.
Four movementsThe open record
Whitepapers, field notes, talks, and reference designs as they land — published openly, syndicated via the dedicated RSS feed.
Latest artifactsThree pillars
What makes a learning platform LMS 3.0
Orchestration over containment
LMS 1.0 was a course shell. LMS 2.0 added a marketplace of plugins. LMS 3.0 is a real-time orchestration layer that conducts curriculum, AI tutors, assessment, credentialing, and analytics as one coherent system.
AI-native, not AI-bolted
Personalization, tutoring, content generation, and assessment are first-class platform services — not features bolted onto a 1997 architecture. Inference, retrieval, and orchestration are line items in the operating model.
Open by contract, governed by trust
Standards (LTI 1.3, IMS Caliper, xAPI, OpenBadges/CLR), a Building-Blocks-style extensibility contract, and an institutional governance model that boards, CIOs, and accreditors can actually defend.
The work in flight
Four movements being written in public
Each movement will land here as an artifact (whitepaper, field note, reference architecture, talk). New entries are added to the registry and surface on this hub automatically.
- Movement I
From course shell to orchestration layer
Why the LMS as a category has to change shape. The 1997 architectural decisions that no longer hold under AI workloads, lifelong learning demand, and the credentialing economy.
- Movement II
The six layers of the LMS 3.0 stack
Identity & roster · Curriculum graph · Learner state & memory · AI tutor and content services · Assessment & evidence · Credential & analytics. How they compose, what they cost, what they replace.
- Movement III
The institutional operating model
What boards, presidents, CIOs, provosts, and CTLs actually have to decide. Procurement, governance, faculty workflow, data trust, and the AI policy stack.
- Movement IV
Reference architectures
Open-source, vendor, and hybrid reference architectures that an institution or platform team can actually ship in 2026–2028. Build vs. buy, with cost-to-serve modeled.
Strategic engagement
Bring LMS 3.0 to your board, your CIO, or your product team
Working sessions with Stephen for institutions and platform teams making LMS 3.0 / orchestration decisions: architecture reviews, board briefings, RFP shaping, AI-policy stack design, and reference-architecture critiques. Limited engagements per quarter.
Latest in the series
LMS 3.0 artifacts, newest first
Whitepapers, field notes, reference architectures, and talks — surfaced automatically. Tag a field-note post or a whitepaper lms-3-0 and it appears here on the next render. For one-off artifacts without a DB row (talks, external PDFs, the orchestration series), add an entry to src/lib/lms3Registry.ts.
Loading the latest LMS 3.0 work…
Continue
Build the next generation LMS — together
Talk to Stephen about the LMS 3.0 architecture, the orchestration layer, or how your institution / product team can move from a course shell to a real conductor.
For the historical corpus, see LMS at 30 → · For the product / company record, see Blackboard →