On Oct 29th, I delivered a talk on Research in Engineering and STEM Education in SMK Nenasi. This is part of their teacher’s profesisonal development workshop involving 40 teachers from SMK Nenasi.
The session drew on two decades of engineering education research — not as a retrospective, but as a working framework. This post distils the core ideas shared that day: a map of research areas in education, a cycle for turning classroom problems into publishable innovations, and four journal studies that demonstrate what that cycle looks like in practice.
A Framework for Understanding Educational Research
Conversations about education often reduce to familiar binaries — theory versus practice, teacher-centred versus student-centred. These oppositions are real, but they can obscure a more productive question: where, precisely, does a teaching problem live?
I’ve always believe in the framework that position the learning environment as a triangle of relationships: the Educator, the Student, and the Subject. Research in education tends to cluster around the edges and nodes of this triangle, giving rise to seven distinct areas of inquiry:

-
-
-
- Pedagogical research — approaches to teaching that connect educator to student
- Professional Development — how educators continue to grow in their practice
- Curriculum research — the selection, sequencing, and design of subject content
- Educational Technology — digital tools in support of learning
- Learning Sciences — how students learn particular content and skills
- Inclusive Education — equitable access and differentiated support for diverse learners
- Assessment — evidence of learning and feedback across the system
Any classroom problem can be located somewhere on this map. Most substantive problems touch more than one area — which is precisely what makes education research both challenging and consequential.
The Innovation Cycle in Teaching and Learning
Identifying where a problem lives is a starting point, not a solution. What translates observation into evidence is a systematic process. The Innovation Cycle in Teaching and Learning — Identify, Design, Apply, Evaluate — provides that structure.
-
-
- Identify. Define the problem precisely, through observation, diagnostic assessment, and engagement with existing literature. Vague problems produce vague solutions.
- Design. Develop an intervention grounded in educational theory. The design phase should be evidence-informed, not intuition-driven.
- Apply. Implement the intervention with real learners in a real context, with appropriate instruments in place to capture what happens.
- Evaluate. Analyse the data rigorously. Determine what worked, for whom, and under what conditions — then feed those findings back into a new cycle of Identify.
The cycle is not linear; it is iterative. Each pass through Evaluate generates a more precise version of Identify. Over time, this compounding of evidence produces not just better teaching practice, but publishable, replicable research that contributes to the broader field.
“Good teaching is, at its core, a form of research. Every classroom problem is a research question waiting to be asked properly.”
Four Studies: The Innovation Cycle in Practice
The following four studies in UMPS STEM Lab illustrate how this cycle operates across different educational contexts, learner populations, and research areas. Each began with a documented classroom problem; each produced findings published in internationally indexed journals.
Study 1 — Game Development-Based Learning and Programming Skill Acquisition

Noordin, N.H., & Karunanthini, G. (2026). Evaluating the impact of game development-based learning on programming skill acquisition and student engagement. International Journal of Evaluation and Research in Education (IJERE), Vol. 15, No. 1.
DOI: 10.11591/ijere.v15i1.35542 · Q2, SCOPUS-indexed
Research Area: Pedagogical · Learning Sciences · Educational Technology
The problem: Secondary school students encounter a well-documented gap in computing education — the ability to follow a worked programming example does not automatically translate into the ability to work independently. Form 1 students in a block-based programming context demonstrated strong performance during guided tasks and significant difficulty the moment that guidance was withdrawn.
Through the Innovation Cycle:
- Identify: Students lacked the structured progression needed to move from dependent to independent programming. The gap was not motivational but scaffolding-related.
- Design: A four-stage Full→Minimal scaffolding framework, with the development of a Snake Game in mBlock as the learning context. Game development was selected deliberately: it provides a meaningful goal that sustains engagement across multiple sessions.
- Apply: Students worked through four progressively less-supported activity sessions, building a fully functional game by the final stage.
- Evaluate: Pre- and post-test computational thinking scores, algorithm design quality, and block-programming error analysis. Result: Cohen’s d ≈ 1.86 — a very large effect size by conventional standards. Gains were observed in both achievement and self-reported engagement.
Key finding: Scaffolding design — not simply task design — determines whether students can transfer programming knowledge to novel problems.
Study 2 — The STEM Cube: Bridging Abstract Concepts and Physical Making

Noordin, N.H., Abdullah, K.K.B.H., & Eu, P.S. (2024). Assessing the effectiveness of UMP STEM Cube as a tool for developing digital making skill sets. IEEE Transactions on Education, pp. 1–11.
DOI: 10.1109/TE.2024.3376448 · Q1, IEEE
Research Area: Educational Technology · Curriculum · Learning Sciences
The problem: A structural weakness in STEM education is the tendency to teach Science, Technology, Engineering, and Mathematics as discrete disciplines. Students arrive at university able to calculate within a subject but unable to integrate across them — competent in isolated domains, underprepared for interdisciplinary engineering work.
Through the Innovation Cycle:
- Identify: Engineering students lacked hands-on, integrated experience with IoT systems and physical computing. Existing curricula addressed components of STEM separately, not as a unified practice.
- Design: The STEM Cube — a compact, 3D-printed kit (56×65×30 mm) integrating sensors, a servo motor, LEDs, and a microcontroller, programmable in both Arduino and Python. The physical artefact was designed to make cross-disciplinary integration tangible and unavoidable.
- Apply: Students assembled, programmed, and tested the STEM Cube in project-based sessions, applying physical computing skills to self-defined engineering challenges.
- Evaluate: Digital making skill sets assessed using validated measurement instruments. Results demonstrated significant gains across hardware integration, programming fluency, and design thinking — published in IEEE Transactions on Education, one of the field’s leading Q1 journals.
Key finding: Tangible, integrated learning objects can bridge the gap between disciplinary knowledge and cross-disciplinary application more effectively than software-only environments.
Study 3 — Computational Thinking Through Scaffolded Game Development

Noordin, N.H. (2025). Computational thinking through scaffolded game development activities: A study with graphical programming. European Journal of Educational Research, 14(4), 1137–1149.
DOI: 10.12973/eu-jer.14.4.1137 · Q2, SCOPUS-indexed
Research Area: Learning Sciences · Pedagogical · Assessment
The problem: A persistent concern in game-based learning research is whether students develop transferable thinking skills or simply learn to complete the specific task at hand. For programming education, the question is pointed: does building a game teach computational thinking, or does it teach game-building?
Through the Innovation Cycle:
- Identify: First-year university students struggled with abstract Python object-oriented programming concepts. Without a meaningful goal, engagement and retention were low. The question was whether a structured game-development sequence could develop computational thinking as a generalised competency, not merely task performance.
- Design: Seven sequential Pygame activities, moving from simple object manipulation to a fully playable slider puzzle game. Each activity introduced exactly one new computational concept — decomposition, abstraction, pattern recognition, or algorithmic design — before the next was added.
- Apply: Implemented with 310 first-year students across a semester-1 programming course, in studio-style sessions conducted over multiple weeks.
- Evaluate: Pre- and post-assessment of computational thinking using validated instruments. Significant gains in decomposition, abstraction, and algorithmic thinking — not merely game-making performance — confirming that the learning was transferable.
Key finding: Scaffolded game-development sequences can develop computational thinking as a generalisable skill, provided the design isolates and builds each thinking dimension deliberately.
Study 4 — AI Scaffolding in Programming Education

Noordin, N.H. (forthcoming). AI scaffolding in programming education. IEEE Transactions on Learning Technologies.
Accepted; DOI pending · Q1, IEEE
Research Area: Educational Technology · Inclusive Education · Learning Sciences
The problem: In large programming cohorts, instructor-to-student ratios make real-time, personalised scaffolding practically impossible. Students who struggle may not receive timely support, and by the time difficulty becomes visible it has often compounded. Artificial intelligence offers a potential structural solution — but only if the scaffolding it delivers is pedagogically sound and equitably distributed.
Through the Innovation Cycle:
- Identify: Large-cohort programming courses cannot provide adaptive scaffolding at the individual level through human instruction alone. The gap between strong and struggling students widens precisely because those who most need responsive support receive it least.
- Design: An AI-powered scaffolding system designed to respond in real time to learner behaviour within a programming environment, delivering calibrated hints and prompts based on each student’s current state rather than a fixed sequence.
- Apply: Deployed within a programming education context. Students received dynamic AI-generated guidance while working through programming challenges, with no change to their instructor contact time.
- Evaluate: Results accepted for publication in IEEE Transactions on Learning Technologies (Q1). The findings confirmed that AI scaffolding produced measurable learning gains — and revealed a significant pattern in which students benefited most, with important implications for equity in programming education.
Key finding: AI scaffolding in programming education is not simply an efficiency tool. Its most significant contribution may be to equity — reaching learners who are systematically underserved by conventional large-cohort instruction.
From Research to Practice: What This Means for Teachers
The four studies above were conducted in higher education settings, but the framework underpinning them is not institution-specific. The Innovation Cycle in Teaching and Learning is as applicable in a secondary school classroom as it is in a university research project.
A teacher who notices that students disengage during a particular topic has completed the first step: they have Identified a problem. The question is whether the response will be intuitive — a minor adjustment next time — or systematic: a Designed intervention, Applied with observation, and Evaluated with evidence.
The difference between those two responses is not access to a research grant or an institutional affiliation. It is the discipline of asking the problem precisely, building a response theoretically, and measuring what actually happens. That discipline is available to any educator. It is, in a meaningful sense, what professional teaching is.
The seven research areas in the triangle framework are not an academic taxonomy. They are a prompt: Which relationship is under strain — between teacher and student, between student and subject, or between teacher and subject? Locating the problem correctly is half the solution.
Conclusion
Two decades of research in engineering education have produced one consistent finding above all others: the classroom problems that resist easy solutions are almost always the ones worth studying. The gap between imitation and independent thinking in programming. The disconnect between disciplinary knowledge and integrated practice in STEM. The invisibility of struggling students in large cohorts. These are not incidental frustrations — they are the defining challenges of the field, and they are solvable through systematic, evidence-based inquiry.
The Innovation Cycle offers a structure for that inquiry. The Research Areas framework offers a map. What teachers and researchers bring to both is the most important element of all: sustained attention to the learner, and a commitment to acting on what that attention reveals.
References
Noordin, N.H., & Karunanthini, G. (2026). Evaluating the impact of game development-based learning on programming skill acquisition and student engagement. International Journal of Evaluation and Research in Education (IJERE), 15(1). https://doi.org/10.11591/ijere.v15i1.35542
Noordin, N.H., Abdullah, K.K.B.H., & Eu, P.S. (2024). Assessing the effectiveness of UMP STEM Cube as a tool for developing digital making skill sets. IEEE Transactions on Education, pp. 1–11. https://doi.org/10.1109/TE.2024.3376448
Noordin, N.H. (2025). Computational thinking through scaffolded game development activities: A study with graphical programming. European Journal of Educational Research, 14(4), 1137–1149. https://doi.org/10.12973/eu-jer.14.4.1137
Noordin, N.H. (forthcoming). AI scaffolding in programming education. IEEE Transactions on Learning Technologies. [Accepted; DOI pending]
https://nurulhazlina.github.io/eduResearch/PdPcNenasi














