Skip to main content

Say what?!?

"Not intended for use as a life saving device" was what the packaging for my infant's outdoor, blow-up pool read. "What?" was my response. After all, who in the world would mistake a blow up pool for a life saving device?

The problem above is not uncommon in the world of business either. One of the best public presenters that I've ever seen, David Barnes, did not earn that accolade because of his enthusiasm. (And he is a very enthusiastic public speaker.) Instead, in spite of the energy level that he had that could power Manhattan for a week, his message was clear as a newly produced pane of glass.

Does this come naturally? There is a common expression that says (paraphrased): "amateurs practice until they get it right, while professionals practice until they cannot get it wrong." While this adage is probably more applicable to situations where you are being questioned (e.g. product demonstrations, job interviews, etc.) the sentiment that you can never practice enough should not go unnoticed.

Occasionally, important situations like meetings spring up unannounced. But even when unannounced they are rarely about topics whose importance is unbeknownst to you. Are you always at DEFCON 1 with regards to these topics? Could you, on a moment's notice, answer even the most pointed questions about their details? Do you take the time to rehearse and rehash possible discussions and how you would frame your responses?

Although my neighbors probably think I'm a mad scientist, whenever I'm out walking my infant around in the stroller, I can always be found talking to myself. I haven't lost my marbles; instead, I have picked my topic du jour and am debating myself on the pro's and con's of it. And while this doesn't guarantee me success should this ever become the topic of discussion, I am already a step ahead in my preparedness.

Being viewed as an intelligent speaker with "all the answers" doesn't have to be an impossible task. But the rewards of leaving such an impression upon others are unmistakeable: people will look to you as the person to go to, thus increasing your worth to the organization. And in these economic times, one can never be worth too much.

Popular posts from this blog

"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 attemp

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 that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ