Skip to main content

The Art of Pursuasion: A Helping Hand from Sales

I recently stumbled over this really great article from Steve Martin (not the comedian) in the Harvard Business Review on "Personality Traits of Top Sales People."  The article had some surprising revelations, most of which I realized could end up helping almost all of us in our daily lives one way or another.  It's a quick read, so do please run off and read it.  But I had a couple of thoughts about how Steve could help the rest of us out.
From Jeff Moore,

Professional sales people are role models to all of us in at least one crucial thing:  the ability to pursuade.  Sales people get their targets to do two very hard things:  make a decision, and commit money to be spent on that decision.  In our lives, we may feel we have had a "big win" if a decision maker we work with tentatively agrees to go along with a suggestion we have made for a while on a trial basis (while planning to disclaim all knowledge if it goes south), so long as it doesn't cost anything.  Now picture that deal if it had been handled by a real professional:  the decision maker would have committed to the idea in the budget!  Perhaps a supportive email would have been sent!  Hands could have been shaken.  That's what I'm talking about!  How do we get there?

Surprisingly, to me (sorry, professional sales friends), it's not by being ostentatious or even friendly.  Top traits are:
  1. Modesty
  2. Conscientiousness
  3. Achievement Orientation
  4. Curiosity
  5. Lack of Gregariousness
  6. Lack of Discouragement
  7. Lack of Self-Consciousness.
Actually, when I compared this list of traits to the personalities of people I know are top sales people in my company, I realized they are very true, but I hadn't recognized them before.  So thank you HBR!  Additionally, though, I had a couple of thoughts about this, in terms of persuasion you or I might need to do on a daily basis:

Develop a pursuasive persona:  it's not what you might think!

If you are a person who likes to get her way, (and who isn't?), then here is a behavior strategy to cultivate in a work setting:  internally, be a man or woman of steel:  determine your goals in a way you can measure (brush up on S.M.A.R.T. goals), and then pursue those goals doggedly, sloughing off discouragement and self-consciousness.  This advice encompasses traits 2, 3, 6, and 7, above.  But externally, be modest, quiet, and somewhat aloof, coming out of your shell only to ask a lot of questions (1, 4, and 5, if you're keeping track).  This combination of behaviors tracks remarkably well to rules of thumb given to consultants when dealing with clients anyway (see for example Rule 22 in "Rules to being Software Consultants," "Only speak 30% of the time.").  Or think of the Art of War, always a handy reference for software consultants:

It is the business of a general to be quiet and thus ensure secrecy; upright and just, and thus maintain order. (XI.35)

In particular, understand that self-deprecating humor may not be the thing here for you or for your client.

I don't mean to be sexist, but I think especially of my women friends with this point.  Any of us who try to be friendly and non-scary as our primary communications mode may want to rethink this strategy in a work environment where we hope to be persuasive.  If we are trying to achieve anything in particular, we need the respect of our clients (or coworkers), not their friendship.  Martin says that you need to keep your emotional distance to stay in control:  "Dominance is the ability to gain the willing obedience of customers such that the salesperson's recommendations and advice are followed. The results indicate that overly friendly salespeople are too close to their customers and have difficulty establishing dominance."

Lastly, be a Tigger:  don't be self-conscious, and learn to bounce.

As Woody Allen famously said, "80% of success is just showing up."  Stay focused on the goal, and don't let small setbacks get in your way.

...because selling is what Tiggers do best!  

Popular posts from this blog

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today.  Some of these might even apply to you if you're in a smaller place.  So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else.

Here's what you should think about:

1.Your staffing pattern.  A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios.  So as you provision the project, check to see whether you can arrange this staffing pattern.  If not, you will encounter risks because of missing people.  Concretely it means that:
a.You need your user experience people (if applicable) and your analysts at the beginning of the project, as always, b…

The Agile Business Case

Many agile teams have never seen a business case, ever, and they may even be proud of it.

Our mantra is that we deliver "business value," not just "software," quicker, better, and faster, but if so, we certainly don't spend a lot of time reporting on value delivery, and in fact we may be scornful about "analysis paralysis."  As software developers, we consider ourselves to be doing quite well if we can deliver the software every two weeks (or continuously).  And this is particularly if we've enabled this frequent high-quality delivery through automated testing and automated build-and-release techniques.  We've reduced business risk by making results visible more often, and allowing the business to change direction more frequently.  We assert that along the way of course we're also delivering value.  But how would we prove it?

I've recently posited that we shouldn't even think of doing agile projects without capturing and recording s…

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA")  is the "traceability conversation."  Eventually, you will have to have one.  You may have seen one already.  If you haven't, you may want to half-avert your eyes as you read further.  It gets a little brutal.  But if you close them all the way, you can't read.
WBABA: in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration!Corporate Standards Guy:  but how do you do traceability in agile?  You have to have traceability.  It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actual quotation from the Center of Excellence for Software Traceability website!] WBABA: [cowed silence]Corporate Standards …