The Question to Ask First

Most parents arrive at this subject through a specific worry and leave with a product. The question below puts them back in order.

The question

What exactly are you worried about?

Named specifically, as a thing that could happen to this child at this age, rather than as a general unease about the internet.

What the answers point to

"They will see pornography." A filtering question at younger ages, a conversation question at older ones, and the conversation is covered in its own note.

"Someone will contact them." Contact risk, which technical controls barely touch. Platform settings, privacy settings and a route to tell you are the answers.

"They will spend money." Restriction at the account level, which works well and is the easiest thing here to fix properly.

"They are on it all the time." A household rhythm question rather than a safety one, and treating it as safety produces the wrong tools.

"They will be bullied, or bully." Conduct risk. Controls do nothing; noticing and talking do.

"I do not know what they are doing." The honest answer, and the one that most often produces covert monitoring — which is the decision to think hardest about.

Why the question works

It separates four completely different problems that share a name.

It produces an answer you can check against what a given control actually does.

And it frequently reveals that the worry is about an age the child is not yet, which changes the timing rather than the tool.

The second question

What would you want them to do if it happened?

Almost always: tell you.

Which makes the design goal explicit — that the child comes to you — and that goal is damaged by some of the measures people reach for.

Every subsequent decision can be tested against it: does this make it more or less likely they would tell me?

The third question

How old are they, and what changes next year?

Because a setting is a decision about a moment, and the moment moves.

Asking it converts a permanent restriction into a stage with an endpoint, which is how the whole thing is supposed to work.

Using them together

Name the worry, decide what you want the child to do, and choose the measure that does not undermine it.

Which will sometimes be a technical control, often a platform setting, and frequently a conversation.

Ten minutes, and it produces a better arrangement than any product comparison.

The collection in one line

Match the control to the age, tell the child what it is, and protect the thing that matters most — that they would come and tell you.

Everything else in these notes is the detail of doing that at each stage.

What this changes

Naming the worry first redirects the effort, frequently away from software entirely.

Most parents who do this find the answer is a platform setting and a conversation rather than a purchase.

The check

Write the worry in one sentence.

If it takes a paragraph, it is general anxiety rather than a specific concern, and the measures that address it are different.

Asking it of a product page

Read a marketing page and ask which of the four worries each feature addresses.

Most pages answer the anxious worry with features that address the technical one, which is how a parent worried about contact ends up buying a content filter. Naming the worry first makes the page readable.

Worth knowing

Most households discover the worry and the arrangement do not match, which is useful rather than embarrassing: the mismatch is the commonest condition in this subject and it is cheap to correct once named.

One more thing

Ask the question of somebody else's arrangement too. A grandparent or another parent describing what they do produces a better comparison than any product page, and the conversation is usually welcome.