Seek first to understand
Whilst mooching through social media this weekend I came across a fascinating thread. Someone within my network had posted a rather generic request for help on a pretty generic topic. It was one of those moments that we’ve all had where we ask, “does anyone know anyone who can xxx”.
What fascinated me was that despite the very generic nature, the thread was filled with responses, “I can” or “I recommend x”. It was only after about forty or so responses that someone answered, “I think I might be able to help, but I need a little bit more detail. What specifically are you looking for, who are the people you’re looking for this for and where and when would you need it?”
It reminded me of many of the conversations that we have at work. A problem is generically stated and immediately we all pile in with attempts to fix it. Suggestion after suggestion is made in the attempt to solve a problem that we haven’t even fully understood. From the limited data that’s presented we all form our own individual interpretation and yet we rarely take time to check that our understanding is the same.
The impact on the original requestor can be overwhelming as they are inundated with solutions that can often be contradictory to one another meanwhile the other participants can get frustrated as their “obvious” answer to the problem goes unheard. But what if instead of being at the end of the thread, those questions had been at the beginning? Would that have led to a better quality of response?
It would be easy to say that the originator of the question should have thought it through, but I disagree. The nature of collaboration is that we work together to try to find a solution and that is particularly true in the workplace. If we all take responsibility to ask questions and seek to understand all the aspects of a problem, rather than making assumptions, we not only help to achieve better answers, we save everyone time and effort in the process.