I see why performance conversations are such a confront: saying publicly what I’ll do and by when would be fine if I was sure nobody was listening!

So, I have created a timeline for getting my “management is missing” summaries – including solutions – out on the Management-is-Missing blog before the end of December. And I’ll meet with my weblog guy to learn how to turn the prototype into something user-friendly – in that timeline too.

To box myself in, I’ve requested an appointment with him. So as soon as he picks the date and time to meet, I’ll have an agreement to turn over a deliverable.

When I know someone will be expecting to meet with me and discuss my deliverable, I have an obligation to produce, and to arrange my schedule to do the work and be at the meeting. That’s why performance is a product of agreements.

OK, I’m a woman at work!

Deadlines are specific – they tell people the exact date and time by when you want to receive something or start something.  For example, “by Thursday at 9AM” or “at 10AM on March 23, 2012”.  Telling people you want things “ASAP” (as soon as possible), “when you get a chance”, “first thing”, or “at the next opportunity” is not a deadline.  Although you may have a clear idea of when you mean, they don’t and won’t know how to schedule their work.  Giving people a specific “by when” reduces the chances of being told later “I didn’t know you wanted it then.”

Deadlines increase accountability – theirs and ours.  If you are going to give a deadline, be prepared to receive what is due at the time its due, don’t be “out of the office”.  The accomplishment value of deadlines is diminished if people believe you are not serious or if you give false ones (saying you need it by a date when you really don’t).

Deadlines are a tool that can dramatically increase the accomplishment and success of both parties.  If you aren’t using them, try adding them to your requests.

Complaints are prevalent in organizations.  People complain about the weather, about their work, about their coworkers, and about their boss(es).  Although some complaints may seem innocuous, complaining contributes to a culture of negativism, lowers morale and satisfaction, gets people upset or angry, and adds to resignation and cynicism.  Complaints act like depressants, particularly when they are expressed to people who really can’t do anything about them.

But some complaints can be productive if they are directed to the right people.  Properly directed complaints can improve processes, products, and customer service.  They can lead to and support change and be a source of innovation.

If you want to increase the number of productive complaints (and reduce the number of unproductive ones), create a policy where you ask people to direct their complaints to someone who can do something about it.  If you are the someone, then listen up.  However, if you aren’t, then let them know immediately they have the wrong person and then either direct them to the right person or ask them to find out who the right person is.  This will reduce the number of complaints you listen to and train people to being accountable for their complaints.

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.  Even when you aren’t given a good request, you can have a performance conversation to convert hidden expectations into clear agreements.

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?” It is better to risk some potential discomfort upfront than it is to risk damaging your reputation by not delivering what people expect.

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 – a key for any good promise. 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.  Move ambiguous requests into good promises by clarifying expectations.

If you don’t counteroffer when you know something cannot be done, you’re setting up yourself and others for failure.

What do you do when someone asks you to do something you know you can’t get done? Do you say “Yes” and hope things will work out somehow?  Or say “Yes” knowing you’ll deal with the consequences later?  Or say “Yes” and break other promises for on-time performance?

A better way to deal with the situation is to make a counteroffer.  Counteroffers are one way to respond to the requests that make up Performance Conversations.  A counteroffer is where you say, “I can’t do A, but I can do B”. For example, say, “I can’t get it for you by 5:00 PM today, but I can get it for you by 3:00 PM tomorrow.” Another type of counteroffer is, “I can’t do A unless B happens”.  For example, say, “I won’t be able to do that today unless we can extend the due date on Project B by at least a day.”

Counteroffers communicate two important things. First, that you are not currently in a position to accept their request. And second, that you are willing to work something out.  It says that you will be responsible for what you promise, and it prevents the need for excuses later on.

To be effective, counteroffers must be made with integrity.  You can’t just say, “I’m too busy,” or, “I don’t have time.” A counteroffer is an alternative promise that includes a request. You are offering to do something, and you are re-negotiating the due dates of one or more other projects.

Counteroffers can be very effective.  You don’t always get all the leeway you ask for, but that should remind you to ask for as much as you think you need. It’s worth giving them a try, even if you think the people around you are pretty inflexible. You just might be surprised.