Why do IT professionals always blame eachother

vyle

thescouselander wrote: »

Yes, you could be right here. And that being the case it would probably be better (in the case of the Panasonic app at least) to declare the configuration in question is not supported rather than giving the customer the run around by blaming everyone else they can think of.

I think one big problem is people rarely consider the connotations of the words they use, especially on the phone.

For instance, when I am working in my tech support capacity, I get lots of people coming in without their devices saying that something isn't working right, and they want to know why, and I often have to tell them that without their device to hand, and without knowing exactly what it's being used with at the time of the fault, I cannot say. My other colleagues aren't as careful and will say that they think something is "faulty" which of course often causs customer service issues if the customer thinks they've been sold duff kit, and it turns out to be a software issue, or something unrelated.

Somebody who says "android is wrong" might really mean "it's an unsupported handset" but they simply worded it badly, but that can be fatal in a situation as precise as technical support needs to be.

prowla

As far as products go, there is also an overriding imperative to get them to market first, and all other considerations like performance (eg. the iPhone's battery handling), usability (eg. Windows 8), and quality in general typically get pushed to one side in the mad rush to meet target dates.

The only company that I recall who has recently postponed consumer product releases for quality considerations was Blackberry, and in the end they were forced to release the Playbook with missing features in order to try and get at least some market share.

Is guess there is not really any profit in quality anymore; I've seen it being sidelined in datacentre products too.