Progress Dashboard¶

A visual feedback interface — instantiates Formative Feedback Loop

Aggregates progress indicators into a visible, persistent display so patterns and at-risk learners surface early enough to trigger support before it's too late.

A Progress Dashboard collects progress indicators across learners and over time into a single visible display, so patterns — who is falling behind, which topic is sinking a whole cohort, whose trajectory just bent downward — surface early enough to act on. Its defining features are aggregation, persistence, and thresholds: it keeps a running record rather than a single snapshot, and it can flag when an indicator crosses a line that warrants intervention. It is a monitoring interface, not a diagnostician: it makes the signal visible and routes attention, but it does not itself explain why a learner is struggling or what to do — it points, and hands off.

Example¶

An instructor running a twelve-week coding bootcamp watches a cohort dashboard: per-student progress on projects, quiz trends, time-on-task, help-requests. In week five it isn't a single failing grade that catches her eye — it's a pattern: three students whose project-completion line has gone flat while their help-requests dropped to zero. The dashboard's amber threshold flags them as at-risk before any assignment is formally failed. That's a routing signal, not a diagnosis: she reaches out and finds, in conversation, three different causes — one is lost on async/await, one is working a night job, one is quietly stuck on setup. The dashboard found who and when; the why and the fix came from the human it prompted.

How it works¶

It aggregates many indicators across learners and time, so the unit of insight is a pattern or trend, not one result.
It persists — a running record — so trajectories and drops are visible, not merely current state.
It carries thresholds that flag when an indicator crosses into "needs attention," routing scarce human attention to where it's warranted.
It displays and routes; interpreting and fixing are explicitly handed off to a human.

Tuning parameters¶

Indicator choice — which proxies are shown; well-chosen indicators surface real risk, poorly chosen ones make people chase the metric instead of the learning.
Threshold sensitivity — where the at-risk line sits; sensitive thresholds catch problems early but cry wolf, loose ones miss quiet slides.
Aggregation grain — individual, group, or topic view; each surfaces a different pattern and hides others.
Visibility — instructor-only, learner-facing, or both; learner-facing adds self-monitoring but can shame or invite metric-gaming, and surveillance risk rises with exposure.
Refresh cadence — live versus periodic; live catches fast drops but invites over-reaction to noise.

When it helps, and when it misleads¶

Its strength is scaling attention: one instructor can watch fifty trajectories and be pulled to the three that need them, early, with the history in view.

Its failure mode is that everything it shows is a proxy, and proxies drift from the real target; make an indicator consequential and people optimize the indicator rather than the learning it stood for.^[1] It can also breed surveillance and anxiety, and its tidy visuals invite the illusion that being seen is the same as being helped. The classic misuse is treating the dashboard as the intervention — a green board taken as proof learning is fine, a red cell as a verdict — instead of as a prompt to go find out why. The discipline that guards against this is to treat indicators as questions, not answers, tune thresholds to route attention rather than to grade, and always pair a flag with a human look.

How it implements the components¶

progress_signal — it ingests and displays the indicators that serve as progress evidence.
feedback_record — it persists a running history, so trends and drops are visible over time.
escalation_threshold — its at-risk lines flag when an indicator crosses into warranting intervention.
instructional_response_channel — flags route attention to the instructor or support side to act on.

It does not diagnose the cause behind a flag (gap_diagnosis — Misconception Probe, Practice Review), tell a learner what to change (actionable_feedback — Coaching Check-In, Formative Rubric), or drive the revision-and-recheck (learning_response, recheck_cycle — Draft Feedback Cycle).

Instantiates: Formative Feedback Loop — it is the monitoring interface that makes the loop's signal visible and routes attention early.
Consumes: progress signals from mechanisms like Low-Stakes Quiz and Exit Ticket, which it aggregates over time.
Sibling mechanisms: Coaching Check-In · Adaptive Practice Set · Draft Feedback Cycle · Exit Ticket · Formative Rubric · Low-Stakes Quiz · Misconception Probe · Peer Review Protocol · Practice Review · Rapid Feedback Cycle

References¶

[1] Goodhart's law — "when a measure becomes a target, it ceases to be a good measure." A progress dashboard's indicators are proxies for learning; once they carry stakes, learners and instructors can optimize the proxy at the expense of the capability it was meant to track. ↩