What are some "favorites" from the HN crowd?
What are some "favorites" from the HN crowd?
A few years ago, it was 'at the end of the day', which my boss said 42 times in one 60 minute meeting. Yes, 42. I counted.
Annoying? Oh yea.
But what is wrong with reaching out? Seems like a different way of phrasing “make contact with”, except with a connotation of intending to help.
Btw, 'intending to help' I don't think is implied. Naturally you may 'reach out' to provide or offer assistance, but in a business context there should be a business driver for doing the actual contact thing, and then you can choose to specify the context or not.
I use language along these lines, often after talking about an issue, as a way of steering the conversation onto solutions. In my experience, it can be a useful phrase.
'Can you call Bob's surf shop and see if they carry Mr. Zog's Sex Wax?'
'Please find out if Bob's surf shop carries Mr. Zog's Sex Wax.'
A few of the terms in the header image on the article seem perfectly appropriate to me depending on context, but I'm probably thinking of them being used literally (reaching out as in contacting, incentivising as in more money paid, deep dive as in RCA) and have insufficient exposure to the BS versions to comment - so, I'll stop!
Eg if you ask someone to call bobs surf shop and they don’t answer they might stop there or call back later. If you ask them to reach out they might go down there and see them, set up a meeting, speak to a friend that works there, etc.
That's where you can use the more general and succinct term, "contact".
"can you reach out to Carol and see when that will be done" vs "can you ask Carol when that will be done?"
Ever since Walking Dead came out, "reach out" evokes thoughts of hordes of zombies grabbing for me.
there are manager bullshit and verbal tics like the one you mentioned. I tend(ed) to use "long story short..." to force myself to summarize, but when a colleague of mine started to use it over 3 times in a single sentence, I've since stopped using it.
-Kabuki Dance
-Coal Face
-KT (Knowledge Transfer)
-Across the Piece
-And my personal Rockstar: Like Putting Socks on an Octopus
Our HR group actually put together a wonderful "Leadership" website complete with a "Leadership Handbook" (Buzzword Dictionary). Of course, it's hidden on an obscure sub-site and is unsearchable. I've never met anyone else who's actually seen this site or handbook, but it's been fun for me!
To be fair though, it is straightforward to understand what it means. On the other hand, it took me a while to adjust to "throw under the bus", "rounding error" (a small amount of money), and "up to one's eyeballs".
"Putting socks on an octopus" helped me find a buzzword dictionary online: http://www.theofficelife.com/business-jargon-dictionary-P.ht...
- "Cross-functional"
- "Ping"
- "Green Field"
- "ROI" (this actually means something specific, but it's often mis-used to imply something like 'overall value')
- "MVP" (this actually means something but has now been co-opted to sound agile while meaning 'the thing we're willing to release to users and keep our pride')
- "A matrixed organization"
- "Get everyone on the same page"
- "Stakeholders"
... many others...
- Synergy: explained in my other post
- Stakeholders: anyone who holds any power over a decision, even if it isn't formal power
- Everyone on the same page: make sure that everyone has the right context and knows all the important facts to date
- ROI: how much bang you're getting for the buck
- Green Field: building from scratch, without using existing infrastructure (as building a factory on a Green Field), compare to brown field (using existing infrastructure)
- Cross functional: when you're working with engineers and lawyers, aka, people who will absolutely never understand each other
Sure, you could use long phrases to replace any of those, but what's the point?
Don't be confused, ask what it is :)
However having to ask indicates these phrases communicate poorly. (This obfuscation, as the article states, is intentional.) Instead of "green field", for example, call the project "brand new" or "from scratch". There's no need to concoct additional synonyms in a language that already has so many.
Further reading: - Orwell's "Politics and the English Language" - Musk's "Acronyms Seriously Suck"
No, they actually speed up communication. Sure, to someone outside that area of work, it might seem like poor communication, but that's valid for any profession.
> This obfuscation, as the article states, is intentional.
Might be in some cases, but dismissing all of it as obfuscation is naive.
> Instead of "green field", for example, call the project "brand new" or "from scratch".
No, doesn't have the same meaning. Both "brand new" or "from scratch" might also refer to the design.
Building a "brand new" datacenter "from scratch" doesn't have the same meaning as calling it "a green field project".
Every profession has its own language. Just because you don't understand, doesn't mean it is obfuscation, or inefficient.
This is a real problem, especially for customer facing teams that continue to speak their own language instead of the client's language, and it will destroy your relationships if you do it wrong.
The article is about this language being used to convey expertise when it does not exist (understanding of the language does not imply understanding of the subject you're supposed to know, but may make you sound smart in a meeting).
Obviously feel free to keep using the terms if they work for you, but do so while also knowing the impact of the words.
TL;DR: Words matter, sounds like you are of the same opinion :) As long as we use them purposefully and understand the trade-offs, all good.
The whole point of the article was that business created / re-purposed a number of these things to mean something specific to _business_ rather than using regular words. The parent poster asked for some favorite examples of this, so I provided them.
I am not saying that I think all these words are worthless in a corporate context, but if you trotted out some of this during a bar discussion you might get laughed at. All disciplines have their own languages, and to really know it you should speak it, but sometimes this is used to hilarious effect.
"Hey - quick ask: can I link up with you tomorrow at 6 to talk fantasy baseball?"
"Yeah, let me ping my stakeholders and make sure I can get a block for some real ideation, you know, deep work."
"Alright. I'll take an action to get it on your calendar, and will capture learnings / best practices in a deck and send via email so we can circle back with the rest of the league."
"Great, thanks."
Every single profession has its own language, and they all use it to keep outsiders out.
But apparently most people here in HN can't understand business lingo, so they just assume it is all bs.
Just look at the example you gave. I don't know about you, but I've never seen anyone use business lingo like that.
But I bet you could say the same bullshit using eng speak: "oh, hang on, I need to ping all the other peers, make sure they're up and running then run a distributed consensus algorithm to achieve sync and schedule the processes".
Pure bullshit.
If HR decides to lay you off, you're probably not a stakeholder.
But I agree that YMMV, and I see how it could also be used in the way you suggest.
The best example of Stakeholder is a director who a teammate presented a project to before taking it to the VP. The director said:
- I don't agree with this project, but it isn't my decision. But I'm a trusted advisor of the VP.
One of the best classes I ever had was called "Power and Politics in Organizations", and dealt with identifying, managing and using power in organizations. Power comes from many different sources (information, money, influence, friendship, knowledge, formal authority, etc.), and managing is one of the most important learnings when working in any organization with more than 2 people.
Sadly, most engineers overlook those skills and focus only on "hard" skills, which I personally find to be far easier than "soft" skills (which are hard as hell to master, IMHO).
KT - the expectation is that the recipient should be able to perform the conductor's responsibilities after the knowledge transfer.
Stakeholder - there is a very specific group of people (mostly VP and above) that fall into this category. They need to be "kept in the loop" (another bullshit word, I suppose) when major changes to features, resources or business strategy are made.
ROI - for us, this boils down to a number, either in dollars or an expected change in a KPI (another bullshit term?)
On the same page - when a meeting/mail thread is started with this intent, the idea is that multiple teams with different/conflicting priorities need to agree on something so that they won't later claim "why weren't we told about this?"
Going forward - it's better than saying "from now on", which feels like a finger-wag to me
Synergy - yup, it's mostly bullshit
It makes me wonder how much corporate bullshit I hear is actually better communication.
"There's a world where..." replaces "Imagine if..." or "It's possible that...", and I think it's actually a neat way of presenting an idea -- if used very sparingly.
"Solve" and "ask", in this context, replace the words "solution" and "request". I'm not sure how people started abusing these words, but it's pervasive in my industry. I suspect it follows the recent trend of "nouning" verbs (a reverse-Calvin thing to do: https://i.imgur.com/l5AC4qG.jpg) like using "gift" as an action verb ("they gifted me a calendar"). I can understand that because there isn't an equivalent alternative word in English. We could just say "give", but it doesn't have the same meaning as "give as a gift". "Solve" and "ask" are nouns that already have suitable traditional words to use instead!
> pseudo english terms
isn't that just the english language? A mix of norse, french, latin, alotta patoise and irish and ... just sudo english
This inspired me: I'm am now renaming /bin/sudo to /bin/pseudo
Personally, I find the use of ‘architecting’ instead of ‘design’ to be particularly irritating.
I will leave that to others, but one thing I will say is that having been around the business world since the early 80's I can typically date someone just by hearing what expressions and bullshit they use. Anything that we didn't use in the 80's appears strange to hear. For example back then we didn't use 'circle back' (and now I can't even remember what we used for that I think it was simply 'I wanted to get back in touch with you'..) And yes I know circle back has been around for a long time (could even have been late 80's or early 90's).
People in this role are actually paid to walk around inside an organisation, finding things that aren't sufficiently 'agile' and coaching people on how to make them 'agile'. Concrete deliverables=none, ability to measure success=none, ability to achieve any actual tangible outcome whatsoever=none, ability to invoke apparently-meaningful-yet-utterly-irrelevant anecdotes=infinite.
'Experts' in this field are highly in demand, and held in fear &/or awe at many corporates.
For example, "reimagining customer service", as in, complementing 20yo kids hired for peanuts offshore with bloated and expensive contact centre software.
Kind of like going through TSA "nobody make any jokes I don't want to have to spend hours here explaining this."