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

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...