Ask a question someone can answer
‘What would improve school?’ can produce an important conversation, but it is difficult to connect every answer to a decision. A narrower question makes the next step easier to see. For a fictional review of a homework portal, ask which step prevents a student from finding the current assignment and where they expected that information to appear.
The narrow question is not a substitute for wider discussion. It is a way to make one piece of feedback actionable. Tell participants what the review covers, what lies outside it and when they will receive a response. If nobody has authority to change the portal, find that person before asking students to spend time reviewing it.
Separate the observation from the proposed fix
In our portal example, ‘put everything in an app’ is a proposed solution. ‘I opened three folders and still could not find today’s assignment’ describes a problem to investigate. Keep both. The first expresses a preference; the second gives the team a route it can inspect.
Invite students to describe the steps they took without recording passwords, private messages or identifiable information about other pupils. If a demonstration is useful, use a sample account and invented records. A useful account of a barrier should not require publishing someone’s personal schoolwork or circumstances.
Use a response record that fits on one page
UNICEF’s participation checklist emphasizes genuine influence, suitable language, preparation and safety. Our proposed response record translates those concerns into a small follow-up routine. It is an editorial suggestion, not a UNICEF template or a tested measurement instrument.
Use four headings: ‘What we heard’, ‘What we checked’, ‘What we decided’, and ‘When we will look again’. Under each, record a specific action or finding. If an item needs more investigation, say who owns it and give a realistic review point. Do not label an issue resolved just because it was passed to another department.
Return the response through more than one route
A response hidden inside the same confusing portal can repeat the problem that prompted the exercise. Put a plain-language summary where the original participants can find it, and offer a route to correct a misunderstanding. Ask a participant to read the summary before distribution, without expecting that person to endorse every decision.
Keep disagreement visible. ‘We moved the assignment link but did not adopt the proposed app because it would create a second login’ tells a different story from ‘students supported our new portal.’ The example decision is invented. Its purpose is to show the difference between reporting a response and manufacturing agreement.
Review the change, not the enthusiasm
At the agreed review point, repeat the relevant task. Can students now find the assignment? Which step is still unclear? A positive reaction to the meeting does not answer those questions. Equally, one successful demonstration cannot establish that every learner now has access.
Keep the record small enough that it will actually be maintained. One unresolved problem with an accountable owner is more useful than a long list of promises nobody revisits. End with the next decision and the route for contributing to it. That is where listening becomes a continuing practice.
Sources and further reading
- UNICEF: Adolescent participation checklist
- UNICEF: Engaged and Heard! Guidelines on adolescent participation
Sources checked 6 November 2026. Exercises and scenarios are editorial suggestions, not reported fieldwork.
