A model to determine if performance feedback is relevant to job performance
In my previous article, I discussed a common mistake managers make: They evaluate the “interactions with the boss” performance, and not the “doing your job performance.” So an employee can go through an entire year and not receive performance feedback on the work he was ostensibly hired to do, but receive lots of performance feedback on how he interacts with his boss.
Given this concept of receiving feedback on the job performance vs. receiving feedback on the “in front of the boss” performance, let’s create a model to help managers get closer to the actual performance of an individual, and where the performance feedback needs to be.
Here is a grid that looks at various elements that employees commonly receive “performance feedback” on. I put these elements into boxes along the “what/how” grid, with the most relevant to job performance being toward the lower left, and the least relevant up and to the right.
In looking at this grid, you can see that what is most relevant is the impact of something produced, with the next most relevant elements being the actual thing you produced, and the way you produced it. Finally, the contribution to the general environment and the communication around the thing produced is the next most relevant element. The closer to the lower left, the closer it is it performance.
Share and Enjoy
Performance feedback must be related to a performance
Have you ever received performance feedback about what you say and do in a 1:1 meeting?
Have you ever received performance feedback about your contributions to a team meeting?
Have you ever received performance feedback about not attending a team event or party?
Were you frustrated about this? I would be. Here’s why:
The performance feedback is about your interactions with your manager and not about what you are doing on the job. This is an all-too-common phenomenon.
If you are getting feedback about items external to your job expectations, but not external to your relationship with your boss, you aren’t receiving performance feedback. You’re receiving feedback on how you interact with your boss. The “performance” that is important is deferred/differed from your job performance, and into a new zone of performance – your “performance in front of your boss.”
OK, so now you have two jobs. 1. Your job and 2. Your “performance in front of your boss.”
Share and Enjoy
A Performance Feedback/Performance Management Flowchart
The Manager by Designsm blog seeks to create better managers by design. Here’s a great tool that outlines a simple flowchart of when a manager should provide performance feedback, and when the performance management process should occur. It can be used in many contexts, and provides a simple outline of what a manger’s role is in providing feedback, and how this fits with the performance management process (click for a larger image).
You’ll see that Performance Feedback starts at the task level, not the person level. You want to know what the task is, and make sure the individual gets feedback on how well he or she is performing the task. It also requires the manager to know what acceptable performance looks like. If not, then the manager is in a complex feedback situation, and both the manager and the employee agree to strategize on how to do the task differently, since it isn’t defined yet.
You’ll also notice that there is a lot of activity prior to the performance management process, which is actually a more formal version of this same flowchart. Managers need to perform this informal version first.
Let me know what you think. Do you your managers follow this flow chart? Do they skip steps? Do they add steps?
Related articles:
The Performance Management Process: Were You Aware of It?
Overview of the performance management process for managers
How to have a feedback conversation with an employee when the situation is complex
A tool to analyze the greater forces driving your employee’s performance
When an employee does something wrong, it’s not always about the person. It’s about the system, too.
The Art of Providing Feedback: Make it Specific and Immediate
What inputs should a manager provide performance feedback on?
When to provide performance feedback using direct observation: Practice sessions
When to provide performance feedback using direct observation: On the job
Share and Enjoy
Performance Feedback is about next time
Here’s a scenario: Jim reacts badly to a new change in the organization. He starts telling all of his co-workers how much he doesn’t like the change, and discusses ways to undermine or avoid the change. This causes increased doubt in the change, and even causes confusion as to whether the change is actually going to happen.
Jim manager has the option of either addressing or ignoring Jim’s reaction. If the manager addresses it, this would be a performance feedback conversation.
However, many managers avoid the performance feedback conversation. One reason for this is the manager may believe that Jim’s behavior on the job is deeply embedded in the employee’s personality, and the employee’s actions are innate to their very being. So a basic thesis emerges that “Jim is just like that.” There is the belief that Jim just won’t change. So no performance feedback conversation is necessary.
But this is an untested thesis. Jim did react badly to the news, but does this mean that he has to react the same way next time? The answer is—you don’t know until you have the performance feedback conversation.
If you don’t have the performance feedback conversation, the Jim will definitely behave in the exact same way should a similar set of circumstances occur. His behavior was “negatively reinforced,” meaning that he received no information that his behavior was incorrect and he received no adverse reaction from his manager. In fact, his behavior may have also been “positively reinforced” when the other employees start agreeing with his arguments about how he doesn’t like the change. The manager, by being silent, is letting the other forces of behavior determine Jim’s behavior in the workplace.
So the basic thesis that Jim “always is like that” only is true if he never receives coaching or feedback on what he should do instead. And when the manager does not step in, then for sure this thesis will be proven correct.
Share and Enjoy
The Art of Providing Feedback: Banish the use of “always”
Here’s a tip for managers: Banish the word “always” from your vocabulary.
The Manager by Design blog frequently writes about how to give performance feedback. Performance feedback is an important skill for any manager, as it is one of the quickest ways to improve performance of individuals on your team.
One particularly useless word in the art of performance feedback is the word “always.” Here are some examples of where a manager mistakenly uses “always” in performance feedback:
You’re always late
You always make bad decisions
You always come up short
These are examples of bad performance feedback, since they are not behavior-based, but the word that makes these examples particularly bad is the word “always.” That’s because “always” implies that the employee’s performance is eternal and permanent. And that undermines the whole point of performance feedback, which is to change the way your employees are performing, and have them do something better instead.
Let’s start by removing the word always from the three examples above:
You’re late
You made a bad decision
You came up short
OK, these are still pretty bad, but at least this feedback didn’t put an eternal and permanent brand on the employee as “always late,” “always bad at making decisions,” and “always underperforming.” At least without the word “always”, the feedback is isolated to the once incident, making it possible for the feedback to be more specific and immediate.
Removing the word “always” allows you to focus on the particular event you are giving feedback on, and not make a generalization about the person’s permanent character.
Removing the word “always” allows you to support the thesis about “late” “bad decisions” and “coming up short” with more details. By discussing the details, you at least have entry to discussion as to why this happened, and identify the forces that went into the performance.
Removing the word “always” implies that this bad event can be turned around and the next time the performance can be improved.
When you use the word “always” in a feedback conversation, it implies that there is a permanence to the employee behavior the manager is ostensibly trying to correct. “Always” makes the performance feedback conversation useless, because instead of trying to get the employee to do something differently next time (be on time, make a good decision, meet the goal), it instead sounds like a relegation or banishment to permanent underperformance that the employee can never get out of.
That’s not good for either the manager or the employee, unless you want a chronically underperforming team that hates the manager.
Finally, by saying someone is “always late” or “always makes poor decisions”, it is inherently incorrect. If that employee can find one time he was on time, or one time she made a correct decision, then the manager is proven wrong. Not a good move if you want to be able to lead a team.
So to all of the managers out there – banish the word “always” from your vocabulary.
Have you ever been told that you “always” do something? What was that like?
Related articles:
The Art of Providing Feedback: Make it Specific and Immediate
An example of giving specific and immediate feedback and a frightening look into the alternatives
Examples of when to offer thanks and when to offer praise
What inputs should a manager provide performance feedback on?
Getting started on a performance log – stick with the praise
An example of how to use a log to track performance of an employee
Providing corrective feedback: Trend toward tendencies instead of absolutes
Behavior-based language primer for managers: How to tell if you are using behavior-based language
Behavior-based language primer for managers: Avoid using value judgments
Behavior-based language primer for managers: Stop using generalizations
Share and Enjoy
Tips for how managers should use indirect sources of information about employees
In my previous articles, I’ve provided warnings about using indirect sources of information about your employees to provide performance feedback. The reasons are numerous, some of which are provided here and here. Indirect sources of information about your employees performance may include “feedback” from sources such as customers, peers or your boss. We may call this “feedback”, but it isn’t really feedback, since it is, by definition, time delayed and usually non-specific. This makes it, for the most part, non-actionable. So this information – while copious — doesn’t merit the high bar that is “feedback.” However, this is information about your employee, so let’s look at some ways to maximize the value of this information – instead of just passing it along as non-specific and non-immediate “feedback.”
What to do with indirect information about your employee
a) Try to get more info
If you get some sort of “feedback” about your employee, at least try to get information about what it is that the employee did to earn the feedback.
Let’s say your boss tells you that your employee, John, “Nailed it this week.”
Share and Enjoy
Bonus! Six more reasons why giving performance feedback based on indirect information is risky
I’m a big advocate for managers to give performance feedback to their employees. But the performance feedback has to be of good quality. So let’s remove the sources of bad quality performance feedback. One of these is what I call “indirect sources” of information. These include customer feedback, feedback from your boss about your employee, the employee’s feedback. These are all sources of information about your employee – and provide useful information, but they are not sources of performance feedback.
In previous articles, further outlined what counts as direct source of information about an employee’s performance (here, here, and here). And in my prior article, I describe how indirect sources are, by definition, vague, time-delayed, and colored by value judgments, making them feedback sources that inherently produce bad performance feedback when delivered to the employee.
There are more reasons a manager should hesitate using indirect sources of info as “feedback.” Let’s go through them.
1. Have to spend a lot of time getting the facts straight
Let’s say your boss tells you that one of your employees, Carl, did a “bad job during a meeting.” The natural tendency is to give feedback to Carl about his performance, using the boss’s input. When sharing feedback from this indirect source, you will need to go through a prolonged phase of getting the facts straight. First you have to figure out the context (what was the meeting about?), then you have to figure out what the employee did, usually relying on some combination of what the feedback provider (not you) observed, which, is typically not given well, and what the employee says he did. This usually takes a long time, and by the time you’ve done this, you still aren’t sure as to what the actual behaviors were, but an approximation of the behaviors from several sources. So the confidence in feedback of what to do differently will be muted and less sure.
Share and Enjoy
Three reasons why giving performance feedback based on indirect information doesn’t work
In my previous articles, I advocate that managers provide performance feedback based on direct observation. This way, the feedback is more likely to be specific, immediate, and behavior-based. All good things. The best sources are observation during practice, direct observation during a performance, and tangible artifacts.
Yet, managers receive lots and lots of data about employees’ performance from indirect sources: Other employees, customer feedback, the “big boss.” I generally advocate that managers refrain from “giving feedback” based on indirect sources of information, because they have some serious disadvantages:
(This article uses examples of the boss’s boss giving feedback about an employee, but the same goes for peer feedback or customer feedback given to a manager.)
1. Indirect feedback tends to provide non-specific summaries and vague generalizations.
Let’s say your boss likes one of your employees a lot. She tells you, “John really nailed it this week.” This is great! But you have no idea what it is that John did that earned this praise. Giving feedback to John on this – even when positive — is kind of awkward: “I have some feedback for you, John. Sarah says that you ‘nailed it’!” It’s great to give the praise, but without the specifics, it doesn’t make much sense. John will say to himself, “Okay, I’m not sure what I did, but I’ll take it.”
In the negative example, when the boss says, “John is screwing up, do something about it,” the manager is in the situation where it seems like performance feedback is necessary, but on what? Even though it is “from the boss,” recognize that it’s incomplete and vague. (If the boss’s boss were a “manager by design,” this kind of non-specific feedback wouldn’t be given, and would be more behavior-based.)



