Skip to main content

Everyone is in Sales!

Regardless of whether you are in sales as a profession; accounting; IT; etc. you are in sales. Are you aware of this? Of course, you probably aren't...until you discover that there is something you want.

Whether you are seeking a raise, a promotion, or (especially) a new job, you are thrust into a position of selling yourself and the value you bring to an organization. "Why should I give you a raise / the new responsibilities / a job?" they ask.

How do you answer? This age-old question is similar to the philosophy of how an effective resume is written, as told to me by Tom Espeland the former CIO of Viacom. Tom, who is a good friend of mine, once held a career seminar years ago for college youth and spent more than a few minutes describing the attributes of a good resume.

Of all of the things he said, the one thing that has stuck with me throughout the years is: state the impact you have had on an organization and you'll catch someone's eye. Don't just talk about your job responsibilities. Just as it is said that "faith without works is dead," you shouldn't expect anyone to take your works on faith. If you can't tell them, preferably in dollars and cents, what you've done to make an organization better then you probably need to rethink your approach before you ask for that meeting or interview.

So stop thinking about your responsibilities that await you tomorrow when you go into the office. Think instead of the impact you're having on the people and the organization around you.

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