The Majlis of AI ACADEMY
Academy / The Tao The Tao · How people learn at the Academy

The way we teach

Tao means the way. These are the learning principles behind every Majlis Academy programme, and the rules we keep while we build and run them.

01 · The Tao

We start from what people must do, then design back to the lesson

Six principles from learning science govern every programme. Each one has a check in the factory, so the principle survives production at speed.

Backward design

Objectives first, evidence second, activities last

After Wiggins and McTighe. Each objective has a measurable verb at a stated Bloom level. A script checks that every objective has evidence and activities.

Gate G2Alignment matrix
Designs every syllabus
Cognitive load

Short units, deliberate pacing, no extraneous load

Cognitive Load Theory and Mayer's multimedia principles. Content comes in 6–12 minute micro-lessons with retrieval breaks.

ChunkingRetrieval practice
Audits slides, labs and media
Active learning

Practice on cases from your own sector

Branching cases from banking, telco and government. Role-plays, jigsaws, debates, and ArchiMate and Wardley-mapping exercises.

CasesGroup work
Classroom, online and hybrid
Transparent assessment

Learners know the purpose, task and criteria

TILT assessments, calibrated rubrics and peer review. Labs use deterministic graders, so the same answer always gets the same result.

TILTGate G4
Fair, repeatable evidence
Community of Inquiry

Cohorts learn from each other

We build teaching, social and cognitive presence. Clear norms, onboarding, weekly prompts and wrap-up digests keep a cohort active.

CohortsNorms
Online and hybrid delivery
Plain language

Technical text in Simplified Technical English

Learner-facing material follows ASD-STE100: one instruction per sentence, verb first, one word for one meaning. Framework terms stay exact.

ASD-STE100Gate G3
Clear for every first language
Decide what they must do. Then teach to it.
The design rule behind every Majlis Academy package
02 · Principles

Six rules hold the system together

The rules are not strict procedures. They are the organising principles that every programme, team and tool keeps, from the first meeting to the hand-over.

Own it

Build capability inside, do not rent it

Every engagement ends with your people running the Brain, the skills and the gates. We plan the hand-over on day one.

Outcome · client owns its training capability
Sit together

Decide with the people who do the work

Sponsors, architects, risk and learners shape each programme in one room. Equal voices, one shared question.

Applied in · scoping and plan approval (D2)
Listen first

Start from the capability gap

We ask what people must do differently before we write a slide. The objectives come from that answer.

Applied in · backward design
Speak plainly

One instruction per sentence

Learner text follows ASD-STE100. Framework terms stay exact: BIAN, ODA, eTOM, SID, TOGAF, ArchiMate.

Applied in · gate G3
Show the structure

Draw the real shape of each framework

Architectures in ArchiMate, strategy in Wardley maps, decisions in DMN. A picture people can check, not a metaphor.

Applied in · every visual asset
Knowledge as code

Every fact has a source and a review date

Content lives in Git as OKF concepts. A change in the world finds every package it affects.

Applied in · gates G1 and G5

G1 to G5 are the quality gates and D1 to D5 the human decisions. See them in the method.

Work with us

Start with one stream and one pilot

Tell us the capability your teams need. We propose a first package, the team set-up and the path to run it in-house.