A friend and former teacher shared an idea for making curriculum planning easier with AI. On a digital whiteboard, we mapped her experience from first-year teacher to Mathematics coordinator.
Two opportunities emerged: supporting early career teachers with limited classroom experience to draw on, and improving relief handover. I developed SageBox through Product Design and Customer Experience coursework, focusing on curriculum-to-lesson planning.
The challenge
New teachers need to interpret curriculum requirements, organise a teaching sequence and prepare lessons across their allocated subjects and year levels.
My starting hypothesis was that a guided planning tool could help them translate those requirements into classroom-ready lessons. Research would need to establish where support was most useful and whether the proposed tool reduced their work.
Researching the opportunity
I combined a teacher interview and journey map with a 14-response survey, secondary research, prototype testing and concept testing.
Three findings shaped the direction:
-
Classroom credibility mattered: 13 of 14 respondents rated classroom-tested resources as important or highly important.
-
More resources were insufficient: the opportunity centred on making material usable without extensive adaptation.
-
The target audience needed further research: only one survey respondent was in their first year. The findings largely reflected experienced teachers.
I treated early career teachers as a segment to investigate further.
The turning point
I asked my teacher collaborator to use the prototype to plan a curriculum-aligned Mathematics lesson.
The task was not completed after 35 minutes.
Her feedback exposed a problem with the proposition: empty curriculum slots could create more work, while displaying curriculum codes did little to help teachers scope and sequence learning.
Concept testing reinforced this distinction. She valued support for lesson dependencies and identifying gaps in a teaching sequence.
Shaping the solution
The findings shifted my design priorities towards:
-
Keeping curriculum standards accessible within the planning workflow.
-
Balancing guidance with teacher control over scope and sequence.
-
Connecting individual lessons into a coherent learning experience.
The proposed experience supported two planning cycles: establishing a curriculum sequence before teaching begins and preparing lessons during the week.
Adapting an existing school curriculum plan to specific student needs was deferred from the prototype following feedback.
Defining success
I developed a Get-Keep-Grow strategy with measures tied to specific product behaviours:
-
Activation: export a completed curriculum plan or plan a full week of lessons.
-
Value: assess effort after curriculum planning and satisfaction with generated lesson plans.
-
Retention: measure whether teachers return the following term, accounting for school holidays.
These were proposed measures. Later coursework used modelled business scenarios; operational improvements have not been demonstrated.
What I learned
The failed task exposed a gap between generating content and supporting a teacher's planning decisions.
I learned to listen more closely to the teacher's language and test whether the product reduced work. My next step would be independent testing with early career teachers to assess whether the revised flow produces usable plans with less effort.