Quiet hours: defending deep work

Two years ago I was a senior engineer who couldn't finish a function without being interrupted. Slack, meetings, 'quick questions' — my calendar looked like Swiss cheese and my output was about what you'd expect from cheese. Then I made one change: I blocked 8am-12pm as 'Quiet Hours' on my calendar, every day, and I told my team I wouldn't respond to anything unless the site was down.

The first week was uncomfortable. People were used to reaching me instantly. I got pushback. I held the line. By week two, people had adjusted — they scheduled meetings in the afternoon, sent Slack messages they knew I'd see at lunch, and the 'quick questions' turned into Slack threads that often resolved themselves before I even saw them.

Here's what I learned: most interruptions aren't urgent. The sender feels urgent in the moment, but if you wait 4 hours to respond, 80% of the questions either answer themselves or turn out not to matter. By being reachable instantly, I was training everyone around me that I was always reachable. By being reachable on a schedule, I trained them to be more thoughtful about what they actually needed from me.

The output change was dramatic. In quiet hours I could hold an entire subsystem in my head for 4 hours straight. I shipped more in those 4 hours than I used to ship in 3 days of interrupted work. The afternoon was for meetings, code reviews, and Slack — work that benefits from context switching. The morning was for building. The combination roughly doubled my weekly output.

If you try this, expect resistance. Not from your manager (mine was thrilled) but from colleagues who've come to depend on your instant availability. Hold the line for two weeks. After that, the new normal sets in, and you'll never go back. The single best engineering decision I made in the last five years wasn't a tech choice — it was a calendar choice.