Skip to main content

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message. Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle.

(For the curious, the title says "Do you speak the same language?" in pinyin, which is a transliterated Mandarin Chinese.)

Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice.

I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket.

"A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attempt the ball went right in the pocket.

So what went wrong?

The problem is in my use of the word medium to describe the desired speed of the cue ball. Such subjective words have, by definition, a wide range of meanings depending on how the listener (or reader) wishes to interpret them. Problems down the road can be avoided by using words with precise definitions, and standards like ITIL attempt to clear the confusion by strictly defining IT process concepts such as incident, problem, known error, etc. You don't need to wait until ITIL can be used, though, since the idea of precision in communication has applicability everywhere.

For example, can you imagine the following scenario?

CIO: so why should we buy your product?
You: because it does a lot of great stuff.

"Great?" "Stuff?" Vagaries such as these are a recipe for disaster, and it is for this reason that presenting a business case is essential in sales: they describe, in quantifiable terms, the exact benefit (typically in dollars / euros / pick your favorite currency) that a business will receive.

How about this situation?

Interviewer: so why should I hire you?
You: because I've can do amazing things for your organization.

Is this any better? Of course not. The response deserves some credit for attempting (in spirit) to sell the value of the person, but it falls flat on its face for not being specific at all. (Note to self: tell this to my wife who writes out the vaguest grocery lists and then yells at me for not buying the right brand names.)

Being able to recognize the possibility for gross misinterpretation takes practice. You could say "red ball" and people may point at different shades of red as their definition. This isn't a disaster (in my opinion) even though your red and their red will likely differ by some amount. At least you can have some degree of confidence that they would not select orange.

When you are answering questions or presenting your side of an argument, choosing your words with surgical precision has irrefutable benefits. Maybe you are hoping to close a large sales deal; receive a better job or promotion; or just give directions (to your house for a fête; to install a newly purchased software application; etc.). Your chances of success increase exponentially when care is taken in choosing the words you use.

Popular posts from this blog

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While t...

COSMIC Insights

Consider the following scenario:  you're a mid-level manager and find out that a layoff is coming.  You're about too lose one of your best direct reports, but you have no ability to influence the decision to lay them off. Oy! My head hurts! What do you do? Oftentimes, I find that people - when presented with situations where they feel compelled to act but have no ability to change the outcome - enter a state of mental lethargy.  They don't know exactly what it is they should do but, "gosh darnit!", something has  to be done.  When they realize how helpless they actually are, they start lamenting about the situation, how they are backed into a corner, etc. In a very real sense, they go through the five stages of grief . I'd like to offer the following alternative way of approaching these and other situations:  I call it the COSMIC method, not only because it sounds cool but also because I like science fiction (" Lisan al Gaib! "). COSMIC is an acronym...