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.

Escape hatches, however, can undermine our success. When it comes to the promises we make, it helps us keep them if we cultivate a “no alternative” attitude in which failure is not an option.  One way to do this is to root out any talk about “I’ll try”, or “I’ll do my best”, or “I’ll see”.  I have a friend Blair who has a habit of saying “No problem” in response to the requests made of him.  When I first heard Blair say that, I asked, “How can you say ‘no problem’ when you don’t know if it can be done?”  His response was “If I go into something with that point of view, I am much more open to what is required and willing to take it on because I was the one who said it wan’t going to be a problem.  This doesn’t mean it won’t take work or that there won’t be setbacks, there almost always are, it’s just that it gives me a different context in which to work than ‘I’ll try.”  For Blair, saying “no problem” was a way of burning the boats.

Another way to create a “no alternative” attitude is to make promises to people you would never consider not keeping it.  Stephanie, a manager, wanted to hire a staff person.  Her boss, however, was unwilling to commit the additional resources.  Undeterred, Stephanie promised that if the goal for which the staff person was being hired was not achieved, then her boss could not only assign the staff person to someone else, but also reduce her development budget (a big deal in this organization).  By making this promise, which her boss accepted, Stephanie was burning the boats.

If you’re serious about making and keeping a promise, take a tip from Caesar: he wasn’t interested in trying, he was interested in conquest.  As Yoda, the Jedi master in Star Wars said to Luke Skywalker “Do or do not.  There is no try.”   If you want more than half-hearted efforts from people, find a way to help them burn the boats.

I encounter this complaint from the managers in my MBA classes as well as those I interact with in the “real world”. They insist that a lack of accountability is the primary source of the problems they have in their organizations.  Laurie (my management consultant wife) encounters it with her clients, some of whom maintain that the reasons for inefficiency and poor communication is because people are not being accountable.

It’s as if “accountability” has become the new mantra of managers or the new solution for whatever problems leaders might be having getting things accomplished.  “If people were more accountable, we would be much better off,” they say.

Unfortunately, the call for “more accountability” is often one sided, focusing on the lack of accountability in others, and fails to recognize that there are two sides to accountability: the “holder” side and the “producer” side.  The two sides are located in different places and both are necessary to have any accountability actually perform.

Holder Accountability is the responsibility of a person who wants something, asks for it, and “holds” that commitment until the result is produced. A person with Holder Accountability might be a manager who wants her team to handle customer service calls, or a supervisor who wants his crew to repair equipment. The manager or supervisor (or parent, or friend) requests what s/he wants and then checks back at the end of the day or week or month to see what portion of the request is completed. The manager holds people to account by asking the customer service team or the repair crew to account for their work, their performance, and their results.

When your boss gives you an assignment and then asks you questions regarding its status, she is demonstrating Holder Accountability, holding you to account for the assignment.  Similarly, if you tell a colleague you will do something for them by Friday and they ask you about it on Thursday or Friday (or the following Monday), they are holding you to account for what you said you would do.

The second side of accountability is Producer Accountability. It is the accountability of the person or group who will be producing the results or doing the work: the customer service phone team and the equipment repairmen who are doing their jobs are demonstrating Producer Accountability. They were assigned to do a job and they are doing it, and they will report on the status and outcomes as needed.

There is no “accountability” without both halves of the equation. If there is nobody making a clear request for something to be done and who cares enough about that request to follow through and see that it actually is performed, there is no Holder Accountability. If there is nobody who accepts the request to perform the work, there is no Producer Accountability. Getting “more accountability” in an organization requires accountability on both sides of the table: manager and staff, boss and worker, or any person who asks for something from another and the person(s) they ask.

Someone else can impose Holder Accountability on us, but only we can impose Producer Accountability on ourselves.  When my doctor gives me a diet to reduce my cholesterol, I don’t think about that as any kind of accountability – until I go back the next year for another blood test. She looks at the blood test results and she can tell whether I’ve kept my part of the bargain or not.  Producer Accountability is completely self-generated, and we have only ourselves to look to if it is missing. My doctor will hold me accountable by saying, “Your cholesterol has improved, but only a little bit. How much did you follow the diet?”

Authentic Producer Accountability says that we own the work we have to do – it is ours.  It’s like saying, “I will look to see what needs to be done to accomplish this, and I will do it. I will get the help and the resources needed, and if I can’t find them, I’ll get back to you and ask for your guidance in how to take the next steps.”

So, what is it that leaders are really calling for when they call for “more accountability” in their organizations? More often than not they want more Producer Accountability.  They want employees to show initiative in taking on work, to own their work, and to do what needs to be done without constant supervision and without excuses.

But here’s the catch: if a leaders does not provide a clear request with a visible outcome that permits a follow-up, they are not living up to their side by providing any Holder Accountability.  Furthermore, if a manager has no commitment to holding people to account, and following up with them regarding their performance, workers will eventually assume the managers doesn’t really cares how, when, or if the work gets done.

It is wishful thinking to expect people to generate a high level of Producer Accountability in the absence of Holder Accountability.  The key to building a culture and organization of “more accountability” starts by creating the conditions for authentic Holder Accountability.  In other words, if managers want more accountability, then they will want to learn how to assign work in a way that makes what people are accountable for clear and then hold them to account. Good Holder Accountability gives people a reason to develop Producer Accountability: with a great manager, I’ll maintain or improve my work performance even when I’m in a bad mood.

How can you improve your Holder Accountability?  Here are some ideas:

1.            Spell out the conditions and measures that must be met in order for the assignment to be considered successful.  People need to know what the job is, and you need to know how to tell if they did it. No fair saying, “Do a better job.” You’ve got to say how you – and they – will measure success.  People need to know the “what”, and if needed the “how”, they will be held to account for.

2.            Provide specific time lines and due dates for when you’ll be checking back with them. They need to know YOUR timeline for your Holder Accountability, and when they will be expected to give you a status report or a result.  They need to know the “when” they will need to account for.

3.            Follow through on a consistent and regular basis, such as weekly debrief meetings in which people have to report on the status of all their work and make projections about what they will accomplish in the following week. Holder Accountability is all about reliable follow-up on assignments and is where holding them to account actually happens.

As to building Producer Accountability, here are some tips:

1.            Be sure you assign work to people who have the ability to do the job.  When you give a work assignment to someone you know will fail, it will not build their Producer Accountability. It will build resentment, distrust, and cynicism. If you have people who can’t do the job, you may have a training problem but you don’t have an accountability problem.

2.            Be sure people have all the information and resources they need to succeed. You can’t expect people to make a silk purse out of a sow’s ear. You’ll build Producer Accountability by telling people that you want them to be specific about what resources they need, to assemble as much as they can themselves, and to come to you when they need help.

3.            Give people timelines, milestones, and deadlines. It will support them in good planning to meet your expectations.  No fair saying, “Do it as soon as possible.” Performance is a function of time, and if people don’t have deadlines, they can’t organize their resources to deliver what you want.

When you strengthen your own Holder Accountability, you also strengthen other people’s Producer Accountability.  If you want more accountability in your workplace, start building it!

When Ed Koch was mayor of New York, he was concerned about the number of accidents resulting from bikers darting in and out of traffic. Determined to solve the problem, he had “bike lanes” painted on the sides of city streets. But instead of making things better, the bike lanes actually made things worse. Drivers, undeterred by the double yellow lines identifying bike lanes, crossed them so frequently that police could not write enough tickets, and accidents involving bikers increased. As a result, Mayor Koch had the bike lanes removed, ending a futile exercise that cost the city millions of dollars.

Plenty of editorial space was given to criticizing the blunder and Koch’s poor judgment. Reporters, looking for blood, sought interviews with the beleaguered mayor. In one television interview he agreed to, which was scheduled to last thirty minutes, the host was armed with a list of questions that were sure to make Koch look bad. The host began by asking, “Mayor Koch, you spent millions of taxpayer dollars to paint those bike lanes only to remove them. That tax money could have gone to valuable social services. What do you have to say for yourself?”

Pausing, Mayor Koch replied, “You’re absolutely right. It was a huge mistake. I made the wrong decision, and I apologize.” The host, stunned by the mayor’s response, gathered herself and proceeded through her list of questions, each of which was an accusation of some kind. To each accusation, Mayor Koch gave a similar response, admitting the mistake and apologizing for it. The interview lasted for only five of the scheduled thirty minutes after which the topic was dropped, never to be raised again.

Mayor Koch’s success in this interview demonstrates the power of what we call Closure Conversations. By acknowledging the facts that New Yorkers already knew—that the bike lanes were an idea that didn’t work—and then apologizing for it, Mayor Koch completely disarmed the issue and brought it to a close. In the process, he restored some of his credibility and the confidence New Yorkers had lost in his stewardship of the city.

Closure Conversations can restore credibility and confidence, reduce resentment, build accomplishment and accountability, add velocity to projects, and increase the engagement of participants and potential participants.  Try them – they work.

[From “The Four Conversations: Daily Communication that Gets Results” by Jeffrey and Laurie Ford, Berrett-Koehler Publishers, p. 131-2]

Here is what Paul has to say about it:  “While I continually ask my boss for deadline and priority setting, I often receive non-committal responses or am blatantly ignored when I attempt to clarify his requests.  He has also taken to using the excuse that his boss “demands it now” and that is why he does it.”

Clearly there are times when bosses are under the gun to get something to happen immediately.  Emergencies do happen and unexpected opportunities arise with short response windows.  When these arise, bosses are completely justified in asking that things be done “now”.  But these should be rare occasions, not standard operating procedure.  The fact that bosses can demand something be done now doesn’t make it good leadership practice.  And passing the blame, as this boss does, only further undermines credibility, reduce other’s confidence, and creates victims who are not accountable.

Habitually asking for things “now” is inconsiderate, disruptive, and reduces the likelihood of getting them “now”.  It is inconsiderate because it denies people the opportunity to plan and schedule their work while increasing their levels of uncertainty and stress.  It is disruptive because these types of interruptions result in missed deadlines on other projects and assignments, lower productivity, and increase inefficiencies.  As a result, things that are wanted “now” can actually take longer to achieve than they would have if planned for in advance.

Habitually asking for things “now” contributes to a “fire fighting” culture where people become increasing resentful (resistant?), resigned, and disengaged.  You can almost hear the resentment and resignation in how Paul describes his response to when his boss demands “now”: “I just pull out my sheet, point to the deadlines, and say “We’ll keep working at it.”

Contrast this with what Paul says about his own use of deadlines:  “I have been highly successful in by cooperatively establishing timelines for projects.  Doing so has endeared me to my resources and I feel they are going the extra mile to meet the established deadlines.  I work at restraining the urges to push the “now” button so that when I do, I get a “now” response.”

There are times when, as Paul says, managers need to push the “now” button.  But it is possible to minimize its use.  One way to minimize its use is to plan. There is a popular saying that “Your failure to plan is not my emergency.”  Unfortunately, for people like Paul, the failure of a boss to plan does become their emergency.

Planning doesn’t have to be an elaborate process.  At a minimum it involves looking at the work that is due in the coming week(s) and making the appropriate requests in a timely manner.  One tool that can support managers in doing this planning is a weekly schedule in which they schedule not only meetings and appointments, but when work needs to be to them in order for them to meet their obligations.  Without some structure for reminding us of what is due and when, managers are left to their memories, which are not always reliable, and can result in suddenly remembering that something is needed “now”.

On the surface, habitually demanding things be done “now” might look like it works.  Deeper down, however, leaders and managers are contributing to the very things that undermine the productivity and performance they seek to achieve.  Leaders who are interested in building engaged, accountable, and reliable performers will reconsider this practice.

I recently talked to a manager – let’s call him Roy – whose company had completed a series of employee satisfaction surveys.  It turns out that although Roy’s unit scored higher than others on overall happiness, there were a few areas in which his unit was lower.  To find out why, the people who conducted the survey had a meeting with the employees in Roy’s unit in which they were asked to talk about the things they didn’t like.

“After that meeting, I am convinced people were more unhappy with work than they were before,” Roy told me.  “Why is that?” he wanted to know.

What Roy’s unit went through is what might be called “trauma sharing”, which is a form of understanding conversation in which people want other people to understand how bad things really are.  There is no purpose to the conversation other than to get the misery out.  In the process, people try to “one up” each other with how their problem or situation is so much worse than anyone else.  The result is a form of emotional contagion in which people become increasing dissatisfied and unhappy.

An alternative to “trauma sharing” is to have people talk about what they like at work and how they could get more of that.  In this case, people talk about the things that give them satisfaction and happiness.  The point here is not to outdo each other, but to share the things that you like about your work: the people, the assignments, the equipment, and humorous interchanges, anything that gives you satisfaction.  The result is a positive form of emotional contagion in which people become increasingly satisfied, animated, and happy.

People’s emotions and attitudes are a product of the conversations they are having.  If they are having conversations about things they find dissatisfying, they will become increasingly dissatisfied.  By the same token, if they are in conversations about things that are satisfying to them, they will be satisfied.  Want to increase your satisfaction at work?  Change what you talk about from what you don’t like to what you do and see what happens.

Most of us have experiences similar to those reported by Chiang.  I once order some electronic marketing materials online with a “money back guarantee”.  When I downloaded it and found it did give me what I wanted,  I emailed and called the seller – multiple times.  At no time did he respond (sorry, I don’t remember the  seller’s name), so I finally contacted my credit card company, went through their processes, and eventually got my money back. Interestingly, even though I don’t remember the seller, I do remember one of the people who endorsed him (whom I also contacted and who didn’t respond) and I will no longer consider his products either.  Unfortunately, not only do the people who “don’t respond” hurt themselves, they cast a shadow of doubt over everyone else in the business.

But “no response” is not limited just to businesses.  How many people do you send replies to when they send you something important?  How many people tell you when they got the report, the email, the proposal, or any number of other things you invested in providing them?  Is your opinion of them higher or lower as a result?

I, like most people, get plenty of emails.  Some are simply “fyi”, whereas, others want me to do something.  In each case, I read the email to determine if it is something they need to know “I got it” and, if so, respond accordingly.  I am not yet 100% reliable, but I am working on it because I think it makes a difference to the other person.  I like knowing when people get what I send them, so I assume they would like to know as well.

The other day I was changing a light bulb in my basement work area.  One of the screws holding the cover on the light was tight, so used a screwdriver to loosen it.  When I was finished with the screwdriver, I threw it down onto the workbench (I was on a stepladder), where it hit and scattered some small ceramic tiles I had been removing from a table made by Laurie’s dad.  I found all the tiles except one and was upset because its loss would mean the table could not be restored in its original form.

When I went upstairs to tell Laurie, my first thought was to say “The screwdriver knocked a bunch of tiles off the workbench, and now I can’t find one.”  And that’s when I noticed how the absence of accountability sounds – there is no “I” in the action of what happened.  My initial thought made the screwdriver accountable for the lost tile, not me.  I was the one who threw the screwdriver and my having done that accounts for why the tiles were scattered.

As I thought more about this one example, I began to notice how many places I leave off any mention of “I” when things happen, as if they happened on their own accord and I was simply an observer.  You know, stuff like “The cup feel off the dish drying rack and broke” rather than “I hit the cup and knocked it on the floor.”  The more I considered explanations for things that I have something to do with, the more I realized that the key word missing in those explanations was “I” and what “I” did that produced the result – good, bad, or ugly.

Perhaps you have noticed the same thing when people give explanations – there is no “I” in what they say except, possibly, when it is something good.  Check it out.  Listen to the explanations you and others give and see when there is an absence of accountability.  Let me know what you discover.

Of all the books Todd mentions, however, I am particularly looking forward to reading Switch: How To Change Things When Change Is Hard by Chip and Dan Heath.  Since I teach the MBA courses on managing change in the Fisher College, I am always looking for new and interesting perspectives on making change easier.

Sounds like it could be a good year for reading.