Built with the
people
who use it.
Every product in the roster began as a problem someone brought to us: a university, a TAFE, a not-for-profit, a public service. We build alongside them rather than for them, and the partnership continues well past launch.
Who we work with.
Partners are described by sector rather than name. Several work in sensitive settings, and naming them is theirs to do, not ours.
University partner
Branching scenarios built from real classroom incidents, embedded in a pre-service teaching unit.
TAFE partner
A custom story library for community services students, authored in-house after training.
Advocacy partner
Coverage and gap analysis across a national dataset, built to support a regulatory submission.
University partner
A coding workflow used to teach thematic analysis, with reliability statistics built into the assessment.
Partnership means the practitioners are in the room when the thing gets designed, not just when it gets demonstrated.
What a partnership looks like.
Three stages, usually across eighteen months to three years. We take on two new partnerships a year.
Sit in the practice
We spend time where the work happens before we propose anything. Classrooms, clinics, offices, field sites. The brief comes out of what we observe together.
Build in the open
Short cycles with the practitioners using it. Nothing ships to a cohort until the people who will teach or run it have shaped how it behaves.
Hand over the keys
The goal is that partners can author, adapt and maintain their own content. We stay for support, not for dependency.