“Doing” is about action and activity; “deliver” is about what is handed over to someone after the doing is done.  Generally the things handed over are products (things like reports, computers, invoices, software), services (like training, consulting, appointments, performance reviews), and communications (requests, promises, authorizations).  For example, one of the things I do as a professor is teach classes.  What I deliver are lectures, presentations, exams, assignments, reading lists, and grades.

My students interact with the products, services, and communications I deliver to them.  If I deliver poorly worded exam questions, they don’t care much about the work that went into writing them, only that they have a hard time trying to figure the questions out.  If my lectures are unintelligible and hard to understand, my students don’t care what I had to do to prepare them.  Ultimately my performance in the classroom is determined by what I deliver to my students, not all the things I do in preparing the class.

I have learned that what really matters to people is what gets deliver.  When what is delivered to people “works” (meets their requirements in terms of form, quality, quantity, and time), they are satisfied and more likely to see the deliverer as a credible and reliable performer.  However, when what is delivered doesn’t work, people get upset, complain, and can even retaliate by becoming less cooperative.

It is clear that every time we make a promise, regardless of how big or small it may be or to whom we make it, we give our word.  It is probably less clear, however, that we also give our word every time we accept a promise.  When we accept a promise, we give our word to the person making the promise to receive whatever has been promised by the time it has been promised.

Making and accepting promises creates occasions for honoring our word and raises an important issue: “Where do we keep track of our promises so that we might honor them?”  We cannot reliably honor the promises we have made, or reliably hold others accountable for the promises they have made to us, if we do not have a record of the promises made.

Many people keep “To Do Lists” in which they record the things they want to do, but few of us keep “Due Lists” in which we record the promises we have made or accepted.  Unfortunately, too many of us keep our promises in our memory, which is notoriously unreliable.  The result is that we forget promises, making us look incompetent, political, or inconsistent.

By keeping our promises in something like a “Due List”, we increase the likelihood of remembering what we have given our word to and the chances of honoring our word.  This, in turn,  increases our credibility, trustworthiness, and effectiveness.

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.

I recently had a student tell me he was being personally accountable by telling me he had not seen part of the assignment, so it was not turned in. It was definitely a step in the direction of being personally accountable, but there were several things missing. First, he never really owned that he did not do the assignment. It was always “It didn’t get done because I didn’t know about part B.” At no time did he say “I didn’t do the assignment.” Second, he did not inquire into what he had done (or not done) that contributed to the failure. It was not until I asked “Did you check the syllabus to see what was required?” that he considered he might have something to do with the problem. Third, there was no commitment to taking any new actions in the future.  It seems as if the student felt that confessing he hadn’t done the assignment was sufficient to be personally accountable. But there is more to it than that.

I agree with Mark Samuel and Sophie Cliché, authors of The Power of Personal Accountability, that being personally accountable includes examining how you contributed to the situation, learning from that, and putting in corrections so as to improve effectiveness in the future. Confessing that you didn’t do something isn’t being personally accountable. And, it doesn’t contribute to personal leadership effectiveness even if it takes courage to do so and sounds like you are “owning up”. Being personally accountable requires a willingness to learn and change how you operate in the future.

What is a “sufficient period of time”? It is the amount of time it takes to get something done given (a) the nature of the work required and (b) the productivity of the person (people) doing the work.  In general, the more complex and involved the work, the longer it will take to get done compared to work that is less complex or involved.  Similarly, the more productive the person (people) doing the work, the less time it will take than someone who is less productive.

Example

One of the jobs I perform several times each University quarter is grading exams.  How long it takes me to grade an exam depends first on the nature of the work required. Are there 50 exams to grade, or 150? Just as important, what type of exam is it? An exam that has all objective questions – multiple choice and true-false questions – is much faster to grade than an all essay question exam.

And in addition to the nature of the work, what are the factors that influence my productivity?  One is my reading speed, which is influenced by the writing quality of the student answers on essay questions. A second is my writing speed, for making comments that will give students feedback on both types of exam. And a third is my sitting tolerance – how long I can stay focused on the grading task. I find my tolerance is higher when student writing is good, and lower when it’s not.

A sufficient period of time for me to grade exams, therefore, depends on what type of exam I give and my productivity while grading. The only two ways I can reduce the time it takes to grade an exam is by (1) changing the design of the exam (more objective, less essay) and/or (2) improving my productivity.

As an example, if it takes 1.5 hours to grade one question in a short-answer essay exam for a graduate class of 25 people.  If there are four questions on the exam, I will need a total of 6 hours in order to grade the entire exam for the whole class. I can choose to break it up into four segments of 1.5 hours, or two segments of 3 hours, etc. But if I schedule less time than that, I will not complete grading the exam.

Like the Law of Gravity, we must account for the First Law of Accomplishment.  In order to accomplish something, you must have a sufficient period of time in which to get it done.  If you don’t allocate the time, it won’t get done. Of course, you can get something done in less time if you do a sloppy job. Doing incomplete work, however, damages people’s credibility and reputation.

Steps to Obeying the First Law of Accomplishment

There are four things that will help you obey the First Law of Accomplishment.

1.       Record Your Promises.  You can’t accomplish what you can’t find or can’t remember.  Keep a record of everything you have agreed to do. Write your promises and commitments down somewhere – preferably in one place, like a promise log – and then refer to it regularly until the promises are completed.

Ideally you record (a) What is due to someone, (b) Who it is to be delivered to, and (c) When it is due – plus enough particulars about the “deliverable” so you can determine how much work will be involved. Be sure to consider the different types of work that may be involved – the desk and computer work, phone and email work, research, writing, getting approvals, etc.

2.       Determine the time periods needed to complete the accomplishment.  Given the nature of the work to be done and your level of productivity, determine how much time will be required to complete the assignment.  Bear in mind that most people are overly optimistic about how long something takes to get done, and as a result they often grossly underestimate the amount of time they will need.  If something takes six hours, don’t assume you can get it done in five.

I have learned that most people do not know how long it takes to do the many jobs they have, even the ones they do on a recurring basis.  It took me several University quarters to determine how long it takes to grade different types of assignments.  And grading is only one part of my work!

Determine whether your promise for a particular “deliverable” (a promised product, service, or other result) will take four hours, or fourteen hours. And decide if it would be best to do it all at once, broken up into two or three – or more – steps, i.e., the number and size of specific “periods of time” you will require to accomplish the promised result.

3.       Determine the time available in your schedule to do the work. If you are like most people, you have far less time in which to do the work you have promised than you realize.  The reason for this is because of meetings, appointments, recurring events (including lunch and breaks), and interruptions.  When you are engaged in any of these things, you are not available for working on the other things you have promised – the “accomplishment work” that will fulfill your commitments.

In order to determine when you can work on the things you have promised, start with a blank schedule, then put in all the appointments and meetings you plan to attend, the recurring events like meals and coffee breaks, and an estimate of when you are most likely to be interrupted (and for how long). NOTE: Most of us have more control over interruptions than we think we do, and we know something about our typical patterns of timing and duration of interruptions too.

So what’s left? The time that remains after all these things are accounted for is your unscheduled time.  That is the time you have available for working on everything else – including your “accomplishment work”.  Pause a moment here to allow yourself to be shocked at how much time you are giving to appointments, meetings, recurring events, and interruptions, and how little you are giving to your “accomplishment work”.

4.       Schedule your work, then follow your schedule. Now that you know how many time periods are needed to complete the work you have promised (#2 above) and how much time you have available for doing that work (#3 above), you can schedule the work.  Put the periods of time necessary to accomplish your promises into your calendar.

One trick here is not to schedule yourself too tightly (i.e., back-to-back with no space in between), so that when unexpected events occur, you have some flexibility to deal with them.  Another trick is to use your schedule when people ask you to do things: when someone wants you to do something, pull out your calendar and look to see when you will be able to do the work required.

Remember, the First Law of Accomplishment says, “The accomplishment of anything requires a sufficient period of time in which to accomplish it.”  When your schedule is full, you will be unable to make new promises without modifying or revoking existing promises. Use your schedule as a guide to when you can say yes, and what conditions you must apply to the agreements you make.

This will put your all of your communication skills to work. You can make requests for resources and support, decline to take on something you know you cannot deliver, and make requests to change agreements on due dates for promises you have made with other people.

Conclusion

The biggest challenge to our personal performance is finding ourselves overcommitted because we have (1) failed to keep a good record of everything we have promised, (2) underestimated the amount of time a job will take, and/or (3) overestimated the amount of time available.  When we say yes to more things than we have time in which to do them, we are in an argument with the First Law of Accomplishment. This argument is stressful and unwinnable.  The integrity of your scheduling process is what produces your calendar, establishes the validity of your promises, and provides the foundation for your personal effectiveness. It’s best to make friends with the First Law of Accomplishment.

[This article is reprinted from The Great Managing Newsletter, Vol. 9, Issue 22, November 30, 2010 by permission of Jeffrey and Laurie Ford. For additional information, visit www.laurieford.com or www.professorford.com]

Accountability

Accountability begins when we agree to do something for someone else.  As soon as we accept a request and say, “Yes, I will”, we have made ourselves accountable to the other person for keeping our agreement with them.  Once we’ve said, “Yes”, we either keep our agreement or we don’t.

Most people want to perform well at work.  Few of us get up in the morning, look in the mirror and say to ourselves, “Today I am going to do the worst possible job I can and make the lives of everyone around me miserable.”  There may be a few “bad apples”, but most of us want to do a good job.  Unfortunately, doing a good job doesn’t always happen.

Sometimes we are late with assignments.  Sometimes our work is incomplete.  And sometimes our work is inaccurate or of poor quality.  Unfortunately, the people to whom we deliver our work don’t always tell us.  How often do you tell people they are late, their work is incomplete, or of poor quality?

If you are like most people, rather than say anything – rather than provide honest feedback and have the accountability conversation – you make accommodations.  You fix the mistakes, do the missing work, or have someone else redo the work.  The result is that you continue to get late, incomplete, and inaccurate work.

Getting Pushback

One reason we are hesitant to provide honest feedback is that we do not want to deal with the “pushback”, which can sometimes get emotional.  I recently returned exams to a group of 140 MBA students in the Working Professional MBA program.  They had done very poorly on the exam and so when I returned the exams, I told them to notice their reaction to the results. “Notice whether you want to blame me,” I said, “or whether you are willing to consider that the grade is a reflection of YOUR performance.”  I was concerned that they would dismiss the feedback and miss the learning opportunity.

Some students claimed that, “I studied hard and have a high grade point average”, suggesting that Jeffrey’s grades were an inaccurate estimate of their study skills or capabilities.  Other students pointed out, “The whole class did poorly, so it must have to do with the teacher,” a valid point.  Still others went silent and essentially withdrew from the discussion.

Most of the reaction to receiving straight and honest feedback about their performance was to invalidate that feedback.  “No”, they say, “this is not feedback on MY performance. This is more a commentary on you and the way you teach.”  As the cliché goes, they wanted to kill the messenger for the message.

Why Bother

The student reactions are consistent with what happens in organizations every day. The negative pushback is a primary reason that managers dislike doing performance reviews and giving direct and honest feedback. They, like Jeffrey, catch flak for it, making it uncomfortable to have the conversation and fend off the attacks.

As one manager told me, “Why Bother?  If I give people anything other than praise and appreciation, I will have upset people who are going to argue with me. They are more interested in being right than in developing themselves to be better performers.”

When people receive feedback indicating their performance is deficient in some way, they can lose sight of the fact that they once wanted to learn, grow, and develop themselves. Suddenly, the most important issue is to preserve their dignity and avoid looking bad to other people.

People want to be well regarded, respected, and seen as competent.  Of course, they want to avoid being embarrassed, or have someone question their ability. It is natural to try to explain poor performance, or give reasons for lateness or low quality results.

The challenge is to find a way to return people to remembering the good intention behind even negative-sounding feedback: we want to use the facts of our results today to help us improve our results in the future.

I use an article in my class called, “The Folly of Rewarding A while Hoping for B” by Steve Kerr.  When we say we want to support people in being better performers, but then reward them for just getting by, that’s a folly that undermines accountability.  Great managers who want high performance and accountability will take the trouble to give honest feedback, in service of developing the people in their charge.

Signage is a critical part of an effective infrastructure that allows for “silent” (non speaking) communication.  We rely on signage every day to navigate through work.  Signage is used to guide and direct traffic, get us into and out of buildings, and tell us which restroom we should use.  Signage, in the form of uniforms, also makes it possible for us to know who we are talking to, who belongs to which group, and what people are accountable for.  We depend on signage to help us coordinate work.  Given our reliance on signage, therefore, it should not come as a surprise that failing to play attention to it can create performance breakdowns.

I work on a conference project where people are assigned to different teams.  Each team has a particular accountability and must coordinate their part of the conference with others.  One way we distinguish who is on which team is by the type of name tag they wear.  That way, when the conference is happening, we can tell instantly who is suppose to be in certain places and who isn’t – all without ever talking.

In a way, it is like the way the teams on the flight deck of an aircraft carrier distinguish themselves by the color of their uniforms.  Since the flight deck is loud, oral communication is not always possible or effective.  And, because the deck is dangerous, it is imperative that coordination get done or people die.  One way the Navy accomplishes the necessary coordination is through the use of colored uniforms.

Although the conference I work on is nothing like the flight deck of an aircraft carrier, effective coordination of it nevertheless requires being able to know who is who quickly, and in many cases, quietly.  We do that though name tags.

Recently the client we do the conference for said that a new person was going to be at the conference doing work for them.  “No problem”, we said, “what name tag will he wear?”  Rather than answer the question, they proceeded to explain what he would be doing at the conference and why it would be important and valuable.  They didn’t understand that we were asking a question about infrastructure and they answering a question about activity – they are not the same.

We didn’t want to know what he would be doing, we wanted to know how to “tag” him so that people at the conference could appropriately coordinate with him.  We explained that if he wears a conference participant nametag, he will be related to in one way, but if he wears a conference worker nametag, he will be related to in another way.  No one will ask (or even care) what activities he is engaged in other than as they relate to his name tag.

All this over a name tag????!!!!!  Yes, because that is the power of infrastructure.  It is one of the key elements we use in coordinating with the world and each other.  I suspect that there are far more breakdowns and upsets related to issues of infrastructure that many of us imagine.  In our case with the conference, the client had no idea they were violating a piece of infrastructure we rely on for coordination.  Instead, they believed we were being resistant to the person (“You don’t like him?” they asked) and what he would be doing.  Each time we would ask about the “name tag”, they would try to explain what he would be doing.  We were not communicating and both sides were upset, but for different reasons.

I am beginning to wonder how much things like “resistance to change” or “poor performance” are a function of infrastructure breakdowns rather than motivation, leadership, commitment, etc.  What do you think?

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!

There are lots of reasons why we don’t like some people at work: they don’t treat us or others the way we think they should, they create problems for us and others, they don’t do what they say they will, and so on.  For the most part, these differences don’t create problems for us and we can go on about our work without much difficulty.  But occasionally the fact that we don’t like them, or the things they do, gets in our way.  It is at these times that our lack of affinity for them actually works against us; our effectiveness is reduced, our stress increases, and we lose our sense of humor.  Work gets harder and more unpleasant and it takes longer and more effort to get things done.  And, we blame them.

What we fail to consider in all this is that it is OUR lack of affinity for them that is an issue.  It is not surprising that we treat people we like differently than the people we don’t. Nor is it surprising that we use the fact we like or dislike someone as a justification for how we treat them.  When asked why we do or don’t do things for others, we are likely to respond (if truthful) “I like/don’t like them”.   We act as if they are responsible for our liking or disliking them; that it is their fault we don’t have much affinity for them.  As a result, we believe that unless and until they change, our relationship with them has little chance of improving.  We are not responsible.

Like most people, the managers in my MBA class bought into this line of reasoning.  That is, until they did an exercise in which each one of them wrote a letter to three people they didn’t particularly like.  In the letter, they were to write out exactly what they would say to the person to authentically:
1. Acknowledge the person for something they had done but which the manager had not acknowledged, e.g., completing a project on time;
2. Appreciate something about the person, e.g., a good sense of humor;
3. Apologize for a mistake or misunderstanding the manager was responsible for but had not owned up to, e.g., not providing clear directions on an assignment; and
4. Amend an agreement that had been broken but had been stepped over, e.g., an agreement to meet on a weekly basis which wasn’t kept.

What surprised each and every manager was that they had more affinity for the person after they wrote the letter than before.  They discovered that it was their interpretations, assessments, evaluations, and conclusions about the other person that was the source of their liking or disliking them, not the other person.  They realized that they could be responsible for their affinity toward others and that if they were willing, they could shift that affinity.  What they found most exciting was that they could potentially improve their working relationships with other people if they were willing to authentically engage in something as simple as acknowledging, appreciating, apologizing, and amending agreements with them.

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.