What a Parent Really Needs to See on a Progress Dashboard

The first progress screen I sketched for my middle schooler looked like every dashboard I have ever seen at work. A big average at the top, a line chart of minutes spent, a streak counter, a tidy row of green checkmarks. It looked great in a demo. Then I sat down one evening, looked at it properly, and realized I could not answer the only question I actually had: can my kid do this on their own yet, and if not, what is getting in the way? The dashboard was telling me how busy the software had been. It was telling me almost nothing about my child.

That gap is what this post is about. Whether you are a parent trying to read a progress report, a teacher deciding what to share with families, or a builder designing one, here is what I have learned about what belongs on that screen and what quietly misleads.

Why averages and minutes mislead

A grade average is a smoothie. You throw in a week of work, blend it, and get one number. It tastes fine, but you can no longer tell what went in. An 80 could be steady, solid work across the board. It could be perfect work on easy material and real confusion on the one idea that matters next month. It could be a kid who struggled early, has now figured it out, and is being dragged down by old mistakes. Those are three very different situations that call for three different responses from a parent, and the average hides all of them.

Averages also punish learning itself. If early attempts count the same as later ones, a kid who takes risks and gets things wrong on the way to understanding looks worse than a kid who stayed safely inside what they already knew. That teaches the wrong lesson.

Minutes on app is worse, because it feels like effort. In engineering we call this a vanity metric: a number that goes up and makes everyone feel good without telling you whether the thing works. Time spent can mean deep focus, or a tab left open during a snack, or a kid stuck on one problem for twenty minutes because nothing helped them get unstuck. A long session might be a sign of a problem, not progress. A dashboard that leads with time is rewarding presence, not learning.

What a parent actually needs to see

When I strip it down, there are five things I want to know about my kid's week. None of them is a single number.

What they can do alone

This is the headline. Not "what did they get right" but "what can they do without help." There is a big difference between solving a problem with hints and solving it cold a few days later. Teachers will recognize this as the gap between assisted and independent performance, the edge of what learning researchers call the zone of proximal development. A good dashboard is clear about which side of that line each skill sits on.

Where they are stuck, and why

"Struggling with fractions" is not useful. "Can add fractions with the same denominator, but adds the denominators when they differ" is extremely useful, because now I know what conversation to have at the kitchen table. The why matters most. A misunderstood concept, a shaky procedure and plain rushing are three different problems with three different fixes.

Their own words as evidence

The most revealing thing I have seen is my middle schooler explaining a problem back to me. A sentence or two in their own words tells me more than a page of scores. When they can explain why dividing by a fraction means multiplying by its flip, I believe they understand it. When the explanation is "because that's the rule," I know we have work to do. A good dashboard shows a short excerpt of that explanation as evidence, rather than a score generated from it.

Effort and help used

I do want to know about effort, just not as minutes. Did they try again after getting it wrong? Did they use a hint, look at a worked example, or ask for help? Using help is not a failure. It is what smart learners do. But knowing how much help was used tells me how solid a skill really is.

The week in context

A rough Tuesday means very little by itself. A dashboard should show the shape of the week: what was new, what was review, what got easier. It should also allow for life. A week with a big game, a sleepover and a cold should not look like a crisis.

Levels instead of scores

Instead of percentages, I have come to prefer a small set of plain levels for each skill. Something like: not started, learning with help, can do it alone, can explain it, and holding over time. Think of belt levels in a martial art. Nobody asks what percentage of a yellow belt you are. You can either do the form on your own, or you cannot yet.

Levels do things scores cannot. They describe what a kid can do in words a parent understands. They make the next step obvious. They borrow from mastery learning, where the point is to reach solid understanding before moving on rather than to pile up points. And they keep old mistakes where they belong, in the past. Once your kid can do it alone, the early stumbles stop dragging the picture down.

Design principles I hold myself to

A few rules have survived every round of feedback, including feedback from the toughest critic I know, my own kid.

1. One clear next step. Every view should end with a single, doable suggestion. "Tonight, ask them to explain how they found the common denominator in problem three." Not a list of eight areas for improvement. A tired parent can act on one thing.
2. Be honest about uncertainty. If the system has only seen two attempts at a skill, it should say so. "Early signal, only a couple of tries so far" earns more trust than a confident label built on thin evidence. A forecaster who admits the clouds could go either way is more believable than one who is always certain.
3. No predictions about a child. I will not put "on track for an A" or "at risk" on a parent screen. Predictions about kids tend to become labels, and labels stick. The dashboard should describe what happened and what to try next, then stop.
4. Show evidence, not verdicts. Wherever possible, show the actual work or words behind a claim, so a parent or teacher can judge for themselves.
5. Readable in a minute. If it takes longer than a coffee refill to understand, it is a report, not a dashboard.

What to leave out

The hardest design work was deciding what to leave off.

• Leaderboards and comparisons with other kids. They tell a parent nothing about what to do next, and they tend to make kids either anxious or smug.
• Streaks as the main motivator. A streak is fine as a small nudge. When it becomes the point, kids do the minimum to keep it alive.
• Raw time on app. If time matters, translate it into something meaningful, such as "practiced three times this week," and leave the minutes off.
• Every data point you collected. A dashboard is a summary, not a log. Showing everything is a way of avoiding the decision about what matters.
• Anything you would not want your kid to read. I assume my middle schooler will see the parent view eventually. If a phrase would sting or embarrass them, it does not belong there.

Takeaways

• Lead with what your child can do alone, not with an average.
• Ask for the why behind a struggle: concept, procedure or carelessness.
• Treat your kid's own explanation as the best evidence of understanding.
• See help used as information, not failure.
• Prefer plain levels over percentages, and judge progress by the week, not the day.
• Look for one clear next step, honest uncertainty and no predictions about the child.
• If a dashboard leads with minutes, streaks or rankings, read it with a raised eyebrow.