3 ms·
I can definitely appreciate how distracting it is to get nagged on slack. unless it's a manager, I will usually take at least 20-30 minutes to respond. this ten
by leetcrew 7y ago
I can definitely appreciate how distracting it is to get nagged on slack. unless it's a manager, I will usually take at least 20-30 minutes to respond. this tends to cut down on a lot of the lazy questions. people figure out that if it only takes twenty minutes to solve their problem, they may as well just do it instead of waiting the same amount of time for a response.
most questions I get are genuine coordination problems that need to be resolved. "hey, I see you have x file checked out. I also need to make some changes. should I wait for you to submit or will it merge cleanly?" answering this kind of stuff promptly saves everyone a lot of headache in the long run.
there are also questions about code that you are much more familiar with than the other person. it might cost you an hour to get back into "deep work" mode, but you save that person a day or more of floundering around and possibly messing things up (that you will have to fix later).
I'm not making any assumptions about you personally, but I find that many people who complain a lot about distractions really just don't like working with other people. this is fine, but it means you should probably be in a role where other people depend less on your knowledge and/or using your interfaces.
- gowld 7y agoThis reads like undermining coworkers while cuddling up to management. Why do you peers not deserve immediate replies but manager does? Why should someone spend 20 minutes researching something if you can point them in the right direction faster?
- leetcrew 7y agoI estimate twenty minutes as the average cost of answering a question. I'm only obligated to help co-workers if it costs me less time than it saves them. if a manager in your tree asks you a dumb question, they are squandering their own resources. I'm not obligated to stop them. to be clear, I only use the twenty minute rule deliberately on people who consistently ask low effort questions. usually I just finish whatever subtask I'm working on, then think of a response. fortunately I don't have many people like this where I work, but they do exist.
- briandear 7y ago> I'm only obligated to help co-workers if it costs me less time than it saves them. if a manager in your tree asks you a dumb question, they are squandering their own resources. I'm not obligated to stop them. Wow such a team player! You must be a joy to work with. Helping your team is an “obligation” but only if a certain math equation is a positive number.. When my manager asks a question, I don’t treat it with hostility. It isn’t a “dumb” question, because for some reason that’s what he needed to know. I could bet that you have asked a few dumb questions in your day. And with other teammates, why the contempt? You are a team. It isn’t all about “your productivity,” it’s about the team accomplishing the goal. You probably aren’t a Nobel winning physicist sitting around dreaming up theories that change the earth, but it certainly seems like it. Be helpful and compassionate with your team. If you really can’t be bothered, activate Do Not Disturb. If you actually think your boss is asking dumb questions, perhaps you should ask them why. Or perhaps you should ask to be the boss. Or perhaps you should just be helpful and friendly and not such an entitled grump. Or perhaps get better at your job so interruptions aren’t so horrible for you. Perhaps your hatred of interruption is due to insecurity or anxiety about your abilities. If that’s the case, work on boosting your capabilities. But don’t treat your teammates like some kind of fungus that need avoidance.
- leetcrew 7y agothe original post contained a small disclaimer that annoying, low effort questions do exist (with a strategy for dealing with them), followed by several examples of questions that are important to answer promptly. I even said most of the questions my coworkers ask are in this category, and I mentioned it again in the followup response. the main thrust of the post is to get people to consider how allowing themselves to be distracted by high-quality questions is worth the hit to their individual productivity. I really don't see how you can read all this negativity into my posts without totally ignoring the overall context. I will double down on my point that you don't have to prioritize questions that cost more time than they save. if I spend more time helping you than it would have taken you to figure it out yourself, this hurts the overall productivity of the team.
- hinkley 7y ago
- isoskeles 7y agoWhy stop there? I can finish nearly all of their work faster, maybe I should do that too.