Sharing and Collaborating

Everything in TeacherOS so far has been personal. Your vault. Your context document. Your reflections. Your skills. That's by design — a personal system has to work for you before it can work for anyone else.

But teaching isn't a solo practice. Departments share curriculum. Grade-level teams coordinate pacing. Instructional coaches distribute frameworks. And the best teaching ideas travel from one classroom to another through informal sharing — a template someone built, a strategy someone described in the break room, a rubric that actually worked.

This article is about extending the personal system into shared space. Not replacing your private vault with a shared one — adding a collaboration layer on top of what you've already built.

The Knowledge Sharing Paradox

There's a counterintuitive truth about sharing teaching knowledge: it makes your own knowledge stronger. When you formalize a template enough to share it with a colleague, you clarify your own thinking. When you explain why your unit retrospective template has those specific prompts, you understand your reflective practice more deeply. When you contribute a skill to the SmartChalk marketplace, you've codified expertise that was previously just intuition.

This isn't altruism dressed up as self-interest. It's how knowledge systems actually work. Writing for an audience — even an audience of one colleague — forces a different kind of rigor than writing for yourself. Your messy daily captures are fine for personal use. A shared template needs to be clear, structured, and generalizable. That generalization process is itself a form of professional growth.

Three Levels of Sharing

Level 1: Share a Template

The simplest form of collaboration. You've built templates that work — lesson plans, weekly reflections, unit retrospectives. Share one with a colleague.

Obsidian users: Export a template as a markdown file and send it directly. If your department uses a shared vault, add templates to a shared Templates/ folder. Obsidian's Publish feature can make select notes available to colleagues via a private link.

Notion users: Share a page as a template that colleagues can duplicate into their own workspace. Notion's native sharing makes this straightforward — click Share, toggle "Allow Duplicate," and send the link.

Google Drive users: Share the template file or folder with your team. Use "Make a copy" instructions so each person gets their own editable version rather than modifying the original.

What to share first: the Weekly Reflection template. It's universally useful, it doesn't require any specific subject knowledge, and it's short enough that a colleague can start using it immediately.

Level 2: Build a Shared Resource Folder

A department of four social studies teachers sits down at the start of the year. They each have their own vaults, their own systems, their own Teaching Context documents. But they teach the same curriculum.

One teacher sets up a shared Resources folder — a central location for materials everyone can access. Each teacher contributes:

• Unit plans that worked (with retrospective notes attached)
• Assessment rubrics that have been refined over multiple semesters
• Primary source collections organized by unit
• Differentiation strategies that work for their student population

The shared folder doesn't replace anyone's personal system. It supplements it. When planning a unit, each teacher checks the shared folder first: "Has anyone taught this unit before? What did they learn?"

Over a year, the shared folder accumulates institutional knowledge that survives teacher turnover. When a new teacher joins the department, they inherit two years of refined resources instead of starting from scratch.

Level 3: Contribute Skills to SmartChalk

This is the widest circle of sharing. You've built a skill that works for your teaching context. Other teachers in your subject area or grade band would find it useful. Submit it to SmartChalk's marketplace.

The submission process asks for:

• The skill itself (in SmartChalk format)
• A description and usage guide
• The category, grade levels, and subjects it covers
• A sample of the output it produces

After review, the skill appears in the SmartChalk directory. Other teachers can discover it, copy it, use it, and leave reviews. Your name appears as the creator. Your expertise reaches classrooms you'll never visit.

Some teachers worry about giving away their best ideas. But skills aren't lesson plans — they're meta-tools. Sharing a skill that generates discussion questions doesn't give away your discussion questions. It gives other teachers a tool to generate their own. Your expertise is in the structure and quality standards you built into the skill, not in any single output.

Starting a Collaborative Practice

If the idea of department-level knowledge sharing feels ambitious, start smaller:

Week 1: Share one template with one colleague. Ask them to try it and tell you what they'd change. Their feedback will improve the template for both of you.

Week 2: Set up a shared folder (or channel, or workspace) with your closest teaching partner. Add one resource each. See if the habit sticks.

Month 2: Bring it to a department meeting. Show the shared folder. Invite contributions. Don't mandate — model. The teachers who find it useful will contribute. The ones who don't will come around when they see the accumulated value.

End of semester: Review what's in the shared space. What's been used? What's sitting untouched? Let the data guide what you share next.

What Not to Share

Not everything belongs in shared space. Your daily captures are personal. Your Teaching Context document is yours. Your weekly reflections contain observations that are candid precisely because they're private.

Share the refined outputs: templates, retrospectives (with student names removed), strategies that worked. Keep the raw material private. This boundary is what makes the personal system sustainable — you can be honest in your own notes because no one else reads them.

Your one action this week: Share one template or resource note with a colleague this week. Pick something you've already refined through use — not something untested.