The Slack + Notion + GitHub Issues stack is not a system
You duct-taped Slack, Notion, and GitHub Issues together and called it project management. It's not a system — it's three tools pretending to talk to each other.
Blog
Short, practical reads on building, shipping, and working together without unnecessary process.
You duct-taped Slack, Notion, and GitHub Issues together and called it project management. It's not a system — it's three tools pretending to talk to each other.
We killed our daily standup six months ago and haven't looked back. Here's exactly what we replaced it with and why the team ships faster without it.
Every year a new tool promises to be "Jira but simpler." The problem isn't Jira's complexity — it's the assumption that your team needs project management software at all.
Your backlog has 300 tickets and nobody believes in any of them. That's backlog rot — and it's quietly killing your team's ability to focus on what matters.
Tools should support decisions and delivery, not become the center of the work day.
Teams can handle hard work. What hurts motivation is effort that does not feel meaningful.
A 200-ticket backlog is not a plan — it's backlog rot. Here's what happens when teams confuse volume with progress.
Useful constraints force clear decisions about what matters now and what can wait.
When things feel messy, teams add rules. Most of the time that makes delivery slower.
Workflow helps record decisions, but conversation is still where real coordination happens.
Good coordination often comes from simple habits, not complex systems.
Breaking work into more process steps does not increase output. It usually adds friction.