If you want to improve the quality and timeliness of what you get back from people, then start making good requests and getting good promises.  By good requests and promises, I mean ones in which both parties are clear they are in a performance conversation for giving their word and are awake to what they are committing each other to.  All too frequently, people make “drive by requests” and “drive by promises” – ones that are made on the run or while doing something else and where at least one party is not completely present to what they are promising.  The result is that what gets delivered is not always accurate, complete, or timely.  Making good requests and getting good promises are integral to personal leadership effectiveness.

A good promise is one that is made in response to a good request, and here is how you make a good request:

Step 1:
Request what you want, by when you want it, and explain why it matters.

Step 2:
Get answers to each of the following questions:

1. Do you have any questions about what I want, when I want it, or why?

2. Are you available to do this? Do you see when you could do the work? Are you aware of anything that could keep you from completing it on time?

3. Do you have some ideas as to how this might be done? [This is particularly important when requesting something they haven’t done before.]

4. Do you have the necessary information and resources or do you know where to get them? [This can change over the duration of a project as things that were not known become known – one reason why you would want to schedule progress reports.]

5. Are you accepting my request?

When you get answers that leave you confident the work will be completed accurately, completely, and on time, you have a “good” promise. If you are not confident, explore the answers that give you concern until you are confident. It is better to withdraw a request you are not confident will be completed than to “hope” it will get done.

Peter Bergmann suggests that the secret to ensuring follow through is to create and use a checklist when making each request.  Using a checklist (see Bergmann’s checklist) as a matter of policy increases the likelihood of making good requests, increases consistency (which builds trust), and makes the interaction easier.

Consider the case of Paul (you met him earlier in http://professorford.com/2010/02/01/is-demanding-%E2%80%9Cnow%E2%80%9D-undermining-leadership/).  He has consistently had problems with his boss not setting deadlines and calling things “high priority”.  From where Paul sits, this habit is frustrating, inefficient, and ineffective.  So he wants his boss to stop doing it and start having more complete performance conversations in which deadlines are established and agreements for actions and results clearly established.  Now, unlike many people who just complain about their bosses, Paul has actually talked to his boss about the issue, but without success.

In the face of his failure, Paul asked, “I need to come up with an angle/pitch that proves unequivocally that the form of “high priority” manipulation my boss uses is inefficient.  I need to detail a “process” to help him make better requests more efficiently. Any thoughts, resources, and editorial skills are welcome.”

I told him, “If it were me, I would want to know what my boss is concerned about, what he is accountable for and how he wins at his game.  Inefficiency may not be his thing in which case you are showing him something he may not care about. The thing that is likely to interest him is if you can show him that his actions are actually working to limit him getting what he wants or cares about.”

No matter how insane, inane, or just plain stupid the actions of a boss may seem to us, those exact same actions look reasonable, appropriate, and potentially effective from the boss’s point of view.  Bosses and the people who work for them live in different worlds – what looks “wrong” in our world looks “right” in theirs.  So, if you want to understand more about why bosses do what they do, you will want to learn more about what the world looks like to them rather than judge them from a world they do not inhabit – ours.

Paul raised an interesting issue: “Maybe that is the problem in of itself.  Maybe my requests to understand his concerns are not good enough.  It feels that when the topic comes up I am rebuffed more than answered.  I will have to think some more on that.  Maybe the simple answer is that my request is just not understood?”

What I like about Paul’s response is that he is beginning to consider that maybe he has something to do with how his boss is acting.  Rather than put all the blame on his boss, or make what his boss is doing wrong, Paul is looking at one of the things he can personally control – his own communications.

I told Paul, “Perhaps he doesn’t understand why you would want to know what they [his concerns, etc.] are. There are at least two reasons someone might want to know my concerns – to support me or to thwart me.  Since most people don’t seem to care about the concerns of others, it can be seen as strange and create suspicion and guardedness.  The key would be to make it clear you are his partner in winning and that your only interest is to support him in winning at what he needs to win at.  Any other reason is worthy of suspicion.  If any of this were the case for him, then the approach would be a closure conversation to acknowledge the past attempts and your concern that your interest may have seemed out of place and apologize for that.  Then let him know it was out of an interest in support and that you still have that and if he is willing to share with you, you promise your support, thereby creating a new agreement with him [or something like that].”

Bosses are interested in winning at the game they are accountable for to their bosses, and anything we do that does not support them in that is seen as a hindrance, a distraction, or unnecessary.  Paul’s wanting deadlines is something he wants, not something his boss necessarily sees as valuable no matter how often Paul tries to explain it to him.  However, if through the use of deadlines, Paul can have his boss win, his boss is more likely to see the value in deadlines.  Paul now has a choice, complain about the way his boss works, or become a partner to his boss and use what he (Paul) knows to have his boss win.  If what Paul has to offer has value, the proof will be in the results.

Paul wants his boss to use deadlines rather than calling everything “high priority”.  One way of accomplishing that is to partner with his boss.  Now he has to decide if he wants to do that, or if he just wants to BMW (bitch, moan, and whine) about his boss – could be a tough choice!

No doubt, inspired understanding can get people excited and energized, and there are numerous books and websites that focus on being an inspirational leader.  But inspired understanding is not enough.  If it were, Obama and other inspirational leaders would be far more effective and successful than they are.  If leaders want reliable action from others they will need requests and accountability.

One of the biggest mistakes leaders make is to assume that when people understand something, they will take the appropriate actions on their own.  That somehow the excitement and engagement that comes from being inspired will automatically translate into effective action.  Unfortunately, understanding, even inspired understanding, does not cause reliable action.  During the 2008 Presidential campaign, there was considerable speculation whether the younger voters who were inspired by Obama would, in fact, vote.  This speculation shows that the link between inspired understanding and action is not direct or tight.

How many times have we attended meetings, conferences, or seminars in which we were inspired by what was said and then left the event and did nothing?  We may have talked about how great the event was, or even what difference it would make if people did the things that were talked about, but then still did nothing.  Or, maybe some of us did take action.  Maybe we were one of the one’s who saw the value and importance in what was said and initiated some actions on our own only to find that no one else was.  No, inspired understanding is not enough.

If leaders want action, reliable action, then the way to get people into action is by having performance conversations in which they make requests and then holding people accountable for their promises through closure conversations. The American Society of Training and Development (ASTD) conducted a study to determine under what conditions people are most likely to complete a task. Their results indicate that people are six times more likely to do something when they promise actions, results, or outcomes to someone else (65%) than when they just hear a good idea (10%).  And they are almost certain (95%) to complete a task when they have a scheduled appointment where they will be held to account for their promise.

Requests provide people with an opportunity to take specific actions that forward the accomplishment of something that may, or may not, inspire them.  Well formulated requests let people know what is wanted and needed, when it is wanted and needed, and why it matters.  Getting people inspired and not making a request gets everyone buzzed, but gives them no outlet for the energy.  As the ASTD study shows, leaders who assume inspired understanding is sufficient will be frequently disappointed.  People may “feel good” about the leader and the message, but little will happen.

But requests must come with accountability.  Accountability is built in the interactions between people in which they account for the status of the promises they made to each other.  As the ASTD study shows, if this accounting does not happen, there is a substantial reduction in the likelihood people will do what they promised.  As a result, leaders lose credibility and trust by failing to follow through on their requests.

Inspired understanding clearly can energize people.  But if leaders want reliable and appropriate actions, they will combine inspired understanding with requests and accountability.  Otherwise, they run the risk of becoming “motivational speakers” people like listening to, but do nothing with what they hear.