<aside> 📌

Welcome to the Comma Operating System — a project management and collaboration environment built in Notion around a single, proven methodology: Getting Things Done (GTD).

This guide will get you up and running in under three minutes.

</aside>

Table of Contents

Why This System Exists

Most teams don't struggle because they lack tools. They struggle because information is scattered, priorities shift without visibility, and no one is speaking the same language. This system fixes that by giving your team one central place to track all work — from high-level strategy down to individual daily tasks — and a shared structure for managing it.

<aside> 💡

The goal is simple: every project has a clear owner, every owner has a list of next actions, and every week your team checks in to make sure the right things are being worked on.

</aside>

A quick note from Matt about how Comma use this project methodology.

A quick note from Matt about how Comma use this project methodology.

A Note on Habit Change

The most common reason teams abandon a system like this isn't the technology — it's the transition. You have existing tools, existing habits, and not everyone will switch at the same pace.

The recommendation is to not try to migrate everything at once. Start with new work. Use the system for your next project, your next meeting, your next client. Build the habit incrementally, and the old systems will naturally fall away.

If you're stuck for more than 15 minutes on anything, reach out.

The system should reduce friction, not create it.

The GTD Foundation

The system is built on three concepts. Learn these and everything else will make sense.

1. Projects are anything that requires more than one action to complete. Onboarding a new client is a project. Sending a welcome email is not — that's a next action. Writing project names in the completed tense (e.g. "Client X has been onboarded") helps keep the end goal in focus.
2. Next Actions are the single, specific steps that move a project forward. They are assigned to one person, linked to a project, and have a due date. Think of them as disposable sticky notes — once done, they get archived. Don't store permanent information in next actions; that belongs in a project page or a note.
3. Weekly Reviews are the heartbeat of the system. Once a week — individually and as a team — you scan your projects, check your next actions, and ask: is the right work happening? Without this habit, the system becomes noise.

<aside> ⚠️

This is the most important thing to understand: the system only works if your team commits to a weekly cadence of reviewing priorities. The tool is only as good as the habit behind it.

📕 Read more here

</aside>

How the System is Structured

Information flows through three layers: