Category Archives: Accountability

Excuses and Reasons

“When you evaluate his effectiveness, given his resources and his challenges, how does he stack up?” I asked.

Audrey was quick to reply. “No way. That’s the problem. We have a results based performance review system. He is obviously not getting the results we want, but there is always something, some circumstance that prevents him or his team from delivering the goal. And that something, that circumstance always seems to make sense.”

“You mean the excuse that gets him off the hook is the excuse that you believe.”

Worldwide Conspiracy

“We call him, teflon,” Audrey said. “Nothing sticks. Things go wrong in his department all the time, but he always has an explanation why one thing or another caused the problem. Always something out of his control. Not his fault.”

“Has he ever taken responsibility for any problem in his area?” I asked.

“No, he has never had to. You would think there is a worldwide conspiracy out to get him and foil all his plans. Even when I don’t buy his excuse, he has a backup excuse to replace it. Do you think he is just unlucky?”

“Audrey, sometimes the explanation for the problem tells you more about the explainer than it does about the problem.”

Three Accountabilities

From the Ask Tom mailbag:

Question:
You talked about Managers and systems. And you described the most important system for a Manager as the People System. What’s inside that system?

Response:
There are three primary accountabilities for any Manager.

  • First, is that the Manager is accountable for the output of the team. I don’t listen to excuses that some team member failed to perform, or some other team member fell short. I hold the Manager accountable for the output of the team.
  • The ingredients that support that output are the ability of the Manager to assemble the team together. This has a great deal to do with identifying and selecting talent.
  • Once assembled, the Manager must lead the team to work together, competently and with commitment in pursuit of the goal.

Failure in any part of this system falls to the Manager.

Everybody’s Busy

Crystal looked across the table with a grimace on her face. She had a project to delegate and just returned from a circle of the office looking for a candidate.

“As I walked around, everyone looked so busy,” she said.

I smiled. “And you let that fool you?”

“What?”

“The fact that everyone looked so busy was a trap you set for yourself.”

“A trap?” Crystal was curious, but she wasn’t sure she would like the answer.

“As you walked around looking to hand this project out, what was your purpose?”

“Well, it’s a project I have been doing over and over for the past two years. It would save me a couple of hours a week if I could find someone to do it for me,” she replied.

“So, your primary motivation was to save yourself some time?” I didn’t wait for the answer. “So, tell me, what’s the major benefit for the person you would delegate this to?”

Crystal hadn’t thought about this, but she responded quickly. “Well, they would gain a new skill.”

“And what else?” Over the next few minutes, Crystal made a list of 12 benefits to the team member. The list included:

  • A sense of accomplishment.
  • Feeling a greater part of the team.
  • Feeling more valuable to the team.
  • A sense of contribution.

“Crystal, do any of these things have to do with saving you time?” I asked.

“No. Most of these things have to do with challenge and development.”

“So, get out of your time trap. I want you to make the circle again, but this time, think about the person who would see this as a positive step in their professional development.”

Crystal didn’t move. “You know, I don’t have to make the circle. I already know who needs this project. You’re right, she is busy, but this would be important to her.”

Mama Told Me

“My mother taught me that if you want it done right, you have to do it yourself,” proclaimed Judith, repeating the sage advice she learned in her youth.

“Interesting,” I replied. “Why do you think your mother said that?”

“Well, people just never do things the way we expect them to be done.”

“And, why is that?” I wanted to know. “Why do you think they might miss the quality standard?”

“I don’t know,” Judith replied. “I tell ’em what to do, they just fall short.”

“Did you explain what the project should look like when it’s done?” I pressed.

Judith paused. “I just told them to get it done.”

“So you told them what to do, but not how well or by when?”

“Shoudn’t they be able to figure that out?” Judith sighed.

“I assume they did figure it out, it’s just what they figured is different than what you figured. Didn’t your mother also tell you if you don’t like what’s for dinner, you should say something sooner?”

Change or Shift?

“Look,” I said, “if you want to fire this guy, or just cut him off at the knees, you don’t need this. Do this, only if you want to see him correct the misbehavior. Otherwise, just fire him and get it over with. You don’t need me for that.”

“I just don’t see any other way,” Alice stated flatly. “I gave Barry a list of about 15 things he needs to change if he wants to stay on the team.”

“What about the other five that didn’t make the list?” I grinned.

“You’re right, I guess I was piling on.”

“Look, if the solution seems difficult,” my grin disappeared, “what is the likelihood that Barry is going to jump in and make everything right?”

“Not much,” Alice replied.

“If you want to raise the probability that Barry will actually change his behavior, he has to truly believe that the solution will be easy for him. You have to break it down to its simplest terms so he can understand that we are not asking him to scale Mount Everest.”

“So, I need to just pick one thing he needs to change?” Alice said, narrowing her list.

“Instead of asking Barry to change, why don’t we start by asking him to shift. Shift is a lot easier than change.”

An Expensive Meeting

“One more thing, there is one more discipline that is critical to the success of this time management system,” I responded. “I was taught this several years ago by a firm who truly understood its power, it’s the weekly review.”

“Each Monday, every Monday, without fail, even if some members of the team were absent, there was a special meeting to review the action plans for the week. Daily was too often, monthly was too long, weekly was just right. The firm did this as a group.

“To that meeting, attendees would bring all the tidbits, scraps of paper, file notes, phone slips, due date reports along with the schedules of every person in the firm. The purpose was to review every possible action step in the time frame of that week, to make sure every person and every thing was fully scheduled.

“Around the table sat approximately $3000 per hour of billable personnel. The meeting lasted two hours so double that number. This was a $6000 meeting. That was the value the company committed to that meeting.

“The value of a full-on action-step-review on a weekly basis has been proven time and again. If you work alone, you need to meet with yourself to schedule your personal weekly calendar. If you work with other people, a mutual meeting can accomplish both personal calendars and cooperative calendars. The meeting can happen face to face or through some technical hookup when necessary.

“I always look for leverage. This is one powerful lever.”

When Does It Start?

“What’s the timespan of this task?” Reggie wanted to know.

“It depends,” I replied. “When does it start and when does it end?”

“It depends,” he smiled. “Depends on who you ask.”

“I’m asking you, you’re the manager. Timespan is a manager’s judgement. When does it start and when does it end?”

“Depends on the role I am thinking about.”

“Exactly, different roles at different levels of work see the timespan of the task differently, indeed, they see the starting point and the ending point at different places. The starting point and the ending point create the timespan of discretion, the point in the project where they have the authority to make decisions and solve problems. On the same project, we have different roles with different timespans of discretion.”

“So, right now, in my department, we have three projects under three different project managers,” Reggie mused out loud. “I have three project managers who have the authority to make decisions only within the scope of their one project. They are concerned about resources available to them, the project schedule they agreed to, the contingencies within that project when things goes sideways. They have a very sharp focus and don’t spend any time thinking about the other two projects assigned to other project managers. The project starts when the contract is signed and ends when the punch list is complete and accepted by the customer.”

“And you? When does the project start with you as the Senior Project Manager?” I pressed.

Reggie nodded. “For me, it starts way before the contract is signed. I have to work with our sales department to see what we have in our pipeline and what is likely to close. Based on our closing ratio, I have to decide if we have enough project managers with the capacity to handle all the projects that are likely to come under contract. I have to continuously monitor that pipeline to make sure we have enough work to keep everyone busy as project managers cycle off completed projects. I have to figure out what they are going to do next. So, the project timespan for me, over multiple projects, begins long before the contract is signed and I am accountable for the workforce long after specific projects are complete. It’s a different level of work.”

A Manager’s Goal

“I thought I was very clear,” Marianne grimaced. “It was important for the team to understand and take ownership. This is a very important team goal.”

“Describe what you see?” I asked.

“Their words are supportive, but their actions are passive. There is no skip in their step, no sense of urgency, no critical eye for detail. It’s as if they are just going through the daily motions.”

“You described the project, what you are trying to accomplish. Whose goal is it?” I wanted to know.

“Well, it’s a team goal,” Marianne explained, sounding like I should have figured that out on my own. “I need the team to work together, support each other, cooperate. That’s why it’s a team goal.”

“Have you ever heard that if it’s everyone’s accountability, it’s no one’s accountability?”

That was a stumper to Marianne. A slow burn in her brain. “So, I have to single one of them out?”

“If it’s not the team’s goal, whose goal is it?” I repeated.

Marianne did not like the realization. “If it’s not the team’s goal, it must be my goal,” she flatly stated.

“And, if that’s the case, what changes?”

Written vs Verbal

Reggie was adamant. “I believe that using a written memo is the best approach to communicate my vision of the project, because it ensures consistency and allows everyone to refer back to the information whenever they need it. I feel that face-to-face communication might lead to misinterpretation or forgetting important details.”

“Written memos are useful,” I replied. “Tell me more?”

Reggie was quick to continue. “Sometimes I feel like the message gets lost or diluted when I communicate verbally. There have been instances where team members seemed distracted or didn’t grasp the complete vision during our face-to-face discussions. That’s why I thought a written memo would provide a clearer message.”

“Maybe that’s the downside of a verbal conversation. What about the upside?” I pressed.

There was a pause. Lasted forever, but silence often does the heavy lifting. “A verbal discussion, in a meeting, allows for immediate feedback on the project, understanding its purpose, its scope, its sequence. It may also surface questions that everyone has, but most are too timid to ask about. It might also create a sense of connection and trust in the team.”

“In what way could you combine both the clarity and consistency of a memo, a written description, with the improvisational value of a robust discussion?”