🧩 The 5 SLS OSH Domains (A–E)

These are officially defined in the SLS OSH guide:

🅰️ Domain A

Use SLS for Communication, Scheduling & Non-digital T&L

👉 Focus:

Announcements
Planner (timetable)
Tracking homework (including paper work)

👉 Goal:

Make SLS the single place students check daily

🅱️ Domain B

Department Groups & Resource Consolidation

👉 Focus:

Teachers collaborate
Share lesson materials
Build common resources

👉 Goal:

Reduce duplication
Improve consistency across classes

🅲 Domain C

Student Groups & External Content

👉 Focus:

School-level student groups
Use external tools (e.g. Google, simulations, vendors)

👉 Goal:

Scale learning across classes/schools
Tap external ecosystem

🅳 Domain D

Assessment & Learning Review

👉 Focus:

e-assessment (quizzes, assignments)
School-based assessment (SBA)
Learning analytics

👉 Goal:

Use SLS as the central assessment + data system

🅴 Domain E

Professional Development & Observation

👉 Focus:

Teacher PD in SLS
Lesson observation
Sharing practices

👉 Goal:

Improve teaching using SLS data + artefacts

🧠 Big picture (VERY important)

From the official guide:

These domains are used to organise school-wide processes so SLS can function as a One Stop Hub

And:

When fully implemented, SLS becomes a platform where communication, resources, activities, and data are all in one place

🎯 Simple way to remember

Domain	What it does
A	Daily operations (comms + timetable)
B	Teacher collaboration
C	Students + external tools
D	Assessment + data
E	Teacher learning

💡 Why MOE uses these domains

Because SLS OSH is NOT just:

“teachers using SLS”

It is:

whole-school system integration

The domains help schools:

Plan implementation
Track progress
Ensure consistency

🚀 In your context (very relevant)

You are already working heavily in:

Domain B → resource sharing (MOE Library, ACP)
Domain C → external tools (EJS, xAPI, AI tools)
Domain D → scorable interactives, analytics
Domain E → PD, workshops

👉 Which is why OSH discussions keep coming to you 😄

🧠 First: What “hurdles” mean in OSH context

When we talk about:

“Hurdles for SLS as One Stop Hub (OSH) vs Google Classroom / Microsoft Teams”

We mean:

👉 Why schools don’t fully centralise everything into SLS yet

Even though SLS is designed to be:

the single platform for T&L, communication, data, and assessment

🚧 Key Hurdles (Realistic, Ground-Level)

1. 🧩 Fragmentation of tools (BIGGEST issue)

Reality:

Teachers already use:
- Google Classroom
- Microsoft Teams
- Padlet, Kahoot, Quizizz, etc.

👉 These are:

familiar
fast
flexible

📌 Problem:

Teachers use tools outside SLS → breaks OSH

2. ⚡ Ease of use vs System power

Comparison:

Platform	Strength
Google Classroom	Simple, fast, low learning curve
Microsoft Teams	Strong collaboration, meetings
SLS	Full ecosystem (assessment, data, AI, MOE alignment)

👉 Insight:

GC = easy to start
Teams = good for communication
SLS = powerful but heavier

📌 Hurdle:

Teachers choose ease over integration

Supported by:

Adoption often depends on familiarity & existing ecosystem

3. 🔐 “Single platform” vs “Best tool for task”

SLS OSH philosophy:

Everything inside ONE system

Teacher mindset:

“Use best tool for each task”

Example:

Zoom / Teams → live lesson
Google Docs → collaboration
SLS → assignment

📌 Hurdle:

OSH requires discipline + consistency, not just preference

4. 🔄 Workflow duplication

If not done properly:

Assign in SLS
ALSO upload in Google Classroom
ALSO message in WhatsApp

📌 Result:

Double / triple work

👉 Teachers then say:

“SLS adds workload”

5. 📊 Data not consolidated (critical OSH gap)

OSH promise:

All learning data in ONE place

But if:

Quiz in Kahoot
Work in Google Docs
Feedback in Teams

👉 Data becomes fragmented

📌 Hurdle:

Schools don’t fully realise analytics + tracking value

6. 🏫 School-wide consistency (leadership issue)

From OSH guide:

OSH only works when whole school adopts processes

📌 Hurdle:

Some teachers use SLS
Some use GC
Some use Teams

👉 Result:

No system-wide benefit

7. 🔗 Integration limitations

Even though SLS:

allows embedding
supports integrations

👉 But:

Not all tools are seamlessly integrated
Some require workarounds

📌 Hurdle:

Teachers feel external tools are “smoother”

8. 🧠 Mindset shift (deepest issue)

Teachers often think:

“SLS = just another LMS”

But OSH requires:

“SLS = the SCHOOL SYSTEM”

📌 This is a big cultural shift

⚔️ SLS vs Google Classroom vs Teams (in OSH lens)

Area	SLS (OSH vision)	Google Classroom	Microsoft Teams
Role	Central system	Classroom tool	Communication hub
Scope	Whole school	Subject/class level	Org + comms
Data	Centralised	Fragmented	Fragmented
Ease	Medium	Very easy	Medium
Integration	Controlled	Open	Enterprise

🔥 The REAL core tension

👉 SLS OSH wants:

Standardisation + centralisation

👉 Teachers want:

Flexibility + convenience

💡 Key takeaway (this is how to explain to DD / HQ)

The hurdles are NOT technical.

They are:

1. Behavioural

Teacher habits
Tool preference

2. Organisational

Lack of school-wide processes

3. Perceptual

SLS seen as “one of many tools” instead of “the hub”

🚀 In your context (very sharp insight for you)

Your work (ACP, xAPI, interactives) is actually solving this:

👉 Making SLS:

more powerful than external tools
worth centralising into

🎯 One-line summary you can use

“The key hurdle in SLS as OSH is not capability, but getting schools to shift from a multi-tool mindset to a centralised platform mindset.”

Pages

Wednesday, April 8, 2026