Skip to main content

Value Selling? Challenger Selling? Bah!

Every so often, it seems, there is a new "Johnny come lately" on the sales scene as far as methodologies, means of engagement, etc. is concerned.  Whether it's BANT, MEDIC (or any its variants), Value Selling, Challenger Selling, etc. there always seems to be a new book that promises to make you more effective in your selling activities.  Here's and idea, however, that doesn't seem to get a lot of press coverage, in all likelihood because it's fairly obvious:  just solve the problem.

Let me explain.

With the exception of the CIO, CTO and CDO, most IT professionals aren't looking to anticipate future needs or prevent issues that will occur because they can start to develop a solution now.  Instead, they are reactive, seeing problems develop and then realizing that solutions are needed.

See if these stories sound familiar.

- The PMO is having trouble managing releases from the application development teams because compliance-related activities like developing support plans aren't done by the application owner yet these deficiencies aren't uncovered until the application has had a Severity 1 issue in production six months after it was released.

- The Security Operations team discovers that anyone using the proper version of their VPN solution can get access to the corporate network regardless of authorization due to a misconfiguration or their VPN infrastructure.

- Infrastructure Monitoring has a monitoring solution, which has been in use for years, that was bought by a large software company who decided to discontinue support for it two years ago.  Only now have the applications being monitored outgrown its capabilities, meaning that it finally has to be replaced.

In all of these examples (which are all based on recent situations in real companies), the solutions to the problems weren't pursued until the problems became large enough that they could no longer be ignored and solutions were absolutely necessary.  If you were the head of the PMO, the CISO, or the Head of Infrastructure Operations in those examples, do you need someone to challenge the way you think?  What about someone to show you the value of their solution to your business?

When I was in IT, my answer would have been, "I don't need any of that - just fix my damn problem."  Yet this seems to be the biggest challenge to all sales professionals that I've seen - they overthink things and, as a result, they spend far too much time trying to impress their customer with all of the bells and whistles of their solutions.  They should instead be showing their customers how they can stop keeping the lights on and go back to creating value for their company through innovation.

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