3 ms·
Like many of you, I'm sure, I've been plagued by interruptions at work for years and years. For most of those years, I've ranted about how bad it is, and gone t
by dahart 11y ago
Like many of you, I'm sure, I've been plagued by interruptions at work for years and years. For most of those years, I've ranted about how bad it is, and gone to antisocial extremes like hanging office hours signs on the back of my chair closing the door and not answering knocks, hiding out in quiet places, and more. All of my tactics largely failed, people ignore my requests for quiet because "it's just a really quick question." It's always just a "quick" question, that is never satisfied with a quick answer.
But lately I'm turning around and feeling like interruptions are a sign that communication needs to be happening that isn't, and asking the question, "how can the things we're interrupting each other about be communicated on a schedule we expect and can batch, rather that being surprised by it in continuous small increments?" It might be a failure to manage properly, or it might be poor documentation (say it ain't so!) or it might be that interruptions are necessary and healthy and I've been swimming upstream instead of going with the flow.
It's not like anyone wants or needs more meetings, but a lot of important talk happens on nobody's schedule, and I'm realizing (especially as I get older and manage people & start my own company) that much of how a company runs depends heavily on impromptu communication, and that cutting it off might be wildly bad. But, this post and others are right about the cost of context switching, so clearly we need some balance.
I have no answers, other than I know the entire company has to be in on and agree to any interruption mitigation plan. I want some magical software that will arrange batches of impromptu meetings every hour or so, that everyone in the company would use willingly, just to keep the interruptions from being a constant stream.
- Retric 11y agoEmail can be a good middle ground as long as there are no popups. The important thing is much of this background communication works as long as people need to respond quickly as in <4h, but not right now. Generally where email falls down is back and forth communication, but giving people a little time to think about something before a discussion can save a lot of time. The trick is to also have regular add hock meetings without interrupting people. An informal schedule might look like 1h post scrum is communication time; 12-4 is work time where leave people alone unless you have absolutely nothing else you can work on. And then 4-5 is a last chance to bother people before people start heading home. PS: If you have a shared calendar it’s not a bad idea to block out ~12-4 so people look occupied on IM.
- simoncion 11y agoTo nitpick: It's "ad hoc". Otherwise, yeah, this sounds like a reasonably good workday schedule, actually.
- beachstartup 11y agohttps://news.ycombinator.com/item?id=10248601 https://news.ycombinator.com/item?id=10248601