Hacker News new | ask | show | jobs
by michaelt 778 days ago
It depends on the nature of your work.

In some types of work, individuals are supposed to do their own time management, and carve out chunks of time for activities that require sustained concentration, and respond appropriately to occasional requests, which are a mixture of low- and high-urgency. For example, someone who needs to read complex academic papers, but occasionally might be interrupted for an urgent production incident. For them, time management is all about avoiding distractions - like synchronous conversations about trivial matters when they're supposed to be working.

Other areas of work have far less need for uninterrupted blocks of time. A manager doesn't just change tasks every hour, they often also respond to e-mails and chat messages during meetings. For them, time management is all about choosing between overlapping meetings, and managing the length of their queue of work by rejecting and delegating tasks. And of course talking to people is the core of their job.

For the former, sending a 'hi' message without the context needed for them to triage it into urgent or non-urgent means they're interrupted twice instead of once - which is pretty inconvenient.

For the latter, though? A dozen interruptions per hour is completely normal, what's the problem?

3 comments

There is absolutely zero overhead for the person messaging to simply add more context to their opening message regardless of the situation. They're going to have to give the context anyway. If it's an emergency, just say "Hello, there's a fire", if it's informal say "Hello, you heard about Eddy?".
If we stop treating asynchronous communications mechanisms (chat, email, etc.) as synchronous (voice/video calls, face-to-face), the urgency issue goes away for everyone.

Async comms should regularly (and, perhaps, by default) be muted to enhance focus. Let them collect and allow the person to manage their own time. "No hello" allows them to have the question ready for them to address when they process their incoming queues.

Synchronous comms should be used to get immediate attention on an urgent issue that needs to be addressed immediately, or be used for tight, rapid iteration in a discussion (e.g. rapid design discussions). Because it necessarily takes attention away from another task, the activation energy should be higher.

> For the latter, though? A dozen interruptions per hour is completely normal, what's the problem?

It's still needless overhead. Just because interruption 13 is proportionally less painful doesn't make it free.