Pages

Friday, October 25, 2013

How to Completely Derail a Problem Discussion

So, you're in a situation be it via email or conference call discussing some kind of problem which has arisen. The issue has been established, and people are working to get to the heart of the matter by attempting to sort out what needs to be done and who needs to do it. Somewhere, someone returns to the source of the original information in an attempt to figure out the intent or perhaps the mindset behind some level of advisement.

Then, out of no where, someone asks why, but it's a why something happened that can only be speculation and its answer has no bearing on the actual problem or its solution. It usually amounts to a bit of the blame game when it happens because someone asks why you asked so-n-so, or why someone did that thing they did. Where most questions to that point had flowed in a completely logical fashion, the right-field "why" kinks it all, and since no one wants to admit that they don't care, the conversation ends up completely derailed with guesswork and speculation.

When I'm looking to solve a problem, I keep it simple: what did you want it to do, or what sort of solution are you looking for? Never have I asked why they did it or why someone was bothered about it. Sometimes I wonder, but I know that it just comes off as accusatory and most of the time, it adds far more time to any discussion that I can spend doing something else.

The most recent eyeroller had to do with a discussion over how something worked, and really, it wasn't my specialty anyway. They had possibly misunderstood the original info and added the original people onto the email. The original person derailed the entire conversation by asking why the asker asked my group instead of, you know, just answering their question to him. Then the email string went off the deep end never returning to its original topic.

Seriously, there are questions with irrelevant answers. Some say there are no stupid questions, but I assure you there are. They are just trying to spark discussion when they say that. In fact, there are hosts of stupid, pointless and irrelevant questions that should never be asked in a group setting. If you are about to ask a question that will not, in any way, benefit the group, don't ask it. If you are asking a question that you are throwing out for the direct purpose of blaming someone else for something, don't ask it. If you feel like you have to lead the question with an apology, don't ask it. And finally, if you think your questions requires a disclaimer, either don't ask it or don't provide the disclaimer. Seriously, no one cares.

And finally, to clear up another fallacy: the customer is not always right. Ask anyone in technical support.

No comments: