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?

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.

I was recently at a holiday dinner reception at the Fisher College of Business hosted by the Dean.  At my table were several other faculty members.  At some point, the conversation turned to a favorite complaint of faculty – “Why don’t students do what is needed to do well in class?”  Now, if you notice, this is a general complaint in that with a few minor substitutions, it can be applied to anyone, anywhere, at anytime.  Consider “Why don’t [fill in the person or group] do [fill in the blank] to [fill in the blank]?”

Examples:

• Why doesn’t Ed do the report according to the specifications so we can move the project forward?
• Why don’t the Democrats/Republicans put more effort into cooperation to get things done?
• Why doesn’t the faculty spend more time with students so that they will do better in class?

What each of these (any many other) complaints have in common is that someone is not doing something someone else thinks they should when and how they think it should be done.  With those at my dinner table, students were not behaving in what was considered by those at the table in a responsible way; they were not being personally accountable.

It was during this discussion that I realized something was really missing – common ground.  The faculty at the table were assuming that students saw the world much in the same way they did.  But they never tested the assumption.  They just held students accountable for not being personally accountable.

The term “common ground” has different meanings.  For many, it means a common or background understanding of something.  For example, if we both go to a professional football game, then we have a common background understanding of what such a game is like; we have a similar experience.  Or, if we both take a course on art appreciation, we have a background understanding in common. Accordingly this meaning, the way you increase common ground is by exposing people to the same or similar experiences and information.

In the case of performance and accountability, however, I don’t think this meaning of common ground is sufficient because it does not necessarily provide mutual knowledge.  Mutual knowledge is another view of common ground in which both parties know the same thing.  For example, if you like chocolate ice cream, and I know you like chocolate ice cream, and you know I know you like chocolate ice cream, and I know you know I know you like chocolate ice cream, we have mutual knowledge.  We both know you like chocolate ice cream and we both know that each other knows it.  We have that knowing in common.

There are two things that make common ground interesting to me.  One is that it seems to be necessary for good communication between parties.  The other is that it is apparently missing for most of us.  Creating common ground takes work – it takes dialogue and really getting to know people.  But rather than do that, we seem to assume that they know what we know (or they should) and then operate from there.  Or worse still, we dismiss their world as invalid.

I have just started my investigation into the role of common ground and how it impacts performance, but what I have learned so far indicates it could be a key ingredient in “misunderstandings” and “miscommunications”.

I recently had a conversation with a manager who was disturbed by her inability to meet the expectations of those “higher up” (her term).  They would give her assignments and then, when she would complete them, they would point out something that was missing they expected to be included. Has this ever happened to you? Although it is easy for this manager to blame the “higher ups” for not being clear, she shares some of the responsibility for not finding out what they wanted.

If you look at each of your current assignments, are you confident you are 100% clear about what is expected of you in every case?  Is everyone else involved in the assignment also 100% clear about what you expect of them?  Or are you assuming you’ll figure it out, or they already know?

Assumptions and expectations are “silent standards”. We take a big risk when we assume that everyone knows what to do. If creativity is desirable, it’s fine to give a general direction. But if there are specific creative requirements that matter, you’ll want to get them spelled out.

Take the time to spell things out. What should the final product look like? What are the components? When do they need to be ready? Are there other people who should be involved and if so, who?  Is there a particular method or process that should be used or avoided? What restrictions and specifications apply? Don’t take a chance: assume nothing is obvious.

Remember: everyone associated with an assignment has expectations and assumptions.  Some people expect you to ask for their advice, others want to be kept informed, and some only want to be involved in an emergency.  And, they expect you to operate according to these expectations even if you don’t know them!  Ask people to take time with you to spell out their expectations.  Yes, you have to ask.

Sometimes people are afraid to ask because it might make them look less competent or capable, or they don’t want to deal with an unpleasant reaction.  One way around this is to say something like “I want to be sure you get exactly what you want and in order to do that, I want to be sure I understand the assignment clearly.  I don’t want to complete it only to find out there is something missing that you wanted included.  Could we take a few more minutes to clarify some things?”

Getting clear creates a common ground in that both of you know what is expected.  This has the effect of turning an expectation into an agreement and gives you (and them) the opportunity to say whether you can or cannot do what they ask. If something new comes up later, you can always say, “I didn’t agree to that, but I’m willing to consider it.”  What you want to avoid is having to say, “I didn’t know you needed that,” or, “I thought this is what you wanted”.

Reduce your risk by taking time to unspoken expectations into clear agreements that everyone can see and understand.

In the absence of a deadline or due date, all you have is a ‘whenever’.  A ‘whenever’ is something that gets done… whenever they bug you enough for it, whenever you find time to work on it, whenever you feel guilty enough to do it, etc.  ‘Whenever’ is stressful, an ever-looming, unknown burden to be carried around.  ‘Whenever’s’, particularly from bosses, are fear generators – we worry about when it will come due, anxious it will be asked for before we have completed it, concerned about its impact on all the other work we have, and afraid of what will happen if we don’t get it done when they want it (even though we don’t know when that is).

Contrary to a ‘whenever’, a deadline is a tool for accountability and accomplishment.  Deadlines provide information that allows both the person giving it and the person receiving it to know how to plan and do their work.  Deadlines make both the person giving the assignment and the person getting it accountable for getting work done by a particular time, rather than whenever either feels like it should be done.  When we say this is “high priority”, we avoid our responsibility for doing the work necessary to determine by when it really needs to be done.

In some organizations, a “high priority” assignment means it is to be completed within a well known period of time, for example, 24 hours.  In those cases, giving someone a “high priority” assignment is tantamount to saying “Do X within 24 hours”.  But in organizations where “high priority” is not well defined, where managers use it indiscriminately, saying an assignment is “high priority” conveys no useful information for when it should be done, only dread and worry.

In the training session, managers from the one organization pointed out that managers are now saying things like “This is priority 1-A” in an attempt to distinguish their high priority assignment from all the other high priority assignments.  Who are they kidding?  All they are doing is adding confusion while undermining their own credibility and any chance of real accountability.

Do yourself and others a favor, make clean requests and give a due date.

Chris Argyris, well known author and management theorists, offers an explanation for this process in his “ladder of inference”.  According to Argyris, we do not “objectively” gather data.  Rather, once we form beliefs, those beliefs determine what data we pay attention to and collect.  We become selective perceivers who collect data that is consistent with and reinforces our currently held beliefs.  Contrary to the proposition “I’ll believe it when I see it”, according to the ladder of inference “I see it because I believe it.”

Prior to the advent of the internet, if magazines, newspapers, and broadcast news did not reflect a particular view, there was little opportunity for someone to find kindred spirits.  The internet changed that.  Now it is possible to find others who shared your beliefs, no matter how “far out” or extreme they might appear to be.

The impact of the internet information explosion was not to open people to wider and more diverse views, thereby bringing about more tolerance or a greater exchange of ideas.  In fact, it had the opposite effect in that it made it possible for people to find more support for their existing beliefs, no matter how well or poorly founded, while ignoring contrary facts or information.  The result, according to Kolbert, is greater polarization and intolerance.  We can see this today in the current national “debate” regarding health care reform where those on the “right” and the “left” talk past each other, ignoring, dismissing, or criticizing what each has to say regardless of its merits.  And in organizations we can see it where those in one group (e.g., “management”, “finance”) dismiss what those in another group (e.g., “employees”, “marketing”) have to say.

As read her article, I began to notice that I was subject to the very tendencies Kolbert was talking about.  I realized I look for things that support my existing points of view, while skimming over or dismissing contrary points of view.  And I was oblivious to doing it!

In response to this insight, I have taken on a new practice of listening to the other side.  In particular, I have started with the current political discourse in the country by listening to the views of people from the “other side”.  Rather than just dismiss them, I listen to understand the world in which what they are saying makes complete and perfect sense, not only to them, but to others.  After starting this practice (its only a few days old), I have noticed that I don’t get as exercised when “they” (the other side) speak.  And, I have begun to notice that those on “my side” engage in practices similar to those they criticize.

I wonder what would happen in organizations if people really started listening to the “other side”?

The idea behind offering incentives is that they make a task or activity more attractive than it might otherwise be and thus increase the likelihood that people will do it.  But, as Dan Pink indicates and the research supports, extrinsic offerings don’t always work and in fact may actually make the activity less attractive.  But does this mean that incentives don’t work?  No, it means that what you offer someone as an incentive may not be an incentive.  Whether or not something is an incentive depends on its effect on the person to whom it is offered.  Incentives are meant to incent – to arouse or encourage.  If they don’t do this, then they aren’t incentives even if you call them incentives.

Whether or not something is an incentive, therefore, depends on the person to whom it is offered.  To offer workers who want more money more time off is unlikely to occur as an incentive to them.  In fact, you are likely to hear someting like “What kind of incentive is that?”, or “That’s no incentive?”  Since whether something is an incentive and works as incentive depends on the person to whom it is offered, using incentives is a tricky business.  In fact, many managers have found attempting to use incentives frustrating because they can’t seem to find “what works” and what they can provide isn’t always sufficient.  This is one reason why books on recognition, such as Make Their Day! Employee Recognition that Works, have become popular because they focus on things managers can do other than offer incentives.

One way around this issue is to ask people who are hesitant to do soemthing you want done “What would it take for you to do this?” and then determine whether or not you are willing to “pay the price”.  Another way around this issue is to build the level of integrity in the relationship so that people are accountable for what they say and know that they will be held accountable for what they say.  Surprising as it may seem, most people truly value their word and do not want to gain a repuation for being someone who “says yes, but does no”.  Giving people the opportunity to operate consistent with their word, and then operating consistent with their word, reduces the “guessing game” of incentives.  Then, when you do want to use incentives, you can ask people and they will tell you what will work.

Although there were a variety of answers, there were two underlying themes.  The first was how to motivate people to change.  The second was how to deal with people when they resist change.  It was all I could do to say “If you stop trying to motivate them, you might find they are more cooperative.”

Stop trying to motivate people!? Are you nuts Ford?  Isn’t motivation what leaders and managers are supposed to do?  How do you expect to get people to do what needs to be done if you don’t motivate them?

The answer to that question has two parts.  The first is by making good requests and getting good promises in return.  The second is by consistently following up on those requests and promises in order to build credibility, trust, and accountability.

In many cases, “motivation” has become the code word for convincing, either positively or negatively, people to do something we want done.  Such convincing may involve trying to inspire them, making them feel guilty or obligated, offering them some inducement, or threatening them.  But regardless of its form, convincing people (motivating them) has the effect of reducing people to victims.

How does it make them victims?  Because it says we are the cause of their behavior, not them.  They are doing what they are doing at the effect of “our” motivation.  It is tough to have others be accountable when we say we are the one motivating them – so they aren’t accountable for their behavior, we are.

Why not stop trying to motivate people and let them be accountable for their own motivation?  Make good requests in which you ask people to take actions or produce results by a specified due date, ensure they have the resources needed to do what is asked (this includes time and availability), and that they have an idea of how to accomplish what is being asked.  Let them know you are taking them at their word, ask if there is anything they need from you, and set a time to meet to discuss the outcome.  Then follow through true to your word.

Something happens when people realize their internal state (motivation) is not your responsibility, but is up to them.  They become more willing to engage with you as partners rather than someone you have to convince.

Many managers believe that understanding is key to getting people to act.  Managers spend a considerable amount of time explaining, describing, and discussing things on the assumption that if people really understand what is needed, they will be motivated to do it.  The problem, however, is that understanding alone is not sufficient to get people to act.  People understand that if they want to lose weight, they need to eat less and exercise more.  But that doesn’t get them to exercise.  The same is true with people at work.  Just because they understand the need for something, doesn’t mean they will do it.

If you want to increase the likelihood of people taking action, use REQUESTS and PROMISES.  The intent of a request is to have someone else commit to producing a specific result or completing a specific action by some due date by asking them to do so.  Here’s an example of a request: “This is what I’d like you to do: Have the XYZ report on my desk by 5 PM this Thursday. Will you do that?”  When they accept your request, they make an agreement with you to produce the result or complete the action.  Of course, they can also decline your request or counteroffer.

The intent of a promise is to have you take action by saying you will produce a specific result or complete an action by a specified time.  Here’s an example of a promise: “If you need support on getting the report done, I will assign someone else to help you by the end of today.”

When people accept your requests and you make promises, both of you know what is to be done and by when.  They are no longer left to figure out what you want based on their understanding – you have told them.  Making this switch from “understanding” to “performance” (requests and promises) makes a remarkable difference in managers getting what they want, when they want it.