The edutainment glossary: the terms that recur in every project

Why a glossary, and not just one definition?

Dozens of terms recur in any serious conversation about a digital experience for children: the gray prototype, the guardrail metric, data minimization, and others. Some are industry standards anyone in this field would recognize. Others are internal names we use for a practice we hold to, and we do not claim anyone else calls it by the same name. Reading the process page, the safety page or the evidence page, you meet these terms scattered inside a longer piece explaining one whole idea. This glossary gathers them in one place: fifteen terms, each with one plain definition and one line on where it shows up inside a real project. The aim is that you can read the rest of the site without stopping at an unfamiliar word, and that you can write to us in precise language.

What are the terms of making the idea?

• Edutainment. A child learns something useful while playing and enjoying it, without feeling they are in a lesson. If the play could be removed and the benefit survived untouched, what was built is not edutainment. It is a lesson with decoration added. In any project, this is the first question settled: is the goal educational content shaped as play, or a dry lesson with colour added on top?
• Storyboard. Drawn shots arranged on one board and reviewed frame by frame before any real screen gets built. In a real project this is the first document the whole team sees together, and a crossed-out frame stays visible on the board, because knowing what failed is part of the work itself, with nothing hidden afterward.
• Gray prototype. A playable build with no colour, no sound and no final art, built for one purpose: testing whether the play itself is fun before it is decorated. In any serious project, this is the form a commissioning body should see before a coloured pitch, not after it.
• Child test. A session where real children try the gray prototype with their parents' consent, and their sentences are recorded exactly as spoken with no premature interpretation. In any project involving children, this is the stage that separates a design only adults have seen from one approved by the people it was made for.

What are the measurement terms?

• Success indicator. The observation or number telling us the goal a project started from was actually met, not merely that the experience was used. In any project, this indicator is chosen before building, not after, because what gets chosen at the start decides what gets improved after launch.
• Guardrail metric. A separate indicator that watches one specific possible harm, such as usage being hidden rather than reduced, or anxiety rising in the name of discipline. In any project involving children or teenagers, the absence of this indicator from an impact report is itself a warning sign, whatever the rest of the numbers look like, which is why the documentation standard on our evidence page treats it as a requirement rather than an option.
• Proximal and distal indicator. A proximal indicator moves during the program itself and can reasonably be attributed to it, such as a repeated intended behaviour or a skill shown in a specific task. A distal indicator, such as academic attainment or mental health over years, cannot honestly be claimed without a rigorous research design. In any project, the common mistake is measuring the proximal and then claiming the distal, which is exactly what we hold ourselves to never doing.
• Observed, measured, interpreted. Three kinds of results sentence that should never be mixed: what the team saw with no formal tool, what was measured with a declared instrument and time window, and what meaning we read behind the number. In any impact report, tagging each sentence with its correct kind is what keeps an assumed figure from slipping into a table of real results.

What are the safety terms?

• Session end. The design decision that determines how an experience stops: at a natural boundary such as a closing chapter or a completed level, not at a manufactured cliffhanger that pulls a child into another round. In any project, this decision deserves a conversation at the design stage rather than being left to chance after launch, as we explain on our safety page.
• Age-appropriate design. The safest setting is the default, not an option in a menu waiting for someone to find it. In any project serving different age bands between 4 and 17, this means settings built around an age band rather than one number meant to fit everyone.
• Data minimization. Every data field is questioned before it is added: what breaks if we do not collect this? Whatever the experience runs fine without is not collected at all. The US Federal Trade Commission states the principle inside its children's online privacy rule, and the UN Committee on the Rights of the Child states it among the privacy-by-design principles in its General Comment No. 25. In any project, this means a shorter sign-up field, not a long form that only looks professional.
• Dark patterns. Deliberate interface tricks that push a user toward an action they did not intend, such as a cancel button that is hard to find or a confirmation designed to read as a refusal. A US Federal Trade Commission staff report titled "Bringing Dark Patterns to Light" examined the problem in September 2022. In a children's project, their absence is not a cosmetic detail but an ethical condition, because a child is less able than an adult to spot the trick and back out of it.

What are the production and language terms?

• Transcreation. Rewriting a text in a new language to preserve its effect rather than its exact words, unlike a literal translation that carries words across and leaves the cultural meaning behind. Across every article on this site, the Arabic version is the original and the English is a transcreation of it, never the other way around.
• Illustrative example. An explicit tag placed above a scene or an imagined character used to explain an idea, so the reader knows they are looking at an illustration rather than something that actually happened. In any project, this tag does not launder a sentence written in the finished past tense; an illustrative example is written in a visibly different form from the start, not disguised as one.
• Evidence gate. The name we use internally for the simple rule governing everything we publish: no number without a source, no anecdote about a specific child, and no promise we have no reason to keep. The public face of that rule is the What we can prove page, where we sort everything we say about ourselves into exactly three kinds.

Where should you start using this glossary?

If you are reading the process page, the safety page or the What we can prove page and meet a term that deserves more explanation, this glossary is your reference before you ask. If you are drafting a tender document for a children's experience, some of these terms, such as the guardrail metric and data minimization, are worth writing into the document itself, not leaving to a later conversation. You can tell us about your project through the Start a project form, or read our article on ten questions we suggest asking any studio before commissioning one.

References

• US Federal Trade Commission, six-step compliance plan for the Children's Online Privacy Protection Rule (COPPA), retrieved 6 September 2026: https://www.ftc.gov/business-guidance/resources/childrens-online-privacy-protection-rule-six-step-compliance-plan-your-business
• US Federal Trade Commission, staff report "Bringing Dark Patterns to Light" (September 2022), retrieved 6 September 2026: https://www.ftc.gov/reports/bringing-dark-patterns-light
• UN Committee on the Rights of the Child, General Comment No. 25 (2021) on children's rights in relation to the digital environment, CRC/C/GC/25, including privacy by design and data minimization. An official reference named without a link.

Quick questions

Do all studios use these exact terms?

Some are general industry standards, such as edutainment, transcreation and dark patterns. Others are our own internal names for a practice we hold to, such as the evidence gate and the illustrative-example tag. Each definition above marks which kind it is.

Why isn't a literal translation of a term like edutainment enough?

A literal translation carries the words across and leaves behind the cultural assumptions the original term was built on. That is why we call moving this site into English transcreation rather than translation: the Arabic is the original, not a copy of a foreign one.

How does this glossary help a body writing a tender document for a children's experience?

It gives them precise language to ask different studios the same question with the same term, instead of each side reading a phrase like guardrail metric or data minimization its own way. A precise term in the tender document rules out a vague answer that only sounds convincing.