Five mornings, five layers. A new cohort started with one question, who are you as a teacher, and left with a classroom that runs in their own voice whether they are in the room or not. This is what the week covered.
An operating system is the invisible layer that decides how everything else runs. Most teachers inherit theirs by accident, built from old habits, district mandates, and whatever survived the last in-service. The ClassroomOS Bootcamp is five working mornings to rebuild it on purpose, layer by layer: your Source Code, what you actually believe about how people learn, your Architecture, the visible structures that carry it, your Scheduler, the year as a designed arc instead of a pacing guide, and the live Applications that run on top. There is plenty of theory, but it is always interleaved with the practice that makes it land, never a binder to shelve. Each day stands on its own, and the days build on each other, so you can come for one morning or for all five.
Each morning built one layer of the system on top of the last, starting with the person and ending with something that runs without them. Here is the arc the cohort worked through, day by day.
Volume 2 has wrapped, but the work keeps going. Get on the list for the next cohort and early access to Curator (opens in new tab), the platform that operationalizes Classroom OS, or catch the free Google Classroom webinar series on demand.
The week starts with you. Name what you actually believe about how people learn, and draft the Source Code your classroom runs on.
If a stranger walked into your classroom while you were absent, what would tell them who you are as a teacher?
See the gap between the teacher you intend to be and the room you actually run, and start building the architecture that carries your values without your voice.
If you did not remind them, would your students know what to do?
Design your whole year as a journey instead of a pacing guide, and start training your Unit Gemini Notebooks (formerly NotebookLM) on your content and your voice.
Do your students know where they are in the year and where they are going?
A build day. Stand up a live Google Gem trained on your content, and a sub plan that runs your room without you in it.
If you got a call tonight that you could not come in tomorrow, would you feel ready?
Put your ClassroomOS in front of other crews in the Gallery Walk, and leave with an OS Overview anyone can pick up and run.
You already know the answer.
Want the next cohort to build their ClassroomOS at your school, or to take the week yourself? Email us and we will set it up.
At the end of each day, the crew stepped back to reflect on what the room built and what it surfaced. Here are the recaps, day by day.
Day 2 · Analysis
Day 3 · Daydreaming
Day 4 · Prototyping
Day 5 · Testing
The Day 1 reflection is not up yet. Everything else from the week is here, and the whole catalog lives on The Catalog.
Bringing a team, or want the Bootcamp for your whole staff? We are happy to talk it through. Group and district inquiries welcome.
Email Us Directly