Routes by Role

Nine hand-picked paths through the guide, one for each kind of reader, with a line on why every page is there.

The five tracks run from Novice to Expert, but most people do not arrive with a level in mind. They arrive with a job, a classroom or a family. A teacher and a software developer both need “AI explained”, but they need different pages, in a different order, for different reasons. Each route below picks nine to thirteen pages from across the guide, in the order that builds best for that reader, and says in one line why each page earns its place.

How to use a route

Pick the role closest to yours and start at step one. Each page takes ten to twenty minutes; one or two a sitting, a few times a week, will finish most routes within a month. Mark a page as read at its end and the route below ticks it off and points you to the next step. Progress is shared with the track checklists, so a page read on one route counts everywhere. It is stored only in your own browser.

Routes are a starting point, not a fence. If a page is too basic, skip it; if one is too hard, the earlier pages of its own track fill in what it builds on. When a route ends, the track finder suggests where to go deeper. This guide’s framing The roles and the choice of pages are editorial judgements, not an official curriculum.

Teachers and lecturers

Plan lessons with AI, set fair rules, and teach students to question it.

Your students are already using these tools. This route starts with what they are and how they fail, moves through the habits worth modelling in class, and ends with the evidence on AI in learning and where Malaysian education stands.

Students

Study with AI rather than instead of studying, and stay on the right side of the rules.

Used well, an assistant is a patient tutor; used badly, it does the thinking you were meant to practise and occasionally invents a reference that costs you marks. This route is about the first kind of use.

Managers and business owners

Decide where AI helps your team, what it costs, and what rules you need.

No code, and no vendor recommendations. The route covers what the technology can and cannot do, how to choose and review it, the policies and laws that apply, and the scams that now target companies directly.

Office professionals

Write, summarise, analyse and automate the daily work, accurately.

The most practical route on the site. It goes from a first conversation to structured prompts, long documents, spreadsheets and simple automations, with the checking habits that keep errors out of your name.

Parents and families

Understand what children meet online and keep the whole family safe.

Gentle and jargon-free. It explains AI well enough to talk about it at home, separates real risks from scary headlines, and covers privacy, voice-cloning scams and deepfakes. It ends by trying an assistant together.

Public servants and policymakers

Understand the technology well enough to govern, buy and use it responsibly.

Enough technical grounding to question a vendor or a proposal, then the policy questions: bias and accountability, regulation abroad and in Malaysia, privacy, jobs, energy and the AGI debate, each with the main positions set out side by side.

Health, legal and finance professionals

Use AI where the cost of an error is high, without breaching duty or confidence.

In regulated work the question is less “can AI do this?” than “can I stand behind the result?” This route concentrates on reliability, verification, confidentiality and the rules on high-risk uses. It is general background, not professional or legal advice; your regulator’s and employer’s guidance comes first.

Software developers

Build reliable products on language models, and understand what you are calling.

Assumes you can already program. It starts at the API and goes through retrieval, tool use, shipping and evaluation, then dips into the Advanced and Expert tracks to explain the model behind the endpoint. It finishes with a capstone you build yourself.

Career switchers into AI

Build the skills and portfolio for a first job in data or AI.

The longest route, and the only one that assumes no coding at all. It builds Python, data handling and classic machine learning step by step, then language-model applications, and ends with the job market and how to show your work.

Not your role?

If none of these fits, three other ways in work for anyone:

Suggestions for new routes are welcome.

// Pause and reflect

  1. Which route is closest to your work, and which page on it do you most need this week?
  2. Who else in your team, class or family would benefit from a route, and which one?

Your notes are saved privately in this browser.

Key terms on this page

Sources & further reading