Skip to main content
EMU

Doctrine

Methodology that starts with functionality, then earns performance.

The EMU methodology preserves three strategies from the legacy archive, organizes work through the five-stage Quality Improvement model, and keeps district, school, and learning levels connected.

Three strategies

Data, systems, and ICT are the enduring spine of the EMU methodology.

01

Data Driven

The legacy methodology describes a data-driven, evidence-based decision-making process for analysing education challenges, formulating a clear business case, and constructing a preferred future. The phrase retained across the site is: without data, you are just another person with an opinion.

02

Systemic Thinking

The legacy archive distinguishes systemic thinking from systems or systematic thinking. The working assumption is that education outcomes sit inside interacting structures; changing outcomes requires changing the system that sustains the current situation.

03

Use of ICT

ICT is positioned as a big-picture tool for improving education-system efficiency and effectiveness, including GIS and cellular technology. The doctrine is careful about sequencing: standard operating procedures must exist before ICT can create durable performance gains.

Quality Improvement model

A project-management cycle for moving from diagnosis to impact.

The five stages are preserved as doctrine. The surrounding page copy is modernized only to make the model clearer for current institutional audiences.

01

Case Analysis

Analyse the case before prescribing a solution. This stage protects the work from opinion-led intervention design.

02

Input

Match the right support to the diagnosed system constraint instead of flooding a weak process with generic resources.

03

Process

Define the operating procedures, routines, and responsibilities that let the system become functional before it is asked to perform.

04

Output

Track whether the process is producing the expected outputs, not only whether activities were completed.

05

Impact

Assess the difference made to learners, schools, and district capability once the cycle has been implemented.

Three focus levels

District, school, and learning keep the improvement work connected.

District

District

The district level translates policy intent into operational support, monitoring, and quality-management routines across schools.

School

School

The school level builds functionality through leadership rhythm, operating procedures, governance, and management discipline.

Learning

Learning

The learning level keeps the purpose of the system visible: improved teaching, learning, understanding, and learner outcomes.

Source integrity

Protected doctrine is separated from modern marketing copy.

Protected doctrine

Three strategies

Data Driven, Systemic Thinking, and Use of ICT remain the strategic spine of the site.

Protected model

Five QI stages

Case Analysis, Input, Process, Output, and Impact are preserved as the Quality Improvement project-management model.

Historical context

8.1% EMIS claim

The 2005 EMIS success claim is treated as historical context only and is not reused as a current performance claim.

Unconfirmed now

Legacy contact data

Historical phone, email, resource, and partner details are not republished as current until confirmed.

Core principle

Functionality has to precede performance.

The site carries this as an operating principle and connects it to the Library of Excellence conversion path.