You have looked at young people's online rights and at who is meant to protect them, including platforms themselves. Today the focus is on the companies that build the apps and sites you use: the design choices they make, the rules they work under, and how safety reporting is supposed to work when something goes wrong. You will tear down common features, sort what each one gives you against what it can cost you, and judge where the balance tips.
Every app and site you open is designed. Features such as the next clip starting itself, notifications, infinite scroll and targeted ads are choices someone made.
Digital technology companies sit in three roles at once:
Name one feature you notice every day. Do not decide yet whether it mainly helps or hinders. Next you will sort real effects of common features and decide, with reasons, whether each mainly benefits the user or can mainly work against them.
Work on the interactive activity. Each card states a real effect of a common platform feature in plain terms. Your job is to argue it into a bucket, not to match a tone.
If devices are available, pairs may sort first. Then the class merges one contested card on the board. If not, run the whole sort as a class from the board. The learning is in the reason you give, not in racing to finish.
Now the whole class plays the rest, on your own devices.
Join with the code on the board. Everyone answers every round, not one person per table, and you can change your answer until the time is up. You also say how sure you are: just checking, fairly sure, or certain. The class's split appears on the board once the round closes, then the reasoning.
Getting it right matters less than being able to say why. A right answer earns what you staked and a wrong one loses it, so being unsure and saying so costs you very little - being certain and wrong is what costs. Every round has a defensible answer, and the reasoning behind it is what you are here for.
Work in pairs, then share.
Read this invented situation together:
Jordan, 14, keeps getting private messages from an account they do not know. The messages turn nasty after Jordan ignores the first one. Jordan wants it to stop and does not want the account to keep finding them.
In order, write the five steps you think should happen on your mini-whiteboard or page so you can read them back. Use this skeleton:
Be ready to read your sequence to the class. Before you finish, check a five-step reporting sequence you can defend.
You're previewing this lesson. Get full access to this lesson and hundreds more — each one ready to teach, with interactive activities, printable resources and pupil progress tracking built in.