Start with the human
The day opened with a conversation and a question only a person can answer — who are you, what do you believe, what does this room actually need? No screen until the thinking was real.
Four crews of teachers. Five mornings. It started with one question — who are you as a teacher? — and ended with a classroom that runs in their own voice, whether they're in the room or not.
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. Classroom OS was five working days 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 — AI Gems, sub plans, OS Overview — that run on top. Plenty of theory — cognitive load, accessibility, how different learners actually learn — but always interleaved with the practice that made it land, never a binder to shelve. By Friday, four crews of teachers had built something that works whether they're in the room or not.
What if the machine wasn't the enemy? What if it was a mirror?
We don't think the machine is the enemy — and we don't think it's the savior. Every day, for every task, we asked one question instead: what's the right tool for the job? Not no-tech. Not all-tech. So every morning ran the same rhythm — the one we want in their classrooms, too: start with the human, move to analog, reach for digital only when it earns its place.
The day opened with a conversation and a question only a person can answer — who are you, what do you believe, what does this room actually need? No screen until the thinking was real.
Before anything went digital, it got drawn, mapped, and talked through on paper. Slower on purpose — analog is where an idea gets clear enough to be worth building.
Then the laptops opened — and the tech did what only tech can: translate, adapt to a single learner, stretch one teacher's reach, and reflect their work back in their own voice.
Underneath all of it, one house rule: clear rather than clever. We taught the theory, too — cognitive load, accessibility, how different learners actually learn — but always after the practice that made it land.
A teacher asked his brand-new Classroom OS: “If I were a historical figure based on my OS, who would I be?” It answered: “Because of your focus on reflection and leadership, you'd be Marcus Aurelius.” The machine wasn't replacing him. It was reflecting him back.
Each morning built one layer of the system on top of the last — starting with the person, ending with something that runs without them.
We didn't open with tools. We opened by asking teachers to surface what they actually believe about how people learn — the real version, not the evaluation-rubric one. From there they drafted their Source Code, the foundation everything else runs on, and stood up their Course Brain — an AI trained on their classroom that would grow with them all week.
If a stranger walked into your classroom while you were absent, what would tell them who you are?
There's always a gap between the teacher you intend to be and the room you actually run. Teachers audited what was already there — procedures, layout, transitions — and translated their Source Code into visible architecture that holds without their voice carrying it. Then they made it audible: a short podcast walking a listener through what their classroom is actually like.
If you didn't remind them, would your students know what to do?
Most teachers are handed a pacing guide and sent back to their room. Instead, teachers brought the real shape of their year into one place, kept training their Course Brain on their content and their voice, made the pitch — a commercial on why a student would want to be in their classroom — and started building their first Google Gem.
Do your students know where they are in the year, and where they're going?
No more drafts, no more groundwork. Teachers learned to direct the AI with real intent, then brought their Google Gem to life — seated with their Classroom OS, trained on their content, calibrated to their students. And they built for the real classroom: something to hang on the wall, something to use the first week of school, and a sub plan that runs the room without them in it. This was the day the AI went live the way it was designed to.
If you got a call tonight that you couldn't come in tomorrow, would you feel ready?
The whole week pointed here. In “Slopped” — equal parts AI slop and Chopped — teachers had to defend their Gem against live curveballs: “You just got a student from Ecuador who only speaks Spanish. What do you do?” A real stress test of the system against the unpredictable reality of a classroom. It held. Then they learned to ship it — sharing their Gems and putting them to work in Google Classroom.
They already knew the answer.
You can describe a system all week. The teachers didn't believe it until they saw it produce — documents in their own voice, matched to their own classroom, almost effortlessly.
A sixteen-year veteran, she didn't see why she'd customize a generic AI — and that was a fair read. She knew her room, her students, and her standards better than any tool could. The ask was simple: teach the system who you are, and see if it stops being generic. By Friday she'd written, “I'm the human. I learned how to better communicate with AI to achieve the results I'm looking for.” She didn't arrive empty and leave full — she arrived an expert, and left with tools that finally had the range to match her: a whole classroom kit, built in her own voice.
“I don't really see the value in customizing the Gems.” A fair question — from someone who already knew her craft cold.
On Thursday we ran an A/B test. The same prompt — “Create a lesson plan template that meets the requirements for my district” — to plain Gemini, then to Gemini with their Course Brain. For the teachers who'd done the work, the difference was stark: the second answer came back in their voice, matched to their classroom. For the ones who'd left their Classroom OS docs empty, it didn't. The system doesn't invent you — it reflects back exactly what you put in.
AI is not my competition. It is the paper plane I can customize, maneuver and hop on to reach new heights.Ana · 2nd Grade Teacher
This training was extremely helpful to my professional development. Classroom OS is a great communication tool. I love how all my pertinent information is in one place and that I can use AI to ask a question that will help me plan effectively for enhancing my students’ learning experience. Google Gems is great for building personalized activities that I can share with students to make their learning more meaningful and engaging. I look forward to future trainings. Thank you.
Mike and Webs are like Batman and Robin, The Wonder Twins, Milli and Vanilli, etc. The Intelligent Hoodlums keeps you busy thinking, creating, and exploring. The information and resources are super helpful in making a teacher’s world worth it! Time flies when you’re having fun!
If you are an introvert like me, who shies away from PD sessions saturated with ice breakers and moments where you are put on the spot, this is the place for you to be. There is no fluff; Mike & Webs are professionals who get down to business and treat you as a professional. You will walk out of their session with a reservoir of tools & knowledge to not only guide your students towards success, but also drive you towards professional discovery & growth.
We don't ask you to take our word for it. Teachers rated their own classrooms on Monday and again on Friday — same questions, same people — so the shift is measured, not asserted.
Get the white paper for the method, the research behind it, and the Monday-to-Friday data, or bring Classroom OS to your team. Group and district inquiries welcome.
Get the White PaperPrefer to talk first? Email us directly — we read every one.