Par and efficiency scoring: grading the solution, not the child

Evidence grade: design pattern with converging support, not a trialed intervention. Nobody has run par-vs-timer RCTs in primary classrooms. The pattern's warrant is assembled: the HCI tradition that solutions have measurable costs, the motivation research distinguishing task- from ego-involving evaluation, and the accuracy-first evidence against speed pressure. Assembled reasoning, graded as such — and our stake is on the table: we built our scoring on it.

Games need a second axis beyond done/not-done — something that makes a solved task worth re-thinking. The industry default is the clock; the alternative with better psychology is par: score the solution's cost in the task's own currency (moves, blocks, edits, steps) against an efficient reference. Golf has run on it for centuries; speedrunning communities independently rediscovered that optimizing a solved thing is one of play's deepest pleasures. The educational question is what each axis teaches.

Why efficiency beats speed as the second axis

The clock grades the child; par grades the artifact. "Too slow" is a verdict on a person — ego-involving, anxiety-loaded, and unevenly cruel across a classroom (the accommodations page documents who pays most). "Done in 9, possible in 6" is a fact about a solution — task-involving, revisitable, and interesting: it announces the existence of a better idea without saying what it is, which is a puzzle invitation rather than a deficiency notice.

Efficiency is curriculum; speed is a side effect. The gap between a 9-block and 6-block charm is a concept — a repeat unnoticed, a pattern unfound; the gap between fast and slow typing of the same solution is automatization, which accrues from accurate practice and is actively damaged by racing. Par points the child's attention at exactly the layer where thinking helps.

Retries reframe as method. Under a clock, retrying means failing again with witnesses; under par, re-running is how optimization works — every attempt is data. This licenses the experimentation that programming pedagogy wants and timers suppress.

The honesty engineering

Par systems earn trust or don't on one question: is par actually achievable? An unreachable par is a rigged carnival game, and children detect rigging with forensic speed. The engineering that keeps par honest: prove it where provable (for pathfinding tasks, verify par equals the true shortest path mechanically), author-and-verify where judgment enters (loops and functions make "shortest" a design choice; simulate the reference solution before shipping), pad with a grace band (legitimate solution diversity shouldn't cost the second star), and never stack par with time — one pressure axis, chosen deliberately.

What the evidence doesn't say

It doesn't eliminate fluency measurement — WPM with accuracy remains the right metric for typing, measured low-stakes; par is the general-task axis, not a typing replacement.
It doesn't claim optimization is every child's joy — some meet par with a shrug; the design requirement is only that par never punishes (done-at-all keeps its star and its progress).
It doesn't have its trial — if someone runs par-vs-timer with primary cohorts, we'll cite it over this reasoning gladly.

In the classroom

Grade artifacts, not durations, wherever work has a cost dimension — "can the class solve it in fewer steps?" makes a better challenge than a stopwatch every time.
Publish the par honestly — if you set a target, be able to demonstrate it; one impossible target poisons the well.
Use par gaps diagnostically: a child consistently far over par isn't slow — they're missing a specific concept the gap names (the dashboard read).

How Wiz Kids applies this

The design memo has the full account: par in the task's own currency, three stars at par with a grace band, BFS-proven pars where provable, free unlimited retries, no timers anywhere in the product — and completed lessons that stop asking, because the star-chasing failure mode is par's known dark side and we guard it.

References

Card, S. K., Moran, T. P., & Newell, A. (1983). The Psychology of Human-Computer Interaction — solution costs as measurable objects.
Nicholls, J. G. (1984). Achievement motivation: Conceptions of ability, subjective experience, task choice, and performance. Psychological Review, 91(3) — task- vs ego-involvement.
Bjork, R. A., & Bjork, E. L. (2011). Making things hard on yourself, but in a good way — difficulty in the task, not the pressure.

© Glu IO Pty. Ltd. — Wiz Kids (wiz.kids). Link freely; republication requires permission — see terms. Found an error in our reading of the research? We correct fast: tell any teacher piloting Wiz Kids.