The Real Cost of Context Switching
Developers spend 10+ hours per week in meetings and lose 23 minutes refocusing after each one. Here's the real cost of context switching.
Blog
Short, practical reads on building, shipping, and working together without unnecessary process.
Developers spend 10+ hours per week in meetings and lose 23 minutes refocusing after each one. Here's the real cost of context switching.
If you can't kill the standup yet, at least fix it. Here's a 7-minute standup format that cuts the ceremony tax.
Sprint planning, standup, grooming, retro, demo. For a 5-person team doing 2-week sprints, that's 15+ hours of ceremony per sprint. We calculated the real cost.
Status meetings exist because someone in leadership doesn't trust the tools. Here are 5 async patterns that give better visibility without stealing an hour from your team every week.
The average developer spends 10.9 hours per week in meetings. We did the math on what that costs in shipped code, focus time, and morale.
We spent two years testing every standup alternative we could find — async bots, walking standups, written check-ins, no standups at all. Here's what actually worked.
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.
Your daily standup became status theater the moment it stopped being useful. Here's why standups degrade and what replaces them.
You start the day with noise before real work even begins. Here is why that happens and how to fix it.