2 ms·
It really depends on who you are talking to and what their role is, right? If you are bouncing ideas off other workers who have other responsibilities and don’
by bee_rider 4y ago
It really depends on who you are talking to and what their role is, right?
If you are bouncing ideas off other workers who have other responsibilities and don’t really know much about your problem, I suspect they see it as more of a social conversation and don’t feel a responsibility to stay on topic, and will be happier pivoting to things they understand better or find more interesting.
On the other hand, if you are trying to have a deep technical conversation about something you and another expert are working together on, and they can’t stay on topic, there’s a possibility that they aren’t very good at their job. Although, communication is a two way street, and there are probably only a couple people working on your specific problem, so it seems like it would be hard to get a decent enough sample size to figure out which party’s communication skills aren’t up to the task.
Finally there is the case where you are trying to get information from someone who know the problem much better than you. For example, someone who has designed a library that you are trying to use, where they know the internals and you are just trying to figure out the API. In this case, they might decide that they simply can’t describe the API without telling you about internal details that feel, from your point of view, like an expansion of scope and a waste of time. In this case, they might be wrong, but unfortunately it is hard to tell due to the knowledge asymmetry, so there doesn’t seem to be anything to do but go along with them.
Generally a conversation is more productive if everybody knows what everybody else’s incentives and roles are (lots of conversations are just for fun and not intended to be productive, which is probably why we’re used to not really thinking about this before conversing).