1. Start with the learner and outcome
Identify the learner groups, their starting knowledge, learning environment and the outcome the programme should support. Describe what learners should be able to do after completing the experience, not just which topics it should contain.
2. Define the content scope
List modules, lessons, learning assets, assessments, source materials and subject-matter reviewers. Confirm which materials already exist, which require creation and who is responsible for factual and editorial approval.
3. Map the learner journey
Sketch how learners discover the programme, enrol, access content, complete activities, receive feedback and get help. Include the administrator or tutor workflow where relevant, and identify where learners might get stuck.
4. Confirm platform and integration needs
Document whether the project uses an existing LMS or needs a new portal or feature. Record user roles, content formats, reporting, authentication, integrations, data requirements and any technical constraints that need early investigation.
5. Include accessibility from the start
Consider keyboard navigation, captions, transcripts, colour contrast, readable documents, meaningful headings and accessible assessments during planning. Retrofitting these later can introduce avoidable rework.
6. Design assessment and feedback
Define how progress will be measured, what counts as completion, how feedback is delivered and whether assessments need question banks, answer explanations or multiple attempts. Ensure assessment design matches the intended learning outcome.
7. Pilot before broad rollout
Test a representative module with intended users and reviewers. Check comprehension, usability, accessibility, technical behaviour and content accuracy. Use the feedback to refine scope and acceptance criteria before launch.
8. Plan ownership after launch
Agree who maintains content, handles support requests, reviews analytics, updates platform components and approves future changes. A clear handover helps the programme stay useful after initial delivery.
Before the project begins
- Learner groups and measurable outcomes identified
- Content inventory and reviewer responsibilities documented
- Learner and administrator journeys mapped
- LMS, integrations and reporting requirements listed
- Accessibility requirements included in scope
- Assessment and feedback model agreed
- Pilot plan and acceptance criteria defined
- Post-launch ownership and maintenance agreed
Need help putting this into practice?
DGx Creators can discuss the requirements, volumes and review process for your project. Share your brief to explore a suitable next step.
Explore E-Learning Technology ↗ Contact DGx Creators