Learner Analysis: Prior Knowledge, Needs, and Barriers
8 min read
Lesson objectives
- Identify learner information that changes a design decision rather than collecting characteristics unrelated to the task.
- Distinguish prior knowledge, preference, need, and barriers affecting access or performance.
- Derive suitable support or a starting point from learner evidence without lowering the final outcome.
Learner analysis means design decisions, not decorative personas
Learner analysis answers a practical question: what do I need to know about people in order to remove a barrier, choose an appropriate starting point, or provide suitable support? We do not collect every possible fact. We look for characteristics that may affect learning or performance: prior knowledge, relevant experience, the purpose for learning, the language used in the task, access to devices and connectivity, required digital skills, available time, and needs that affect access or participation. These data remain design inputs only when they are connected to an explainable and testable decision.
Prior knowledge shapes the starting point
A learner who understands the domain vocabulary but has never used the new system needs a different starting point from someone new to both the domain and the system. Starting too low may waste experienced learners’ time; jumping directly to exceptions may deprive novices of needed foundations. The solution does not necessarily require two complete courses. A short entry check, a compact review path for novices, and more complex examples for learners with the foundation may be enough. The distinction should be based on relevant knowledge or performance, not on a fixed personal label.
| Information | Possible design implication | What it does not justify by itself |
|---|---|---|
| Low prior knowledge | Introduce vocabulary and core examples before exceptions | Assuming low general ability |
| Strong experience with the old procedure | Highlight changes and reduce already-known explanation | Permanent exemption from practising the new procedure |
| Interrupted mobile study | Short segments, clear navigation, and saved progress | Lowering the learning outcome |
| Use of assistive technology | Accessible structure and testing with relevant technology | Assuming a fixed learning preference |
A need is not the same as a preference
A learner may say, “I prefer video.” That is useful information about comfort or expectation, but it is not enough by itself to choose the medium. Ask what the task requires: does the learner need to see motion, hear pronunciation, search a reference, or practise a decision? A learner may also need alternative text, captions, or keyboard operation in order to access the material at all; these are not merely optional “preferences.” We therefore distinguish preference, task-related need, and a barrier that prevents access or performance.
Collect the minimum useful evidence
Learner information can come from short interviews, performance observation, work samples, entry questions, support records, or legitimately available usage data. Choose the source that answers a specific design question. Do not collect personal data you do not need, and do not use a demographic category as a lazy proxy for knowledge or access. If you need to know task experience, ask about it directly or use a simple performance check rather than inferring it from age or job title.
Lesson summary
Use learner data when it helps adjust the starting point, support, or access, and connect the decision to the task rather than a stereotype about the person.