Skip to content
← Back to Journal

Studio notes

Why ClassStrand Exists

The frustration behind ClassStrand, and the decision to bring planning, assessment and reflection into one place.

Published Updated 1 min read

Why ClassStrand Exists

A familiar problem in classrooms: the tools meant to support teachers’ work are scattered across separate systems that never quite talk to each other.

Starting from the classroom

Before any code, the starting point was how a week of lessons actually gets planned.

The pattern was familiar — plan in one place, assess in another, reflect nowhere in particular, and report everything manually at the end of term.

Choosing simplicity

The easy route would have been something exhaustive from day one. Instead, the aim was a principle that now shapes everything the studio builds: clarity over complexity.

That meant building a smaller, clearer version of ClassStrand first, and letting classroom use shape what comes next.

What happened next

That starting point became the foundation for the workflows ClassStrand is being built to support across planning, assessment and reflection. It is still in development.

Connected work