The MTS Sydney Edition

Welcome to the Australian version of the blog, live from Sydney. This is an exciting couple of weeks as I'll be down under conducting a number of dinner speeches, meetings and training workshops. That also means that the May newsletter was delayed a day because of time zone issues - it should be out 8am on Wednesday 7th May East US Time.

This months lead article is The Challenger Sales Engineer - where I give six great reasons why the Sales Engineer is the perfect person in the sales team to execute on the Challenger premise. It's something that every good SE has known for a long time, but often a lack of courage, permission and corporate culture gets in the way.

Article #2 is an update to "The Stress Free Demo" and examines a dozen things the SE can do to reduce the possibility of things going wrong in 'the big demo". It's amazing how much relates to planning and preparation!

Book Of The Month is Gerry Weinberg's Becoming A Technical Leader. It's written more from an It-problem solving point of view, but has some great insights in dealing with and motivating the "techie". And there is a varying percentage of techie in every Sales Engineer.

Also - a reminder about The SE Manager Pocket Guide if you didn't download it during April, and also that I finally released my video series "The Consultative Sales Engineer".

Good Selling!

Technical Trials and Tribulations

So this has been an interesting 10 days in that a strange bug effectively killed our website. I learnt a couple of things:

1. It's an important part of the business.
2. It badly needs to be updated and modernized.
3. Yahoo (my hosting service) has terrible technical support as I spent hours on hold and they hung up on my several times.
4. The bug was ultimately the results of some poor code from Amazon which was mis-interpreted by Yahoo Site Builder.

But enough of my problems. We are back up, and the new content has finally been posted. You'll be able to read about The Sales Engineer Advantage - why we SE's should be rock stars when in front of the customer (but aren't). There is also an interesting article on The Five SE Manager Basics (which are actually good for everyone else as well!).

The MTS Book Of The Month for SE's is Marshall Goldsmith's "What Got You There Won't Get You Here".  It's been one of my favorite books for years, and I recently had the opportunity to re-read it as part of preparation for a workshop I ran. Well worth your time to pick up a copy and learn about the 20 bad habits that may be keeping you back.

I challenge anyone to read the book and NOT see themselves in there somewhere. You really do feel like you are putting the training wheels back on your career.

More to come. The 3rd Edition of Mastering Technical Sales is nearing completion and is slated for a early July publication, and The Trusted Advisor Sales Engineer in now underway as a planned eBook for later in the ear.

Plus I'm going to be in Australia or a week or two in May running some seminars and giving a couple of speeches.

Good Selling!

 

It's Not A Problem Until The Customer Says It Is A Problem, Unless ...

I had a very interesting experience this morning, listening in to a sales call initiated by one of my customers with one of their customers. My role was to quietly observe, and provide feedback on the entire process. I always enjoy these type of engagements as I get to learn about a new piece of technology, see buyer and seller behavior in action - plus it is great research and consulting material.

This call had a twist. After a little prompting the customer (a Senior IT Director) readily volunteered a couple of business issues that she had, the economic and political pain they were facing, and why they had to do something. In essence, she gave the sales team everything they needed to hear for some great Business Value Discovery.
 
"Not a problem", said the eager salesperson, "we can fix that for you".
 
(Now that surprised both me and the Sales Engineer on the call as neither of the problems were really in the sweet spot of the vendor. AND the IT Director knew that was the case.)
 
 Before the SE could jump in and qualify that response the customer replied:
 
"Wow. That is fantastic. Just to be sure, can you describe my problems to me in your own words?"
 
She was actually trying to help him, which was more than I would have done as a former CIO.  The rep didn't get the hint and plowed ahead with DESCRIBING HIS SOLUTION. Some amazing cloud-driven big-data social thingamabob technology.

She answered, "Yes, but what exactly is my problem?"

Common sense prevailed, I heard the SE typing a message in the background to the rep which said something along the lines of "Be Quiet!".

The SE took over, and gave a really nice paraphrase of the customers problems. You could hear the customer smiling on the other end of the phone. Things went much better.

The moral of the story? There are two.

1. "No problem" is a dangerous phrase and probably not one the customer wants to hear from you. At least not immediately.

2. It is a great exercise to paraphrase the key business issues back to the customer so that they know that you know.

 

Objections And Questions And Answers .. And Sales Engineers

I've always had a problem with the skill of "Objection Handling". Let me clarify that - not with personally handling whatever a client may ask me, but in the actual labelling of the task. Here's why.

I think "Objection Handling" is a salesperson activity. As in "I just gave a great pitch, and if I can hammer through these last few objections I'll get the deal!" It sets up the entire activity as something that is a little confrontational, maybe defensive and certainly becoming "us" (vendor) against "them" (client with money).

Sales Engineers Don't Handle Objections, They Answer Questions

What I've come to realize over the years, based on listening in to thousands of sales calls plus my own experiences in selling MTS services, is nearly 90% of the issues a customer may raise are ...  simply raised because they want an answer to a question. In fact you can turn any objection into an implicit question. Even the classic your solution costs too much (nicely handled in this Visualize Blog Post) can be reframed as "help me to understand the value of your solution and why I should care?"

I feel this approach has a few benefits.

1. It ensures that in the customer conversation you listen to understand, instead of listening to respond. A crucial part of active listening.
2. It reminds you that you have to understand why a customer is asking the question. And if you don't know - bounce it back and find out!
3. It positions you as the customers advocate and a step closer to that "Trusted Advisor" status.
4. You'd be amazed at what you can learn about a person and the company based on the questions they ask. (Hmm - think about that during your next Discovery call.)

There are some warnings too.

1. See point #2 above. If you don't know why a question is being asked - that is a danger signal in itself.
2. Make sure that you share just enough to answer the question. For many technical SE's it is viewed as an opportunity to show how smart you are. Not the purpose of the meeting! It really isn't.
3. Don't stray into other areas. Stay away from sales-type responses (for example, the standard SE response for pricing is "I Know Nothing")

So give it a try. Think "Answering Questions" (with Short Amazing Answers) instead of "Handling Objections" and see the difference it can make.
 

Micro-Resolutions And The February Newsletter

 

So much for the good intentions about blogging more in 2014. So .. I decided to follow the advice of the latest business book I read and reviewed .. Small Move, Big Change By Christine Arnold. She says that New Year Resolutions (or any kind of resolutions) are mostly destined to fail and proposes an alternate approach in which the resolutions are made on a smaller and more measurable scale. So instead of saying "I will do a better job of blogging in 2014" I instead created a micro-resolution which states "I will blog the day before the monthly newsletter comes out and two weeks after that."

Its measurable, very achievable, and may well turn into a habit. I like it!

The February Newsletter - which will now go out to almost 20,000 SE's across the globe, features two interesting articles. The first "Why Do Bad Sales Calls Happen" looks at poor sales calls from the SE point of view. You'll discover that although the effect is very measurable, your view of success is different from that of the salespersons. The good news is that if you decide to take action, instead of complaining, there is a lot you can do to lower the percentage of bad calls to participate it. It's not that hard!

Maybe to get those calls fixed you need to improve your email communications. That is what "BLUF: Bottom Line Up Front - for Email" examines. You'll get seven practical tips for improving email and shortening your reading and processing time. This months "Ask John" deals with the problem of reps scheduling sales calls during presales training - and how to lessen the impact.

All good stuff - thanks for reading. And we will see how my micro-resolution turns out!
 

The Female PreSales Engineer

I've long been a big fan of getting more women into the profession of Pre Sales Engineering. Although I feel the industry has made some progress over the past 10 years, it is absolutely not enough. The overall percentage has wavered between 10-15% and I'm not seeing much of an upwards trend.

It's important because companies are missing out on a vast potential talent pool, and (accuse me of being sexist) women just listen better and generally do a better job of asking questions and conducting discovery. I'm not even going to touch the empathy situation or the attention a female SE may receive when presenting to an all-male customer/IT group. Yet I do feel I am entitled to say that as my daughter is a presales engineer (with an Engineering Degree) and I know what she has gone through.

A few recent experiences this year have brought this to bear.

1. Wow!

For the first time ever - I had a class where there were more women than men. First time. Amazing! Thanks Christine and Stephanie!!

2. Industry Variations

 

Let's say , for math simplification, that my typical workshop has 20 SE's in it.

 

The numbers I've tracked over the years show that the number of women varies from 0 to 8. Breaking that down further. IT infrastructure/"plumbing" companies have by far the lowest percentage. The more technical/geeky the product is, the lower the percentage and diversity drops and rapidly approaches zero. I've had three classes this year with zero women - and the class represented the entire national or worldwide SE team.

 

Hardware companies are little better.

 

General software companies seem to hover around that 10-15% level.

 

Application type companies (ERP, CRM and HR) trend higher and the ratio can reach 25% or more.

 

3. Hiring and Recruiting.

 

Many SE leaders tell me that they cannot even find experienced candidates to hire. So how about a grow-your-own associate program? Or look at your technical support / customer relations team?

 

4. Global Implications

 

Much as I bemoan the stats here in the US - it is even worse in most parts of the world. Asia-Pacific-Japan-China has a long way to go. Parts of Europe are better than others. Yet there is hope -  Early this year I ran 2 workshops in India and there were a significant number of young female SE's in the class. With just a little encouragement to speak up and try new things - they stole the show and put their male colleagues to shame.

 

When I look back at my career, some of the best SE's who ever worked for me (and I like to think that I did make a point of hiring women to diversify and improve my teams) were women. No question about it - and you know who you are. Two of my best ever SE managers were women.

 

Lets make a difference and take a positive step to improve the profession. Evangelize what we do - and lets recruit the next generation of SE's in a 50/50 mix - it will make us all better.

 

What do you think?

Check The Calendar!

For those of you whose fiscal year ends Dec 31^st, or even if it is just the end of the quarter it is time to check the calendar. Last week I sat in on a North America business review for a technology company that was focused on closing as much as they possibly could in their Q4. “Drain The Pipe” was the phrase of the day.

Except ..

50% of their deals were going to close between December 20^th and December 31^st. (15% were closing on December 25^th!)

90% of those late December deals were scheduled for a Proof Of Concept or heavily customized demo between now and December 20^th – (which is 35 actual days and in reality 32 or 33 business days because of the US Thanksgiving Holiday).

The math didn’t work.

First – given the timing of the holidays, a massive proportion of the buyers, recommenders, approvers and signers will be celebrating the holidays and taking off the entire week of the 23^rd and most likely the 30^th and 31^st as well. No-one is going to be there to complete the sale.

Second – looking at the number of days required to either run a POC to completion or create a custom demo (it’s a highly configurable system) , there were too many days and not enough SE’s – by an overage factor of 100%.

Something had to give. In the end we scrubbed the pipeline, developed some prioritization guidelines and “borrowed” a couple of engineers/consultants who could quickly configure a number of similar demos. They’re still 20% over.

The message – you may the greatest goals in the world for this quarter – but are they logistically and socially achievable? It’s not just the responsibility of sales to look at these things. How does your calendar look for the next 7 business weeks?

(And then next quarter we have the Chinese New Year ….)