In my introduction to Creative Differences I said this:
I don’t like to go to into a business situation with a handbook of new vocabulary that my clients should diligently learn. I am much happier listening, finding out what they talk about today: the terms they use loosely (visualization, strategy) ; their formalities (code review, release) ; and the words absorbed from their community (data lake, governance) which may be more or less formally defined within or outwith the organization.
Several people have contacted me with questions about terms they use. Do I think they are overused? What could they say instead?
My impression is that people are well aware we speak in business clichés but we carry on because it is easier than trying to say something new and different.
I am interested in this. Are there terms you use, which you now are worn out, but you still use them because they are convenient?
Are there terms you would like to drop in favour of new expressions?
From a company I recently left, the word synergy is overused.
From an analytics perspective, business value has become a buzzword and marketing fodder - but something that a lot of people still struggle with. We use the term to help orient various conversations.
Synergy! I often hear it where collaboration would be a better term. But I think people are tempted by the sense of emergence. I am sure the rhyme with energy helps too!
Business value is a tough one, isn't it, because in a sense it is always true - we want to deliver more value to the business. I generally deal with that one by asking people what other kinds of value they could optimise for.
One thing I've done in the past is just pipe up in meetings and say "I'm not familiar with that term, can you explain it?" And then usually a half dozen other people message me "Thank you! I didn't know either!" But outside of company- or industry-specific jargon, there are clichés I'd love to see vanish. Synergize. Alignment. Empowerment. Teamwork. They are meant to be positive concepts, but they've become negatives in my mind because they so often seem to be veiling honest risks and problems.
Piping up can be brave, but it can also be an eye-opener like the little boy shouting about the emperor's new clothes.
You make a really important point: when these clichéd terms serve to obscure issues rather than to clarify then they have not only lost their power, they now get in the way of better conversations.
Thank you for the thought-provoking questions, Donald!
When communicating with clients and potential clients in writing, I define terms inline. When presenting in-person, I try to read the room in search of people with questions. This is the biggest challenge when presenting remotely; I cannot read the room, but have to hope everyone with questions will either type them in a chat or interrupt. Some will not.
When I use new terms - especially terms I coin - I remind listeners that I am published and consider publication "a license to spell." ;{>
Mostly I name data integration (SSIS, ADF) design patterns. A "controller" is a pipeline (or package) that explicitly calls other pipelines. A "sniffer" checks for some prerequisite object, usually a file. If the file is ready, the sniffer pipeline starts a pipeline that loads data from the file. Regardless, the sniffer logs the status of the file.
Pattern names are a great example. A good pattern name can really help developers understand both the purpose and technique of the pattern. I used to have one called "The Meter Maid" because its only purpose was to check the status of objects and tag them if overdue for processing. Turned out that people used that pattern even when not strictly necessary, I think because it was memorable!
From a company I recently left, the word synergy is overused.
From an analytics perspective, business value has become a buzzword and marketing fodder - but something that a lot of people still struggle with. We use the term to help orient various conversations.
Synergy! I often hear it where collaboration would be a better term. But I think people are tempted by the sense of emergence. I am sure the rhyme with energy helps too!
Business value is a tough one, isn't it, because in a sense it is always true - we want to deliver more value to the business. I generally deal with that one by asking people what other kinds of value they could optimise for.
One thing I've done in the past is just pipe up in meetings and say "I'm not familiar with that term, can you explain it?" And then usually a half dozen other people message me "Thank you! I didn't know either!" But outside of company- or industry-specific jargon, there are clichés I'd love to see vanish. Synergize. Alignment. Empowerment. Teamwork. They are meant to be positive concepts, but they've become negatives in my mind because they so often seem to be veiling honest risks and problems.
Piping up can be brave, but it can also be an eye-opener like the little boy shouting about the emperor's new clothes.
You make a really important point: when these clichéd terms serve to obscure issues rather than to clarify then they have not only lost their power, they now get in the way of better conversations.
Thank you for the thought-provoking questions, Donald!
When communicating with clients and potential clients in writing, I define terms inline. When presenting in-person, I try to read the room in search of people with questions. This is the biggest challenge when presenting remotely; I cannot read the room, but have to hope everyone with questions will either type them in a chat or interrupt. Some will not.
When I use new terms - especially terms I coin - I remind listeners that I am published and consider publication "a license to spell." ;{>
Reading the virtual room is an art very few people have mastered. Certainly not me!
I am intrigued by the terms you coin yourself. Can you give an example?
Mostly I name data integration (SSIS, ADF) design patterns. A "controller" is a pipeline (or package) that explicitly calls other pipelines. A "sniffer" checks for some prerequisite object, usually a file. If the file is ready, the sniffer pipeline starts a pipeline that loads data from the file. Regardless, the sniffer logs the status of the file.
Pattern names are a great example. A good pattern name can really help developers understand both the purpose and technique of the pattern. I used to have one called "The Meter Maid" because its only purpose was to check the status of objects and tag them if overdue for processing. Turned out that people used that pattern even when not strictly necessary, I think because it was memorable!