4 ms·

Completely fair. But it always goes both ways, it's usually never as clear (to me) that one side is at fault. For example, I've asked several times for clarifi

Completely fair. But it always goes both ways, it's usually never as clear (to me) that one side is at fault. For example, I've asked several times for clarification and got no response back. Now you're busy, and rightly so, you deliver far more than I do, but I considered those ignored contacts. Maybe you legitimately just missed them. Do I keep repeatedly asking? That's the right thing to do, but as a human, it's a hard thing to do. The reality is, there needs to be a communication channel back and forth, there is no hiding the details, but the channel needs to be there, and respond. If either side doesn't fulfill that minimum, there is going to be a lack of information.

iamdave 8y ago
Do I keep repeatedly asking? That's the right thing to do, but as a human, it's a hard thing to do. Blunt answer: yes. Absolutely.
azernik 8y ago
If you ask for clarification from a third party and get no response, first escalate through increasingly low-latency communications channels, from email to your workplace's chat system to maybe an in-person visit. If you still don't get a response after escalating as far as you feel comfortable - then that's what you need to report to your manager, so they can do their job and make sure you get the information you need.
- munk-a 8y ago
  Usually when uncertain about something I'll try and approach it from several angles and batch up a number of questions to send them off in one go so that the person on the other end can answer them more easily and possibly gain extra insight as to what's amiss. But there are some people who are distracted and so when sent a list of five questions one of which is hard, they'll omit the answer to the hardest question... So with them I just resend a response with different wording and just that question. I'm usually not asking these questions of developers and instead communicating with stakeholders but yea, question weaseling is a thing, sometimes accidental, sometimes intentional, but it's good to resolve your question to a definite answer (including "I don't know")
bigiain 8y ago
No no no! Try and avoid thinking in terms of "at fault". The primary goal is to get the work done. Mostly it never descends into blame storming and fingerpointing - so try and avoid behaving like it's got there before it does. You don't need to "keep repeatedly asking", but you do need to ensure you've communicated clearly. If you asked for clarification and didn't get a response, follow up at least once, and make sure you follow up when you decide you need to shelve the task until you get a response (possibly in that first follow up). "Hey $boss, I haven't heard back about the question I asked about $task on $date. I can't move forward without a response, so I'll put this task aside until that's resolved. If it's still urgent or critical, let me know, and let me know if I should continue chasing up that question with you or with someone else. Thanks, $communicative-co-worker." Your last sentence is key - communicate. Both ways. With the prime intention of getting things done, and clear language explaining when things are stalled at your end and what needs to happen to un-stall them. If you're doing all that - you'll make your co workers and bosses very happy, and you'll have all the paperwork you need if things _do_ end up in a blame storming session later on. But don't optimise for the blamestorming, optimise for getting things done and clear communication...
- hinkley 8y ago
  I would go farther. The primary goal is to make sure that work can be distributed. It's not a team if you're all being held hostage by one person. In that context there is no blame, there's just information: Work can't be distributed for reasons, reasons that should maybe worry us. One of the least likely reasons is "person X is stupid". Far more common is "person Y and Z have a serious case of the Curse of Knowledge".
  - myrloc 8y ago
    Yes, but for many people who do not know how to do X, there is the chance that looking into the problem on one's own will result in a solution that can be accomplished in a reasonable amount of time. It's just unknown to that person at the start. YET, if said person raises concerns immediately, there's also the potential for that work to get reassigned in a manner that never gives the said person to learn how to do X. I agree that this is a selfish action, and ideally we do not act in such ways when under pressure to perform and work as a team. But I've found that this psychology often explains why teams find themselves with facing a Canary MacGuffin.

iamdave 8y ago

Do I keep repeatedly asking? That's the right thing to do, but as a human, it's a hard thing to do. Blunt answer: yes. Absolutely.

azernik 8y ago

If you ask for clarification from a third party and get no response, first escalate through increasingly low-latency communications channels, from email to your workplace's chat system to maybe an in-person visit. If you still don't get a response after escalating as far as you feel comfortable - then that's what you need to report to your manager, so they can do their job and make sure you get the information you need.

munk-a 8y ago
Usually when uncertain about something I'll try and approach it from several angles and batch up a number of questions to send them off in one go so that the person on the other end can answer them more easily and possibly gain extra insight as to what's amiss. But there are some people who are distracted and so when sent a list of five questions one of which is hard, they'll omit the answer to the hardest question... So with them I just resend a response with different wording and just that question. I'm usually not asking these questions of developers and instead communicating with stakeholders but yea, question weaseling is a thing, sometimes accidental, sometimes intentional, but it's good to resolve your question to a definite answer (including "I don't know")

bigiain 8y ago

No no no! Try and avoid thinking in terms of "at fault". The primary goal is to get the work done. Mostly it never descends into blame storming and fingerpointing - so try and avoid behaving like it's got there before it does. You don't need to "keep repeatedly asking", but you do need to ensure you've communicated clearly. If you asked for clarification and didn't get a response, follow up at least once, and make sure you follow up when you decide you need to shelve the task until you get a response (possibly in that first follow up). "Hey $boss, I haven't heard back about the question I asked about $task on $date. I can't move forward without a response, so I'll put this task aside until that's resolved. If it's still urgent or critical, let me know, and let me know if I should continue chasing up that question with you or with someone else. Thanks, $communicative-co-worker." Your last sentence is key - communicate. Both ways. With the prime intention of getting things done, and clear language explaining when things are stalled at your end and what needs to happen to un-stall them. If you're doing all that - you'll make your co workers and bosses very happy, and you'll have all the paperwork you need if things _do_ end up in a blame storming session later on. But don't optimise for the blamestorming, optimise for getting things done and clear communication...

hinkley 8y ago
I would go farther. The primary goal is to make sure that work can be distributed. It's not a team if you're all being held hostage by one person. In that context there is no blame, there's just information: Work can't be distributed for reasons, reasons that should maybe worry us. One of the least likely reasons is "person X is stupid". Far more common is "person Y and Z have a serious case of the Curse of Knowledge".
- myrloc 8y ago
  Yes, but for many people who do not know how to do X, there is the chance that looking into the problem on one's own will result in a solution that can be accomplished in a reasonable amount of time. It's just unknown to that person at the start. YET, if said person raises concerns immediately, there's also the potential for that work to get reassigned in a manner that never gives the said person to learn how to do X. I agree that this is a selfish action, and ideally we do not act in such ways when under pressure to perform and work as a team. But I've found that this psychology often explains why teams find themselves with facing a Canary MacGuffin.