|
|
|
|
|
by bitexploder
2291 days ago
|
|
This destroys deep work. If you are paid for deep work you have to balance responsiveness with getting your work done. Don’t be unavailable, use status messages wisely, and set up an SLA that makes sense for deep work. “Seconds” is not reasonable IMO. Depends on your role, I suppose. |
|
yes, but not everybody has to do deep work all the time.
for example, part of my job is to be available to colleagues for consultation. it might be something to which i can quickly respond "ticket or gtfo" or "busy right now, could you ask me again in 10-15 minutes?". But it could also require me immediate action (some production environment is failing).
As a company culture it is important to empower people to tell "not now", to educate people to only tell "not now" if you actually can't right now, and to train yourself to write "not now" without losing focus.