Notion operating system
One structured system for how work comes in and gets done: automated deadlines from vendor lead times, reviews that respect vacation calendars, and capacity modeled in story points.
- Automatic
- order deadlines generated from vendor lead-time history
- Synced
- review deadlines checked against team vacation calendars
- Story points
- bandwidth modeled so throughput runs near its real ceiling
The problem
Incoming work arrived as a pile of emails and tickets with no reliable way to prioritize it, schedule it, or protect the team's capacity. Deadlines were set by hand. Reviews landed while people were away. Nobody could say how much the team could actually take on.
Two iterations
The first attempt was a move to ClickUp. It cost more than it returned. The second was a purpose-built Notion operating system, the layer for how work comes in and gets done.
It generates order deadlines automatically from vendor lead-time history, so nobody sets a date by hand. It syncs review deadlines to team members' vacation calendars, so nothing is assigned into someone's time off. And it models bandwidth in story points, so the team can run near its real capacity without anyone being overloaded.
Result
Reactive intake became a predictable, measured system, and a paid tool that did not justify its cost came off the books. The capacity model is the piece I would rebuild first anywhere else.
What it used
- Operations design
- Workflow and project-system architecture
- Capacity and resource planning
- Story-point bandwidth modeling
- Automation
- Notion
- Tech-stack rationalization