Designing the Learning Action Loop
The central subject of this series has been the learner-facing learning analytics dashboard: a system that turns online activity into signals intended to help students regulate their learning. This final chapter connects the evidence about interaction order, JoL prompts, SRL profiles, GenAI feedback, and tutor judgement into one practical question: what must be true for a dashboard to support learner-owned action rather than merely report more metrics? The answer gives readers a way to evaluate a design, assign responsibilities, and state its limits without confusing a promising component with a proven educational effect.
A dashboard earns its place in the loop
A dashboard is part of a learning action loop when each major output creates a defensible opportunity for the learner to make a better-informed next decision, and when later evidence can test what happened. The loop begins with a necessary and interpretable trace. It does not end when a chart appears, a model assigns a profile, or an LLM produces a fluent paragraph. It ends provisionally when a learner interprets the evidence, chooses and enacts a response, and encounters new evidence that can confirm, complicate, or correct the original interpretation.
The two studies make the sequence visible in different ways. In the programming-course ILAD, the learner judged a competency before seeing the system’s progress and mastery estimate. That ordering made the number feedback on a prior belief. In the online statistics intervention, a learner’s traces were first translated into SRL proxies and a profile, then used to time and tailor feedback, after which post-intervention activity was measured. One case concentrates on the moment of comparison; the other extends the loop across a period of monitoring and response. Neither tested the complete loop as one validated construct, but together they show why a display, a learner model, a prompt, a feedback source, and a later check must be considered as one connected system.
The first design obligation is evidence discipline. Collect the smallest set of traces that can answer the learner’s immediate question, and explain what those traces do and do not represent. A late submission, a score trend, or a viewed resource can be relevant, but its meaning depends on the course, the task, and the learner’s circumstances. The second study’s five SRL pillars offer a useful organising model because they connect activity to goals, strategies, time, help-seeking, and evaluation. They do not turn clicks into direct measurements of those abilities. A profile should therefore be presented as a revisable interpretation, not a verdict about who the learner is.
The second obligation is to give the learner an interpretive role. The JoL gate in the ILAD provides one concrete pattern: self-assessment first, system estimate second, reflection or dialogue after the comparison. The same principle need not use a five-step scale in every setting. It can ask a learner to predict whether a topic is secure, identify the likely cause of a performance pattern, or state what evidence would change their view. What matters is that the learner contributes a judgement that the dashboard can help them inspect. Without that contribution, the system may improve the presentation of information while leaving the learner’s mental model untouched.
The third obligation is a meaningful response. Feedback should not merely label a learner as high or low, nor should it convert every signal into an instruction.