Category Archives: Accountability

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?”

Out of Sequence

“I’m having a tough time with my team, struggling to meet the project expectations I set for them,” Sheila explained. “It seems they have different interpretations of the project deliverables, a bit of confusion, making it difficult to nail down accountability.”

“So, tell me what you told them?” I said.

“We had a team meeting about the project, making the message consistent to everyone on the team, so, I’m not sure how people got off track. I’m not even sure how what they are thinking, I just know each of them has a different take.”

“How so?” I pressed.

“It looks like everyone started at a different place in the sequence. This is a linear project with specific steps, one after the other. But, one person is starting on step three and another on step eight. They told me they were trying to think ahead, so when we got to that step, it would already be done.”

I wasn’t skeptical, but wanted to more detail. “And, the problem is?”

“Step three depends on the outcome of steps one and two, it’s a dependent step. We might even be able to skip step three depending on how steps one and two turn out.”

“And, I am sure you clearly described this?” I smiled.

“No, I just assumed the team would figure that out,” she explained.

“So, if you had to do the meeting over again, what would you, as the manager, do differently?”

Gauge the Risk

Aaron was in a pickle. He was a firm believer that, as a manager, delegation was his most powerful people development tool, but he was uncomfortable with the possible outcome. If this delegation failed, it could be disastrous. His dilemma was “who?” Who should he pick to head this project?

His top gun was reliable, but always overloaded with work. Aaron wanted to spread the responsibility to a young, up and comer, but this would be a stretch, with the distinct possibility of failure.

Selecting the right team member is the absolute toughest step in delegation. The manager can do everything else correctly, but if the wrong person is chosen, success may be fleeting.

Selecting the right person is a process of risk management. If the purpose of delegation is people development, and understanding that people learn the most from their mistakes, risk management becomes the rule of thumb to determine who gets the nod.

If you work in a nuclear power plant, you have to pick your top gun every time. If you run an ice cream shop, you can afford the occasional misstep. Gauge the risk, then pick the person.

Drill a Hole in the Wall

I was walking the floor. The drone of the saws was dampened by my ear protection. The conversation with Lloyd could barely be heard above the din.

“What’s with all the green shirts?” I yelled.

Lloyd looked around. “It’s green shirt day.”

I nodded as we ducked around a corner where the noise wasn’t so bad. I popped out my earplugs. “What’s green shirt day?”

Lloyd smiled. “It’s like the difference between a light bulb and a laser light. 100 watts from a light bulb will light up a room, but with all the light beams focused together, a 100 watts of laser light will drill a hole in the wall. Same thing works with my team.”

What Could Go Wrong?

Lonnie was working hard to change the way his team responded to problems on the manufacturing floor.

“I keep telling them that we need to be proactive,” he said. Lonnie wasn’t defensive, but you could tell he wasn’t having any fun.

“So, tell me what happens?” I asked.

Lonnie shook his head. “It’s just day after day. The problems jump up. You know, it’s not like we don’t have a clue. We know what problems customers are going to have. Heck, we even know which customers are going to call us. We just don’t ever get ahead of the curve.”

“Lonnie, being reactive is easy. It doesn’t require any advance thinking, or planning, or anticipating. Being reactive just happens. Being proactive, however, requires an enormous amount of conscious thinking. It doesn’t just happen. You have to make it happen. You have to make it happen by design. At the beginning of the day, I want you to gather your team together. Show them a list of the work you are doing for the day and for which customers. Then ask these two questions.

  • What could go wrong today?
  • What can we do to prevent that from going wrong?

Lonnie smiled. “That’s it?” he asked.

“That’s it.”