Skip to main content

I'm Looking for a New Job!...

...And you're reading this because you thought I was serious.

A number of months ago, an EVP and member of the Executive Management Team emailed me to say he wanted to spend a few minutes chatting with me.  He and I had met, face to face, for the first time the week prior and I left a positive impression on him that he wanted to explore further.  In the spirit of full transparency, I allowed this meeting to stay visible in my work calendar in spite of the risk of my management chain seeing it and misunderstanding.

So, of course, my manager did see it and did misunderstand.  He called me up a week after the appointment was made (but still before the actual date of the meeting) and seemed distraught that I didn't trust him enough to tell him if I were dissatisfied with my role.  This was the inspiration for a previous blog entry where I contrasted the concept of happiness versus contentedness in one's role.  Another part of my discussion with my boss, that I did not describe in that blog entry, revolved around the activity itself.

Humpty Dumpty? Who's that?
During that part of the discussion, I compared my meeting with the EVP to a sales pipeline.  Was I looking for a new job?  Not necessarily, I said.  But just as a sales professional builds a pipeline that is 4 times their quota because they know that 75% of those potential deals will fail, one cannot take a sequential approach to something as strategic as looking for the next step in their career.  Instead, you have to be willing to entertain all things even if you're not explicitly looking to change jobs at that particular moment.

Or, as the cliché goes:  "don't put all your eggs in one basket."

Expanding this to a more general discussion, devising an effective strategy for anything is part marketing, part sales, and part operations.

Marketing.  Development of an effective strategy requires effective communication of that strategy.  And that starts by understanding what, exactly, it is you're trying to achieve.  For example, when building a public relations campaign, one of the first things you do is answer the questions:  who needs to know, who needs to be involved, who will be effective, and what is the take away for each of those three groups?  Answering these ensures that you thoroughly understand the topic to which your strategy applies and are able to articulate it well.

Sales.  The actual activity of articulating that message, however, is more sales than anything.  Unless you're in a position to simply dictate your expectations and press the proverbial "Go" button, you're going to have to convince others of the strength of your position.  This means that you need to not only understand the topic, but you must also understand the benefits of its execution and the risks of not doing so.  Measurable data points allow you to objectively communicate the latter part of that and also allow you to track it going forward if your strategy is adopted.

Operations.  Tracking its success is incredibly important, as you'll undoubtedly agree, because you will need to know as soon as possible if things don't work as expected and address the problem immediately.  This may require on the fly adjustments or a complete reversal of your position.  Since a compete reversal / rollback would result in a hit to your credibility, contingency plans must be developed and ready to execute should the need arise.

You're probably asking yourself, "is all of this really necessary?"  The answer is neither yes nor no, but instead depends on the importance of the goal itself and the cost of failure.  To put it another way, execution goes a long way but without the guidance to know where you're going you'll only get lost along the way.

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

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

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