3 ms·
Just parroting what someone says... that's super annoying, but there is some use to something like it. I do a lot of: "Here is the problem as I understand it,
by duxup 7y ago
Just parroting what someone says... that's super annoying, but there is some use to something like it.
I do a lot of:
"Here is the problem as I understand it, X -> Y -> Z, when A, B, C.
Let me know if I got that right."
Then I go on into what I saw when I tried it.
What repeating SHOULD be is confirming that we're all on the same page (often with new details and specifics). What it often is ... is just repeating.
Sadly I found folks so generally frustrated by support that a large % of time they would be upset even when you were trying to understand. Some folks are so sensitive to repeating things back that they miss when I include new information / questions.
Support sucks, customers are frustrated so they don't really participate and hurt themselves ... companies devalue support, good management avoids / leaves support, and the whole thing stinks. I chose to leave that general business unit / area despite being well paid because of such things. I actually had engineering folks at my previous job reach out to me to encourage me to apply and return because we worked together well, I enjoyed working with them, but there was no getting around that I would be on the support team and I didn't want that.
- QuercusMax 7y agoYup, all too often support cases may have an X/Y Problem (see http://xyproblem.info/ http://xyproblem.info/). It's really import to clarify: 1. What they're trying to accomplish 2. The steps they're taking 3. The expected result 4. The actual result A misunderstanding of any of those points can waste huge amounts of time and cause lots of frustration.
- duxup 7y agoYeah if you can come up with a good definition of a problem, you can save serious time / $. If you don't ... hold on man it's gonna be a wild ride because really you're just guessing.
- dmd 7y agohttp://3e.org/xy.png http://3e.org/xy.png
- roel_v 7y agoWell I've gotten allergic to the term 'XY problem' itself. All too often it's tossed around by people who think they know my problem better than I do, and then dismiss me by saying 'don't do that' or 'just do something else' (this is mostly in the context of 'community support' like Stack Overflow). It happens mostly when I distill a problem down into its most basic, abstract form, because otherwise it's too difficult to explain (I mean I can't fault people for not wanting to take 30 minutes to understand all design nuances and trade offs that were made over the last 10 years in my particular case). Then they take that abstract example as the real use case and find reasons to not answer the actual question. Then again, I'm probably in the 'cynical' category mentioned up-thread.