5 responses to “Doublespeak and Placing Blame”

  1. Fluxor

    With customers, the doublespeak and hedging of each statement is like a game. “This may be the root cause, or it could be this other thing, but we need more testing to really be sure.” or “I think this is most likely the problem, but ….” And then you put all that doublespeak into a PowerPoint presentation. Fun!

  2. Cherish The Scientist

    Oh my. I can identify. We had some major problems with parts, and after extensively documenting the problem and correlating it to the same phenomenon described in the literature, we gave our vendor a 20 page report. (I think they’re not used to their customers having the kind of analysis equipment we have, so it shocked the heck out of them.) They still won’t accept responsibility for the problem, and when one of their people gets testy, he will start talking about the “*supposed* problem with xxx”. Unfortunately, the fact that they won’t admit it or do anything about it makes me really not want to work with them, but there are a couple people who keep insisting we should. I’m leaning toward using them as backup.

  3. Ben

    I’m sometimes asked on short notice with no additional resources to express a technical opinion on a subject that really needs thorough analysis to answer with any confidence. Vagueness and double-speak are pretty much the most honest responses in this situation.

  4. sophi

    I’m really not into double-speak, stalling and making things to look differently than they really are. When I am presented with this behavior it makes me see red.
    It is unavoidable that in this world of suing and litigation, you can’t admit to screwing up on paper simply because it’s too expensive. But it’s pretty lame that it has to be that way.

  5. Truth and Money: The Sale-Dependent Salary (by Sophi Kravitz) | Engineer Blogs

    […] have to say:¬†Frautech’s recent post about Double Speak resonated with […]