Why this exists
Course quality is not just a matter of whether the content is accurate or the screens look polished. A strong course needs a visible chain of evidence.
Goals should point to meaningful practice. Assessments should show whether learners can do the work. Rubrics should make expectations clear. Evaluation should help the team decide what to improve next.
Use it to ask better questions
- What should learners be able to do?
- What evidence would show they can do it?
- What criteria will help reviewers judge the work fairly?
- What might prevent learners from succeeding?
- What data will help the team improve after launch?
Goal-to-evidence alignment map
Use this before building assessments or learning activities.
| Course goal or outcome | Learner action | Evidence we can collect | Assessment or activity | Adaptation question |
|---|---|---|---|---|
| What should learners be able to do? | Explain, apply, evaluate, create, troubleshoot, decide, perform, or reflect. | Product, response, scenario decision, rubric score, observation, self-check, quiz item, or workplace artifact. | What will learners complete or demonstrate? | Does this evidence actually show the outcome, or only recognition/recall? |
| Is the task realistic for this audience and context? | ||||
| What would count as acceptable performance? |
Design reminder: if the assessment only asks learners to remember wording from the course, but the outcome asks them to make decisions or perform a workplace task, the course probably needs better practice.
Assessment design check
Use this when creating or reviewing assessments.
- The assessment matches the level of performance described in the objective.
- Learners know what success looks like before they begin.
- The task is authentic enough to resemble the real use context.
- The prompt avoids unnecessary ambiguity.
- The scoring criteria are visible, fair, and observable.
- Feedback helps learners understand what to do differently next time.
- The assessment avoids irrelevant reading load, cultural assumptions, or hidden prior knowledge.
- The format is accessible and usable with assistive technology.
- If the course is not graded, the activity still gives learners a useful reason to engage.
Adaptation prompt: remove any checklist item that does not apply, but replace it with a better question rather than leaving a blind spot.
Rubric planning frame
Use this to draft a simple analytic rubric with observable performance levels.
| Criterion | Developing | Proficient | Strong |
|---|---|---|---|
| Accuracy | Response includes major gaps, misconceptions, or unsupported claims. | Response is mostly accurate and addresses the core task. | Response is accurate, complete, and handles important nuance. |
| Application | Response repeats ideas without clearly applying them to the situation. | Response applies the relevant concept to the situation. | Response applies the concept thoughtfully and explains why the choice fits. |
| Evidence or rationale | Response gives little support for the decision. | Response gives a reasonable explanation or example. | Response uses specific evidence, tradeoffs, or context to support the decision. |
| Communication | Response is hard to follow or missing key information. | Response is clear enough for the intended audience. | Response is clear, concise, audience-aware, and easy to act on. |
Rubric review questions
- Are the criteria things we actually care about?
- Can a reviewer observe each criterion in the learner's work?
- Are the performance levels distinct?
- Would two reviewers likely score the same sample in similar ways?
- Does the rubric help the learner improve?
Usability review checklist
Use this during prototype review or before launch.
Navigation and orientation
- Learners can tell where they are in the course.
- The next action is obvious on each screen or page.
- Required activities are distinguishable from optional enrichment.
- Page titles, module titles, and activity labels match the course structure.
Clarity and cognitive load
- Instructions are short enough to act on.
- Important information is grouped and sequenced logically.
- Learners are not asked to remember too much across screens.
- Examples are close to the decisions or tasks learners need to perform.
Accessibility and inclusion
- Images have appropriate alt text or are marked decorative.
- Link text is meaningful outside its surrounding sentence.
- Color is not the only way information is communicated.
- Interactions can be completed with keyboard and screen reader support.
- Language avoids unnecessary assumptions about identity, background, role, or prior access.
Feedback and improvement
- Knowledge checks explain why an answer is reasonable or not.
- Reflection prompts are framed as useful practice, not busywork.
- Learners have a way to recover after confusion or incorrect choices.
- Reviewers know what kind of feedback the design team needs.
Post-launch evidence log
Use this after a pilot, first offering, or major course refresh.
| Evidence source | What it might show | What to watch for | Possible action |
|---|---|---|---|
| Learner survey | Perceived clarity, relevance, confidence, friction. | Overweighting satisfaction without checking performance. | Revise unclear directions, examples, or pacing. |
| Assessment results | Patterns in understanding or performance. | Items everyone misses, items everyone gets right, or weak alignment. | Revise instruction, practice, item wording, or rubric. |
| LMS data | Completion patterns and drop-off points. | Assuming time-on-task equals learning. | Shorten, restructure, or better signpost problem areas. |
| SME or facilitator notes | Content accuracy and learner misconceptions. | Anecdotes that need corroboration. | Add examples, clarify terminology, update content. |
| Usability review | Navigation, accessibility, and technical barriers. | Treating friction as learner failure. | Fix layout, interaction, access, and instructions. |
How to use the toolkit
The template is not the work. The conversation it creates is the work.
Start with one course, module, or assessment.
Choose the template that matches the decision you need to make.
Fill it in quickly with the team.
Mark anything uncertain instead of pretending the answer is known.
Adapt the template to the project.
Use the finished version to guide development, review, or revision.