Making Notion Sprints Work (When They Almost Didn't)
TD nearly abandoned Notion's sprint system because it wasn't working for their team. Here's how we turned it around and made it stick.
The Real Challenge:
Notion's native sprint features are solid, but they hit a wall when the team needed to kick tasks between sprints and keep everything connected to their OKRs.
The Winning Setup:
- Connected sprints to department task routing
- Linked every task to company OKRs
- Created a date span system for sprint windows
- Built automated QA subtask creation
The QA Magic:
When a task status changes to "Waiting for QA":
- System creates a QA subtask automatically
- Routes to QA team
- Maintains connection to original task
- Preserves sprint context
Quick Tip: "Don't try to force Notion's sprint system to be Jira. Instead, build the simplest version that keeps your team moving. We started with just sprint dates and status - everything else came later."
Next: See how we Migrated Existing Projects into this sprint system without losing data
