A new learner receives their welcome email, logs into the LMS and sees a list of courses.
Some look relevant. Others seem to be for a different role. There is no clear starting point, and nobody has explained which courses are required or when they need to be completed.
The learner has access. But they do not have a clear learning journey.
Before setting up welcome messages, reminders and onboarding workflows, it helps to answer a more basic question:
How should learning be structured for the people using your LMS?
That is where learning architecture comes in.
What is LMS learning architecture?
Learning architecture is the structure connecting your audiences, learning paths, courses and activities.
It also defines the rules around that structure: who receives the learning, how they move through it, what counts as completion and who keeps it current.
You do not need a complicated diagram to get started. You need a shared map that helps your team make consistent decisions.
Start with the audience and the outcome
Uploading the content you already have can feel like the quickest way to launch. But a folder of presentations and policies does not automatically become a useful learning path.
Start with two questions:
- Who needs this learning?
- What should they be able to do afterwards?
For example, all new employees may need company essentials. A new customer support employee also needs to understand the support tools, practise common customer situations and know when to escalate an issue.
Those needs overlap, but they are not identical. Your structure should reflect that.
Separate shared learning from role learning
A simple architecture can organise learning into three areas:
| Learning area | Purpose | Example |
|---|---|---|
| Shared foundation | Learning needed across the organisation | Company essentials, security and finding help |
| Role learning | Learning needed to perform a particular role | Tools, workflows, customer scenarios and guided practice |
| Ongoing learning | Learning needed after initial onboarding | Refreshers, policy updates and development |
This gives you a starting point for deciding what to reuse and what needs to be specific to an audience.
A shared course can serve several paths without needing a separate copy for every team. Role learning can then build on that foundation.
Connect the structure to clear rules
Course organisation is only part of the architecture. Each learning path also needs practical decisions about how it will work.
Assignment: Who receives the path, and what starts their enrolment? This might be a learner joining a role group or an administrator confirming an assignment.
Progression: What should be completed first? Which activities are required, optional or dependent on earlier learning?
Ownership: Who maintains the content? Who manages the LMS configuration? Who follows up when progress stops?
Completion: What evidence is needed? Completing a course may show that the learner finished the material. A role task may also need observed practice or manager confirmation.
Keep the learning requirement clear even when your LMS cannot record every part of it. Agree where additional evidence will be held and who will review it.
Give reference information a clear home
Some information needs to be learned. Other information needs to be found again while doing the job.
A course can introduce a process and provide practice. A current job aid or knowledge-base guide can support the employee when they use that process later.
Link to a trusted source where practical. Copying the same guide into several courses creates more places to maintain when the process changes.
Check the LMS setup before onboarding learners
Once the map is agreed, check that the platform supports it.
Confirm learner groups, access permissions, course assignments, due dates, completion rules and reporting access. Then test the journey with a sample learner.
Can they see the right learning? Is the starting point clear? Does the expected completion appear in the report? Does someone know what to do if the learner gets stuck?
These checks connect the planned architecture to the learner’s actual experience.
Then build the onboarding workflow
With the foundation in place, you can design the workflow around it:
Learner added → Welcome and first login → Assigned learning → Progress follow-up → Completion and next steps
Reminders now have a clear purpose. You can distinguish someone who has never logged in from someone who has started but needs help completing their learning.
The workflow supports a defined journey instead of trying to compensate for an unclear structure.
Map your learning architecture
Our LMS Learning Architecture Map includes a worked example, a fillable planning worksheet and a readiness checklist.
Use it to agree one audience and one learning path first. Define the outcome, structure, owners and rules before expanding the rest of the LMS.
Download the LMS Learning Architecture Map (fillable PDF)
Need help connecting the structure to your LMS setup? AccelerateLMS can help you review the current platform, identify gaps and implement a clearer learning journey.
Once your learning structure is ready, connect it to the onboarding workflow.