Skip to content
Hi, Bot
Back to blog
philosophyessay

The case against screen time as a metric

Minutes on a screen tells you almost nothing about what actually happened during those minutes. Here's what we think is worth measuring instead.

November 6, 2026 · Hi, Bot

Screen time is the metric almost every parent already tracks, because it's the easiest one to track — a number an app or a router can spit out without anyone having to look at what was actually happening on the other side of the glass. It's also close to useless for judging whether a kid's time was well spent, and we think it's worth saying that plainly, because we build a lot of programming around screens and get asked about the number constantly.

Two kids, same forty minutes, completely different outcomes

Picture a kid scrolling a feed of short videos for forty minutes, and a kid spending forty minutes debugging a robot that won't turn the right way. Same screen-time number. Nothing else about those two forty-minute blocks is the same — not the attention involved, not what's produced, not what the kid is like afterward. A metric that can't tell these two apart isn't measuring the thing anyone actually cares about, which is never really "how long was a screen on." It's "what happened to this kid's attention and skill during that time."

What actually predicts whether the time was well spent

A few questions get you much closer than a minute count ever will. Did the kid make something, or consume something? Was she directing the activity, or was the activity directing her? Could she explain afterward what she did and why, in her own words, or does she only remember a vague sense of having been entertained? None of these show up on a screen-time report. All of them are visible to a parent who asks two or three specific questions at pickup instead of checking a number.

Why we don't publish our own screen-time totals

We could tell you the average number of minutes a kid spends in front of a screen in a session here, and it would be a large number, because building with AI and robotics tools happens on screens. Publishing that number without context would hand parents exactly the wrong data point — a big scary total that says nothing about whether the kid spent that time building a working object detector or watching something passive. We'd rather you ask what she built than ask how long she was logged in.

The replacement metric we actually use

Internally, the thing mentors track isn't time, it's output and explanation — the same two questions we use instead of a grade. Did something get built or meaningfully advanced, and can the kid explain the choices behind it. A session that produces a real answer to both of those questions was a good session regardless of whether it ran forty minutes or ninety. A session that produces neither wasn't a good session even if it only ran twenty.

What we'd tell a parent instead of "how much screen time"

Ask what she made. Ask what didn't work and what she did about it. Ask her to show you, not tell you. Those questions take longer to answer than a number does, and that's exactly why they're more useful — a real answer can't be faked the way a small screen-time number can be waved around as proof nothing bad happened. The number was never the thing that mattered. What happened during the minutes always was.

› Keep reading

Get the next dispatch.

Occasional, never spammy.

By submitting, you agree to our Terms and Privacy Policy.