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

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

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

Application Development Done Right

In a previous article, entitled DevOps as the Ultimate Panacea? , I described how developing code without thinking about the current needs of the end user as well as the future needs once they've become accustomed to using your application ends up not only frustrating them but also can result in customer churn and ultimately lower revenues.  In this article, I'd like to describe something simple that I came across today that shows a definite degree of effort to do quite the opposite. Recently, we had a severe snowstorm, one with blizzard-like conditions, which is unheard of in central New Jersey.  Being responsible adults, my wife and I went to the grocery store to stock up on essentials (read:  chips, chocolate, etc.) in case we get stuck at home. As we were ringing up our order, the cashier mentioned to us that the store has a mobile application.  Since both of us are in technology oriented professions, we were skeptical about the need for a grocery store mob...