The Art of Collaboration: Developing a Shared Curriculum with Colleagues in Notion

The grade-level team held a curriculum meeting. Everyone made their own Google Doc and shared it, exchanged revisions over KakaoTalk, and received the final version by email. After the meeting, nobody knew where the "actual final version" was.

Teacher collaboration struggles not because of a lack of will — it is because there is no shared space for collaboration. Notion provides that space. This post explains how to design a Notion collaborative environment for co-developing curriculum with colleagues.

Table of Contents

1. The Structural Reasons School Collaboration Breaks Down
2. Designing a Team Collaboration Space in Notion
3. The Co-Curriculum Development Workflow
4. Establishing Async Collaboration Norms
5. Preserving Collaboration Outputs as Team Assets

The Structural Reasons School Collaboration Breaks Down

Scattered Information

Materials are spread across Google Drive, the school server, email, and messaging apps. It is unclear who has which version, and there is no revision history.

The Difficulty of Asynchronous Work

The time when all teachers can work simultaneously is extremely limited. The cycle of working separately between meetings and consolidating at the meeting repeats itself, and the in-between process disappears.

Unclear Roles

If the question "Who was supposed to write this?" comes up often, roles have not been explicitly assigned. Simply documenting roles in a shared space changes the sense of accountability.

Designing a Team Collaboration Space in Notion

Team Workspace Structure

Organize a grade-level or subject-team Notion workspace using this structure:

[Team Name] Collaboration Space
├── 📌 Announcements & Meeting Notes
├── 📚 Curriculum Development
│   ├── Annual Curriculum Plan
│   ├── Unit-Level Redesign
│   └── Performance Assessment Plan
├── 📦 Shared Lesson Materials
└── 💬 Ideas Board

Setting Access Permissions

Notion allows you to set different access permissions for each page.

• Whole team: Read + edit (curriculum, lesson materials)
• Specific person in charge: Edit rights (teacher responsible for that unit)
• External to school: No access (default)

Any page containing student information must be restricted to team members only.

Designing the Meeting Notes DB

Managing meeting content as a database makes it much easier to search and track later.

Properties:

• Meeting date
• Attendees (multi-select)
• Agenda (text)
• Decisions made (text)
• Follow-up tasks (relational link to task DB)
• Next meeting date

The Co-Curriculum Development Workflow

Step 1: Establishing the Annual Plan (Early March, Full Team)

Use a Notion table view to co-write a 12-month curriculum overview.

Clicking on any unit opens its detailed planning page.

Step 2: Unit-Level Redesign (Individual Teachers)

Each responsible teacher writes the detailed page for their assigned unit.

Required items for a unit planning page:

• Unit overview (3–5 sentences)
• Achievement standards (2022 revised curriculum)
• Session-by-session activity plan
• List of planned materials
• Assessment methods

Step 3: Peer Feedback (Full Team, Asynchronous)

Use Notion's comments feature to leave feedback on other teachers' unit plans. Meeting time is reduced while all teachers can still stay informed about the full curriculum.

Feedback norms:

• Write comments as "suggestions" ("What if we tried this instead?")
• The responsible teacher replies in the comments indicating whether the suggestion was incorporated
• This process becomes a documented record of how the curriculum was developed

Step 4: Final Confirmation and Sharing (Meeting)

After asynchronous feedback, a short synchronous meeting (30–45 minutes) handles final coordination. Because everything is already in Notion, meeting time is significantly reduced.

Establishing Async Collaboration Norms

Put Collaboration Norms in Writing

Verbally agreed norms are quickly forgotten. It is highly recommended to write out "Our Team's Collaboration Norms" as a document in the Notion announcements section.

Sample norms:

• All new materials must be uploaded to the relevant DB (no file sharing through messaging apps)
• Reply to feedback comments within 48 hours
• Record important decisions in the meeting notes
• Include the date in file names (e.g., 20260310_Grade1_Korean_UnitPlan)

Optimizing Notification Settings

If Notion notifications are too frequent, people start ignoring them. It helps for the whole team to align on notification settings.

Recommended settings:

• Comments where your name is mentioned: ON
• Updates to DB items you are responsible for: ON
• All workspace edits: OFF

Preserving Collaboration Outputs as Team Assets

End-of-Year Archiving

When a school year ends, duplicate the entire curriculum space for that year and save it to an archive folder. Teachers who take on the same grade the following year will not have to start from scratch.

Tagging Reusable Materials

Before archiving, team members review materials together and tag items as "reusable." Teachers in future years can filter by this tag and immediately put materials to use.

Preparing for Teacher Transitions

When team composition changes due to transfers, leave, or subject reassignments, the Notion collaboration space becomes a handover document. A space containing three years of curriculum development history is more powerful than any formal transition document.

Teaching well together serves students better than teaching well alone. And teaching well together requires a space where you can build well together. Notion provides that space and preserves the process as a record.

Related Posts

• Building a Project Overview Dashboard in Notion
• A Strategy for Archiving a Year of Lesson Materials as an Asset
• Building a Teacher-Specific Knowledge Base with Notion

What is the biggest challenge when collaborating with colleagues at school? Whether it is a tool problem, a time problem, or a culture problem — share your thoughts in the comments and it will help shape future posts!