6 ms·
I really hate this kind of language, but it is really useful in an American corporate context, as I have recently realized while doing an executive MBA program.
by pclmulqdq 4y ago
I really hate this kind of language, but it is really useful in an American corporate context, as I have recently realized while doing an executive MBA program. A lot of Americans tie up a lot of their emotions in work success. A lot of other Americans don't care about their co-workers, and don't want to put in the effort to figure out how to actually respect people (calling cheap places to work "discount" is a good example of this). Sometimes, the same person is in both groups.
The way to usefully make both groups work with others is to use language that is devoid of meaning and, in particular, lacking value judgments. That way, you can say "Steve, can you explain the learnings from your recent project?" and mean either, "Steve, you fucked up, what are you not going to do again?" or "Steve, your project went great, what tips can you share?" That way, Steve can feel recognized for his achievements even when Steve did something that was really stupid. Steve's colleagues have an emotional barrier, too: they won't feel bad for Steve if you are calling out his failures, and they won't feel bad for themselves if you are saying that Steve did something exceptional.
It's really fucked up how we have created this sanitized dictionary, but it's too effective in a corporate context not to use it.
- SamuelAdams 4y ago> A lot of Americans tie up a lot of their emotions in work success. For anyone else still wondering "why" corpspeak still exists, this is it. America has a very work-centric culture. Within a few minutes of meeting someone, people typically talk about their family or work. I guess I'm just disappointed at the world I've inherited. Why are people so afraid of direct conversation? Why is hearing bad news "too much" for some people? I remember a quote from a comic strip saying "people would rather hear an outright lie than an uncomfortable truth". Which is true, but I wish American work culture didn't need to hide from the truth. To me part of being a professional is being able to have direct, pragmatic conversations. You learn to keep your own emotions in check and focus on the discussion at hand. Look at the larger picture of the meeting / your work / whatever is being discussed. What would it take to change work culture to be more pragmatic?
- pclmulqdq 4y agoIn my personal opinion, if we just stopped doing this, and people at work experienced their first "breakup" (in the form of being told "you screwed up" or having to say "I am sorry that I screwed up") we would all be able to be more honest with each other. Just like dating, some people would go through an emotional trauma, but everyone would learn to get over it. Similarly, each manager would learn how to say "this project went poorly" or "you screwed up" in an empathetic way. However, that is just not the culture, and it takes a very long time to change a culture. To make matters worse, the presence of the linguistic emotional barriers makes their removal a lot more painful. The people fighting against this oppressive language would be labeled "mean" (or worse, "non-inclusive"), and unfortunately that is a much worse label than "bad programmer." I think this culture is dangerous, and normalizes both weasel-talk and lies. It has already infected media and politics. I just don't know how to stop it.
- tayo42 4y agothis is basically why i got fired recently. now, idk what to do from here. being so "fake" (idk a better one, using that word feels like angsty teenager) just isn't in me. corporate life isn't for me maybe, but those paychecks...
- bgribble 4y ago"You screwed up" is a tricky one. Yes, individuals do screw up. But that's actually not very interesting; a true individual screwup (with no one else contributing) has a very small blast radius. The bigger the screwup, the more people had a hand in it, and the less truthful it is to point to one person and say "you did it." Let's say I merge a syntactically incorrect piece of code that brings down the entire system on the next release. Nobody notices for a few hours and the company loses a bunch of money. Did I screw up? Yes I did, but that's the tiniest piece of it. * How did my change get merged? Who reviewed it? Did nobody test it or notice that it had no test coverage that would exercise my stupid change? Do we have any standards or accountability for review quality? * How did it get released? Do we not have any automated tooling to stand up a candidate release in staging and do smoke tests? * How did the downtime last so long? Do we have any operational monitoring? Was someone on call? Who is accountable for system uptime overall? A bad boss would just throw the person closest to the cause of the failure -- me -- under the bus. But who among us has never committed bad code? That's why we build systems for code review, for automated test, for release QA, for operational monitoring. And if all those systems fail or are inadequate, it's not really the fault of any single developer who was essentially walking a tightrope without a net.
- pards 4y ago> can you explain the learnings from your recent project? I've seen a lot of organisations publish "learnings" as an artifact of the retrospective on a project that went pear-shaped, but IMHO they can only be classified as learnings once the org has internalised the error(s), developed strategies to mitigate against them, and demonstrated an ability to avoid them. Until then, they're merely a set of recommendations (with a grammatically questionable name).
- KineticLensman 4y agoHence the distinction between lessons identified and lessons learned
- pclmulqdq 4y agoAnd hence a reason why "learnings" is so powerful: it doesn't make it clear that you have actually learned your lesson.
- debacle 4y ago
- hammock 4y ago>calling cheap places to work "discount" is a good example of this What kind of places do you mean- Can you give an example?
- jiayo 4y agoFrom the article: > To distinguish where employees receive high pay versus low pay, Company X organized the locations into three bins: discount, national, and premium. New York City, naturally, is a premium location. Detroit is a discount location. One of her friends works in Detroit, and something doesn’t sit right about her friend being a discount employee.
- mpalczewski 4y agoyou can be neutral without corp speak. "Steve, what did you learn from your recent project?"
- aaron695 4y ago
- 5350-uiop-1130 4y agoworking with americans, i found that they tend to use this kind of passive aggressive language but then in their actions they can be very cruel and sadistic...if they have power over you. i prefer someone who is direct and straightforward, just tell me to my face what you think as long as you're professional and i respect you, it wont be an issue.