When a local authority announces a rule about phones in youth spaces, the discussion often begins with adults who already have a settled position. Some speak about distraction, others about safety, others about freedom of choice. Meanwhile, the young people affected by the rule are often treated as a number, a risk, or an audience that needs the decision explained to them. They are rarely treated as people who can describe which part of everyday life the debate is failing to see. That order matters. Consulting them at the end, after the text is settled and only the colour of a poster remains to be chosen, is not the same as bringing their experience in while it can still change the problem being addressed.
Listening does not mean moving onto children a responsibility that belongs to institutions and adults. Nor does it require accepting every participant's proposal word for word. It means recognising that technology rules affect timetables, friendships, homework, privacy, and ways of asking for help that cannot be spotted from an office. A rule can arise from a reasonable concern and still fail because it imagines a simplified use. If the only voice that counts is the voice of the system's designer, a measure may look flawless on paper and become unfair at precisely the moment a young person needs more room or support.
The useful question is not whether minors should decide everything. It is much more specific: at what point in the process can they point to a consequence no one anticipated, and what obligation do adults have to answer that observation? Put that way, the question avoids two familiar extremes. One is decorative consultation, which turns participation into a photograph for an annual report. The other is asking teenagers to solve alone problems of protection, inequality, or commercial design that they did not create. Between those extremes lies institutional work: preparing understandable information, opening safe spaces, testing different experiences against each other, explaining constraints, and leaving a record of how a contribution did—or did not—change a decision.
Experience is not an anecdote#
Consider a school weighing a phone ban for the entire day. Its intention may be to reduce interruptions and ease conflict in lessons. But a phone's actual journey does not end when the bell rings. Some students coordinate family care after school; others check a change to a work shift; someone needs to know whether they can get home because transport has been disrupted. Others use a device to step away for a few minutes from an uncomfortable conversation, which may be a difficulty requiring support or a sign that they have no other safe place. None of these situations automatically invalidates a rule. They do require a distinction between use that interrupts a lesson and a need that cannot fit within a generic permission.
Consider a school weighing a phone ban for the entire day. Its intention may be to reduce interruptions and ease conflict in lessons.
A well-designed conversation can uncover that difference without requiring anyone to disclose private matters. Rather than asking, “Who needs a phone, and why?”, organisers can offer fictional scenes: someone is waiting for news about a younger sibling; someone else receives persistent messages from a group; another student has no mobile data at home and uses the school network; another is afraid their phone will be searched. Responses make it possible to discuss journeys rather than personal case files. They also show that the same tool does not mean the same thing to everyone. The institution stops debating an abstraction called “screen time” and begins examining concrete conditions of access, care, and conflict.
Difference within childhood is decisive. There is no standard young user. Age, independence, language, disability, family relationships, where a person lives, and access to shared devices all alter the experience. A consultation made up only of those who speak easily in a meeting or already take part in school associations may reproduce the very absence it set out to correct. That is why formats should be combined: small-group conversations, anonymous contributions, mediated sessions, visual materials, and times that do not always conflict with extracurricular activities. Participation must not become a privilege for those who have the time, confidence, and transport to attend.
The choice of listeners needs care too. If a young person explains that a measure leaves them out and receives a defensive reply or a moral lecture, the process teaches the opposite of what it promises. Adults facilitating the conversation need to distinguish disagreement from disrespect, ask for examples without pressing, and acknowledge when they have no immediate answer. Serious listening is not extracting a striking quotation that confirms a prior conclusion. It is allowing an uncomfortable experience to require a review of a category, an exception, or the way a rule is communicated.
From testimony to a decision that can be checked#
Collecting opinions is not enough. An institution can gather workshop notes and still leave unchanged a design that harms the people who attended. For participation to have an effect, each stage should answer a different question. Before a decision, it helps identify the problem: what situation is meant to improve, and for whom? During design, it helps test alternatives: what happens if the rule applies at break, at the end of the day, or during an emergency? After launch, it helps identify harm and make corrections: who has stopped using a service, who has struggled to ask for help, and what explanation is missing?
Now imagine a library planning a digital booking system for youth activities. A meeting with teenagers may show that platform speed is not the only issue. Perhaps the slot opens when some are training or caring for relatives. Perhaps the notification arrives at an account shared at home. Perhaps someone on the waiting list cannot tell whether they may attend anyway. A responsible outcome does not have to mean abandoning digital booking. It might mean keeping an in-person route, extending the deadline, publishing the order in plain language, and naming a person to resolve exceptions. The difference is that those measures are no longer presented as favours: they answer an access condition the system must secure.
There should be a clear public response. It need not include names, personal accounts, or a transcript of every meeting. It should say what was heard, what changed, what did not change, and why. “An alternative channel will remain because several people identified time barriers” is more honest than a vague statement that “young people were considered.” When a proposal cannot be adopted, explaining that also teaches participation: disagreement does not create an automatic promise, but it should create a reasoned answer. Without that return, participants learn that sharing their experience is an act without consequences.
Traceability also protects against a common trap: using a consultation to legitimise a decision already made. If the purpose, alternatives, and criteria are published in advance, it is harder to turn an open question into a leading survey. An institution can explain the legal, budgetary, or safety constraints it faces, but it should not hide them only to present them later as an unavoidable surprise. Knowing the real room for manoeuvre makes proposals more precise. Sometimes a young person will not ask to “remove the rule”, but to create a reviewable exception, improve an alert message, or provide a place to speak with someone without being exposed in front of a group.
Protection must include the power to correct#
One idea needs to change: protecting children and teenagers is not only a matter of moving them away from risk. It also means giving them a safe way to point out when protection has become a barrier. A content filter can block health information; parental controls can reveal a search that someone is not ready to discuss; a school app can record a lack of connection as indifference. In these cases, the response should not be, “That is how the system works.” There should be a human review route that is accessible and does not punish someone for asking for help.
That review must be usable in practice. A link buried at the end of terms of service does not help someone who is anxious, unfamiliar with administrative language, or afraid that a complaint will reach the wrong person. The route should explain in plain words what may be challenged, who will read the request, how long it may take, and what happens in the meantime. For minors in particular, asking for a review should not require exposing their whole personal story at the outset. They can begin by describing the failure, receive support from a trusted person, and be asked for more information only when it is needed to resolve the issue.
Institutions must also be ready to learn from unexpected uses. A teenager avoiding an app is not always demonstrating irresponsibility; they may be showing that the interface is confusing, that notifications intrude on rest, or that the service assumes resources they do not have. This does not make every action correct or remove the need for limits. It changes the starting point: before imposing a sanction, it is worth asking which design produced the friction and whether the same pattern appears for others. A robust measure does not fear that examination. It needs it to distinguish an isolated breach from an organisational failure.
Participation can also create mutual literacy. Adults know responsibilities, budgets, and consequences that are not always visible from a classroom. Young people know group codes, silences, and dependencies that rarely appear in a technical report. When both perspectives meet under rules of respect, the conversation need not romanticise either. It can show that a platform is not neutral, that one household's convenience may become another's burden, and that a general rule needs clearly explained exceptions if it is to be fair. That shared understanding is more useful than any slogan about responsible innovation.
Start with a question that can be corrected#
There is no need to create a grand assembly in order to begin. A cultural centre, school, or municipal service can choose a nearby decision—the hours for a support channel, rules for a digital group, the way an activity is booked—and trial a short process. First, describe the problem without treating the solution as settled. Next, offer two or three alternatives and their consequences. Then seek responses from varied groups and publicly report what was learned. Finally, set a date to review whether the measure works differently for different people. The key is not the ceremony; it is that the question is genuinely open.
The voice of children and teenagers does not replace the adult duty of care. It makes that duty more demanding. It requires a move from intuition to testing, from an abstract rule to lived experience, and from a promise to listen to visible correction. When people who use a technology can identify where it protects them, where it limits them, and where it leaves them alone, a decision gains information that no expert panel can generate by itself. Making space for that voice is not a gesture of courtesy. It is a condition for rules governing connected life to deserve trust.
