Any course in fundamental sales techniques will include material on handling a prospect's objections to closing a sale. A salesman's ability turn a recalcitrant objector into a willing buyer is pivotal in determining their success in challenging sales competitions. As technical consultants, we sell our opinions nearly every day. Some opinion buyers are willing, but others full squarely into the objectionista category. So, how are we to handle objections which threaten to void and devalue our valid opinions? Imagine—your opponent, Jimmy the IT Naysayer—here are six techniques that a novice can call-on to put Jimmy in his place and live to fight another day.
- Direct evidence
- Anecdotal evidence
- Standing on experience
- Invoking higher authority
- The bake-off back-off
- Tactical retreat
Direct Evidence
The most obvious means to handling a technical object is to have the data on your side. Feel people have the will-power or wherewithal to consume and counter a well-formed assertion back by data-oriented, detailed, documented evidence. To the extent that significant objections can be anticipated, prepare these powerful tricks in advance and keep them close to hand. Shutting down an objection with such an attack of preparedness on first utterance is the surest way to close a distractive avenue. This is sometimes known as "blinding with science".
Anecdotal Evidence
Knowledge Warriors are people. Employees are people. What makes our opinions more valuable than Jimmy's opinion? "Best Practices". Be careful, the phrase 'best practice' sounds like an English phrase; it is not. 'Best practice' is a Swahili phrase meaning: things other similar people (clients) have done in similar situations (related projects) that didn't get those people (project participants) fired. Can Jimmy refute your direct experience with such best practices at enumerable, unassailable stable of past successes? Not likely. Ideally, you will use ACTUAL anecdotes. Absent of ACTUAL anecdotes, their closest available proximate may have to do.
Standing on experience
Similar in concept to the anecdotal evidence defense, a stand on experience is playing your long view against the shorter sight of your technical naysayers. Naturally, you may stand on experience firmly only where your perceived experience exceeds the opponent's in duration and/or substance. A successful stand on experience play might play like this:
Jimmy: "This approach doesn't seem very good. What about the inherent instability of the underlying architectural SOA synergy?"
Knowledge Warrior: "Bruce, may I call you Bruce? Bruce, my years of experience are telling me that 'swamp nuts' are the answer. We can always handle the instability issue later."
Invoking higher authority
When your own experience is insufficient to carry the day, you may borrow from some jointly respected authority figure, in actuality or in principle. In actuality, you should be able to quote the authority figure as if you were a regular confidant. "Oh, at dinner the other night, Tim said that blogging is for losers." In principle, you will engage in supposition about the authority's opinion in the matter—to take-on a plausible position based on what so-and-so might think about this-or-that. "Oh, I think we both know that Ron would say that even reading a blog is for losers." The halo effect incurred from invoking the authority may make-up the difference in the apparent deficit in your own experience.
The bake-off back-off
Often objectors are looking for plausible statements that cast doubt on your opinion without requiring them to prove their base assertion. Usually they are looking to avoid work by objecting in the first place. Using the bake-off back-off plays on the opponent's unwillingness to put their efforts where their mouths are. It might go like this: "Jimmy, I am pretty sure that my approach is better, but I am willing to let you try implementing your idea and then we can compare results side-by-side. How would next Tuesday look for you?"
Tactical retreat
Perhaps my favorite gambit is the tactical retreat. Following the sage advice of Sun Tzu, every Knowledge Warrior strives toward glorious victory whilst recognizing that an ignoble retreat is often necessary to winning the war. The tactical retreat involves finding an issue to which you can safely admit defeat in order to gain credibility in the eyes of your audience—credibility that you will spend in-defense of another more critical point. At tactical retreat might break down like this:
Jimmy: "I read in Slashdot that Pega is terrible at sandwich making! And what about system integrations? Isn't TIBCO better for systems integration?"
Knowledge Warrior: "I hate to admit that Jimmy has a point… Pega is NOT good with sandwiches. The product is really focused on integration at the expense of a cohesive sandwich strategy."
In the end our solution need not be all things to all people, just all things to THESE people—our prospects.