From the Ask Tom mailbag: Kurt writes,

Question:
I think we all agree that employees should do their very best all day. But how do we measure/align this according towards our company’s deliverables? How do we translate doing your best towards real life results?

Response:
I can do my best and due to circumstances, the desired result may still not be achieved. I can also do less than my best, and due to circumstances, the desired result may nevertheless occur.

Real life results come from the decisions of the manager. It is the manager who decides appropriate resources and adjusts those resources according to circumstances. It is the manager who decides which tasks will be completed and given priority. If a team member’s best performance fails to net the result, it is the manager who should be held accountable for mis-estimating the effort required for success.

It has been my experience that most team members will always give their best.

When a team member fails to give it their best, due to a personal situation affecting the working behavior, I hold the manager accountable. Every manager should know every team member. They should know every team member’s spouse, and whether they play softball or go fishing on the weekends.

When a team member fails to give it their best, due to a poor working environment, I hold the manager accountable for the systems that created that environment.

When a team member fails to give it their best, because they are attempting to take advantage of the organization, violating their contract to do their best, I hold the manager accountable for identifying that behavior and taking steps to either correct it or remove the person from the team.

“So, it’s not me, but, Joe, who is supposed to motivate his team?” Alicia asked.

“No, that is not Joe’s role, as a supervisor,” I replied.

“Okay, so if he is NOT supposed to motivate his team, how IS Joe supposed to get the work done?”

“Alicia, when you hired Joe to be the supervisor, how did he put his team together?”

“Well, Joe had never really hired anyone before, so I helped him screen candidates and I made recommendations.”

“And what if Joe didn’t like your recommendation?”

“Well, Joe is an adult, and he had the final say. If there was someone he didn’t want on his team, I didn’t force him,” she explained.

“So, that’s the first answer to your question of how Joe is supposed to get the work done. While you (as the Manager Once Removed) may help and qualify candidates for his team, he has the authority to veto any appointment?”

“Yes,” Alicia nodded.

“And if, in his judgment, as a Supervisor, he feels that a team member is either not doing their best or that their best is not good enough to complete assignments, does Joe have the authority to deselect that person from his team?”

“Well, yes, I mean he can’t just fire someone, we have a process for that and it requires some approvals from HR and such.”

“But Joe has the authority to deselect someone from his team?”

Alicia continued to nod. “Okay, but there has to be more,” she coaxed.

Alicia was trying to make complicated sense out of this. “Each day, Joe’s team is required to show up for work and do their best,” she muttered. “I don’t get it. It’s too simple. What if we are not getting the results we want?”

“If Joe’s team shows up every day and does their best, what could they do to get a different result?” I asked.

“Well, Joe could have them do something different, reassign a route, load the trucks differently to make fewer trips, double check the load for missing items.”

“Exactly, but who is responsible for making those decisions and assigning those tasks?” I continued.

“Well, Joe is,” she replied.

“So, the team shows up and does their best. It is Joe who we hold accountable for the results of the team.”

“He always has an excuse,” Rachel continued. “Every time I attempt to hold him accountable, whether it is to meet a deadline or turn in the work complete, he always has an excuse. Sometimes, I think he spends more time creating the excuse than completing the project.”

“Which excuses are the ones that you believe?” I ask.

“What do you mean. Sometimes they are excuses, sometimes they are reasons.”

“So, there is a difference between an excuse and a reason?”

“Well, sometimes there are circumstances beyond his control. Sometimes there are very real reasons for missing a deadline.”

“And those are the one you believe?”

“That’s not the point,” Rachel pushed back. “The question is, how can I hold someone accountable who ALWAYS has a legitimate reason for failure?”

“Rachel, the excuse you accept as a reason, is the one that you believe in the most. The more you, as a manager, believe in the excuse, the more it becomes a legitimate reason. It’s a puddle YOU jumped in off the high diving board. Does it matter whether its an excuse or a legitimate reason? You are still in the same place, with a missed deadline. At that point, what really matters, certainly not the excuse?”

“What matters is getting the project finished,” she flatly stated. “I need to know what the next action is, to get the project finished.”

“Then, if you are listening to excuses, or reasons for failure, you are listening for the wrong thing. You are asking the wrong question. If I tell you a project will be late, do you care why?”

“No, I want to know what it will take to deliver the project on time, in spite of the reason.”

“That’s a much better question. So, get off the high diving board. Don’t ask WHY? Ask, what’s your next action.”

“What do you mean – No surprises?” Rachel quizzed. “My team member must know that this conversation is coming. Everyone is constantly correcting his mistakes, making him do re-work.”

“So, you want to keep him guessing? You see, surprise works both ways. As his manager, you are surprised when he underperforms, fails to meet a deadline or turns in work with mistakes. What happens to your trust, when you, as a manager, are Surprised?”

“The trust level goes down,” Rachel replied. “It’s at the point now, where there is almost no trust at all.”

“So, as the manager, you are surprised when your team member fails to meet a deadline, and your team member is going to be surprised when you have an accountability conversation with him?”

Rachel nodded, silently, her eyes darting back in her brain. Finally, she spoke. “And we don’t trust each other. So, how do I prevent surprises when I go into this accountability conversation?”

“Pretty simple, really. No surprises, no ambushes. When you schedule the conversation, tell him the subject of the conversation will be about his current performance on the Phoenix project and the improvements we need going forward.”

The blood was draining from Rachel’s face. The truth does that, sometimes.