Editorial audit · Last reviewed

What does it take to keep 117 AI lessons understandable?

This audit examines structure, sources, and reading paths across menCARIE Open Learning. We reviewed 117 lessons in two languages to see whether non-specialist readers receive a short answer, an example, evidence, and a next learning step as the subject becomes technical. The results show a consistent foundation and a limit that still requires reader testing.

Written by Cahyanto Arie Wibowo · 8 minutes

The question

How can 117 lessons stay concise, clear, and verifiable without oversimplifying AI?

Beginner material does not need to be shallow. What should be easier is the path to understanding.

Why it matters

AI often feels difficult not only because of the concepts, but because readers do not know where to begin. A consistent structure helps them build understanding without losing the ability to check sources and the limits of each explanation.

Method

  1. We counted every learning unit in curriculum version 2026.08.24: 8 Learning Series, 39 modules, and 117 lessons.
  2. Automated tests checked every lesson for learning goals, a core explanation, an example, practice, a knowledge check, sources, and a path to related material.
  3. We also compared the Indonesian and English structures. This audit measures structural completeness and source traceability. It does not yet measure comprehension through direct user research.

Evidence at a glance

lessons checked
117
source references placed
351
links to related lessons
351
language versions
2

Findings

Start with a short answer

Readers need the core idea before meeting new terminology. Each lesson therefore opens with a direct answer and adds context in stages.

Examples should connect to decisions

A technology-only example is easy to forget. An example becomes useful when readers can see the decision, risk, or task affected by the technology.

Sources should sit close to the claim

A bibliography alone is not enough. Every lesson includes three checkable references, while titles and review dates make the information's origin visible.

The next path should be visible

Every lesson links to three related lessons. Readers can deepen an idea without guessing another search term or returning to the catalogue.

Practical implications

  1. Keep the short answer before technical terminology.
  2. Test examples and reading order with readers from different backgrounds.
  3. Use reader questions to decide what needs rewriting instead of simply making the material longer.

Sources you can check

  1. How should we define AI?: Elements of AI · University of Helsinki
  2. Explanatory memorandum on the updated OECD definition of an AI system: OECD.AI
  3. People + AI Guidebook: Google PAIR
  4. Data on the Web Best Practices: W3C

Related lessons