PDOS

The vision

PDOS — the Product Development Operating System — is a Notion-native operating system for the operations manager of a small team. Projects, role-by-role workstreams, launch cadence, and the contacts rolodex all live in one workspace, with a structured task database underneath as the system of record.

The core insight: the ops manager of a 5–20 person org doesn't need yet another dashboard to check — they need one place that already holds the week. PDOS is that place: a single workspace that coordinates engineers, designers, and stakeholders against a weekly delivery cadence, with the operator as the contact-of-record across vendors, partners, and team.

How it works

• Notion as the source of truth — projects, people, tasks, and assignments live in a structured database any team member can read directly.
• Role pages as modular slots — every role page is the same skeleton (a workstream board plus a per-release checklist), and every dashboard is just a view of the same underlying task DB.
• Launch cadence — a launch checklist and shared calendar drive the weekly delivery rhythm.
• Optional Bridge layer — Notion ↔ messaging, so you can run your week from WhatsApp, Slack, or Telegram instead of opening the workspace.

Forks and adaptations

PDOS is built to be forked. The skeleton stays the same; you rename the slots to fit your team — Backend / Frontend / AI is the v1 default, but the same shape holds for Producers / Designers / Engineers, or Sales / Ops / Customer Success.

spoonbot — the Spoonerism music-label fork — was the first downstream adaptation of the Bridge layer, narrowed to WhatsApp because that's where the label coordinates. Healthcare-CRO and clinical-trial coordination forks are next on the roadmap.