I can't really think of what #2 would look like (solve but not validate)
1. The desire to have a working computer, which was validated and solved
2. The desire to be connected to the process and the people they're working with, which was neither validated nor solved
Validating but not solving the second would include some sort of message saying that you know they'd rather a call but it helps you serve more tickets this way, or something to that regard.
Some would draw the conclusion that the person doing this is deliberately maintaining high dependence. That may be paranoid (The tech person may just be overworked and find social explanations harder than fixing computers) but some do draw that conclusion.
I guess it doesn't agree that it's something you should be feeling, just that you are feeling it.
Maybe its a definions thing, idk which of the two validation is supposed to refer to
In this context, it's the former. If I say, "It's dumb that you feel that way but here's you're stupid gloves," to a toddler, I solved their problem but I also likely made them feel like their problem is somehow not a "valid" one. Especially when this happens repeatedly to children is when they grow up with particularly anti-social behaviors, for fear of others abusing them similarly.
Comcast and Spirit both run their business on NOT solving problems.
It's the alternative option that most people don't realize is in the table. Validate, pretend to have solved, don't actually solve.
Which can be a mistake when the person you are dealing with has or may have an ulterior motive for your interaction (i.e. said "toddlers").
This is why in actual customer service, validating someone's feelings ("I understand you did not like the cook on the steak") is good, while validating their concerns ("I understand that the steak was undercooked") is bad.
You don't want to "find common ground" or "shared viewpoints" just to fulfill the validation matrix plot, because it may very well be based on a false premise, or even a blatant fabrication. In real world terms, validating concerns can often be an admission of liability or fault, or a soundbite that will be weaponized against you.
Well at least to some people, this makes it look like a sleazy attempt form customer service at deflecting blame from a fact ("the steak is undercooked") to a feeling from the customer ("you just don't like the steak, but I don't believe you when you say it's undercooked").
It immediately makes the person seem less human and more like a customer service robot. I'm pretty sure most people hate it, but maybe I'm wrong.
If you assume I can take a good look at you and just know you're the kind of guy who would never do that, you're assuming a level of sight-reading people that even most police investigators don't have. I'm sorry, I'm only human, and I'm waiting five tables simultaneously right now.
If the steak is blue and they ordered medium ... then there is little room for debate. If they wanted something other than what they ordered, then validating the feelings is more appropriate.
And that debate can be had (or not) by a lawyer or perhaps a manager, whose job it is to do so. No server is going to be vested with that authority, nor wants to be saddled with the uncompensated responsibility to.
Actually, if they came to vent about a problem that they don't view as solvable, then validation only is what they're looking for.
e.g. When your partner tells you about their difficult day at work, or your friend tells you about a bad date that they had, they're not usually asking for advice. They just want emotional support.
Spotting when this is the case is useful. Trying to solve it when validation and empathy is what's wanted can be the more annoying response.
https://medium.com/musings-with-meg/the-first-question-you-s...
* Validate emotions + solve the problem: Most people consider this excellent service, and some people consider it at least adequate. Very few people will complain about this.
* Do not validate + solve the problem: Some consider this excellent, most consider this adequate, some consider this a slight even though the problem is solved.
* Validate + not solve: Most people will be annoyed, but at least be civil about it because you've been civil to them. A few will lash out, but they were going to anyway.
* Not validate + not solve: Virtually nobody likes this.
The game theoretic optimal solution for a service provider is to always validate, and hopefully solve the problem as well.