Culture Trumps

“But, I set the context for my team. We talked about the work we would receive from the process step before. We talked about how we would inspect our work before we handed it off to the next process step. I thought I was very clear,” Rory complained.

“So, what happened?” I asked.

“It’s like the team wasn’t listening,” he replied. “I even had them repeat the steps back to me, to make sure I was understood.”

“So, what happened?” I repeated. “Why did you feel the need to be so explicit? Why the need for clarity?”

“We’ve had quality problems out of this team, seems like, forever. They don’t seem to care. They come to work, go through the motions. End of day, they head home. That’s why I was called in to manage this team.”

“So, what was different, after you explained the sequence, described the context for their work?” I probed.

“Nothing changed. We had the same incidence of quality re-works. Almost like shoddy work is part of the team culture.”

“So, what you are telling me is that culture trumps clear work instructions?”

Nobody Dies

“I don’t know why my team is behaving this way,” Riley complained. “I know we drive our people hard, and I know we expect a lot from them, but they knew that when they signed up for the job. We are a very intense organization.”

“How are they behaving?” I wanted to know.

“You can see them dragging into a meeting. Smiles are few and far between. It’s like they need a vacation really bad. Bordering on burn-out. I know we expect them to be responsive on their smart-phones, even after hours, but we are in the service business. We don’t know when our customers are going to call, or some project is going to go sideways.”

“So, in addition to working a normal day-shift, they are on-call after hours?”

Riley nodded. “Yes, but they get on-call pay, even if nothing happens. And we rotate that, so it’s not like it’s every day.”

“So, what is causing the fatigue,” I asked.

“I don’t know. It’s just that we are intense. If we relax, details get missed. And, missed details can turn into real problems. We have to keep our guard up.”

“And, if you keep your guard up and no details are missed, what happens?”

Riley had to stop and think. “Nothing special. Things go smooth, no one panics, but it’s not like we win the Super Bowl.”

“When your team does a really good job, it’s nothing special. So, who appreciates it, when they do a really good job?”

“No one really,” Riley admitted. “A really good job just means that no one is upset, mostly the customer.”

“Kind of like running a nuclear power plant,” I said. “If we do our job well, everyone gets electricity, the reactor doesn’t melt down and nobody dies.”

Clear as Mud

“Most of the time, your team members will do exactly what is expected of them, if they could just figure out, what that is,” I explained.  “When you observe underperformance, look for the cause.  It is usually in one of these five areas.”

  • Make the expectation (of output) clear.
  • Ensure the availability of required resources.
  • Validate the required skills and sufficient practice for the task.
  • Match the persons capability with the capability required for the task (measured in time span).
  • Ensure the person places a high value on the work (interest or passion for the work).
  • Ensure the person engages in reasonable behaviors required to complete the task.

“But I told my assistant that I needed the report ASAP,” Carolyn objected.  “When I went to find out the status, I found out the report had not even been started.”

“Let’s work through the list.  The expectations were clear to you, but were they clear to the team member?  What does ASAP mean?  You needed the report for the meeting on Friday, so ASAP could mean – as soon as possible before Friday.

“When I look at expectations, clarity of expectations, I think QQTR.  Quantity-Quality-Time-Resources.  If I miss any of these elements, then the expectation is not clear.”

  • What is the quantity of the output?
  • What is the quality standard (so I know what to count and what not to count)?
  • What is the time deadline, specifically, date and time?
  • What resources are available, or not available?

QQTR

Three Moving Parts

From the Ask Tom mailbag –

Question:
I hear you say that management is about setting context. I think I understand what that means, but I do NOT understand how to do it.

Response:
Culture is context. Setting context is the prime objective for every manager. Context is the environment in which work is done. Work is making decisions and solving problems. This is fundamental managerial work. Three moving parts –

  • Communicate the Vision. This is the future picture of a project, picture of a product in a package, the output from a service. This is what a clean carpet looks like.
  • Performance Standard. This is the what, by when. This is the objective in measurable terms. This is the goal – QQTR, quantity, quality, time (deadline or evaluation period), resources. The vision is full of excitement and enthusiasm, specifically defined by the performance standard.
  • Constraints. There are always constraints and guidelines. Budget is a constraint, access to resources is a constraint, time can be a constraint. These are the lines on the field. Safety issues are always a constraint. When the project is finished, you should go home with all your fingers and toes.

That’s it, then let the team loose to solve the problems and make the decisions within the context. Do not make this more complicated. It’s always about the fundamentals.

Fix Accountability

From the Ask Tom mailbag –

Question:
You seem to think that when the manager is held accountable for the output of the team, it’s a game-changer. You seem to think this one idea has a significant impact on morale.

Response:
Mindset drives behavior. This is a central premise to culture. What we believe, the way we see the world, drives behavior.

When a manager believes the team is accountable for their own output, it creates a punitive, blaming mindset on the part of the manager. I often hear the refrain from one manager to another, “Well, did you hold them accountable?”

And I have to ask, “Accountable for what? And just what managerial behavior is involved in holding them accountable?”

Is it a matter of reprimand, jumping up and down and screaming? Is it a matter of volume, frequency? If I told you once, I told you a thousand times. At that point, I am convinced that I am talking to a manager who has no children.

Managers who engage in this behavior have a direct negative impact on team morale. Response is predictably fight, flight, freeze or appease.

But, when the manager is accountable for the output of the team, everything changes. A manager accountable for the output of the team will –

  • Take extreme care in the selection of who? is assigned to the project.
  • Will take extreme care in the training of team members assigned to the project.
  • Will take extreme care in the work instructions for the project.
  • Will take care to monitor the progress of work on the project.
  • Will take care in the coaching of team members who may struggle in connection with the project.

Why? Because the manager is accountable for the output of the team. The attitude, the mindset, moves the manager from blaming behavior to caring behavior. If this becomes the mindset of all the managers, the entire organization’s culture changes. We don’t need sensitivity training, or communication seminars. We just need to fix accountability with the manager.

It’s What You Believe

“What do you mean, change the context?” Ruben asked.

“Jason is the smartest guy in the room, or, at least, he wants you to think that,” I nodded. “Right now, his attitude is counterproductive. So, change the context. You do some internal training, from time to time?”

“Yes, but that’s my job,” Ruben assured me.

“No, that’s what you believe. You believe that’s your job. What if you believed it was Jason’s job?”

“But, our internal training is usually about something new, not like we have a training manual, I have to figure how a process works and then determine the best way to teach it,” he protested.

“Sounds like you need the smartest guy in the room. What if you believed it was Jason’s job to teach? Change the context, behavior follows.”

Smart, So What?

“Is Jason smarter than everyone else in the room?” I asked.

“On some things, yes,” Ruben replied. “But, that’s not the point. Even if he does know something the team doesn’t know, he doesn’t have to shove it in their face. He needs to share, so everyone on the team can get better. That’s what teamwork is all about.”

“What do you believe about Jason?”

“Well, he is smart, but I believe his behavior is counterproductive. He makes his teammates feel bad,” Ruben pushed back.

“If he is so smart, do you think he could be an effective teacher?”

“Not with that attitude,” Ruben raised his eyebrows.

“In what context could that attitude be different,” I wanted to know.

“What do you mean?”

“Ruben. Look. Behavior does not happen in a vacuum. It happens in a context. Change the context, change the behavior. Could you change the context?”

Smartest Person

“He doesn’t fit the culture,” Ruben explained. “Jason’s okay, knows the technical side of the business, but he doesn’t fit the culture.”

“What do you mean, he doesn’t fit the culture?” I asked.

“He doesn’t fit the team,” Ruben replied. “Our teams work together, support each other, help each other. If someone asks Jason a question, he snaps the answer, he treats the other person like they are stupid. And, they just want to know the answer to the question.”

“What does Jason believe about the team?”

“What do you mean, believe about the team?” Ruben looked puzzled.

“You said this was a culture problem,” I nodded. “Culture is a set of beliefs that drive behavior, for better or worse. Ultimately, those behaviors are repeated and become an unwritten set of rules that guide the team in the way they work together. That’s culture. But, it all starts with what we believe, what you believe, as the manager, what Jason believes as a team member. If you want to change the behavior, you have to change the context. What we believe, what Jason believes, creates the context and drives his behavior. What does Jason believe about the team?”

Ruben looked up into his brain, “Jason believes he is smarter than anyone else on the team. Jason believes that he could do all the work better than anyone else on the team. Jason believes the other people on the team slow him down. When someone asks a question, it proves Jason is right, that he is the smartest person on the team and he wants everyone to know it.”

Does the Feeling Create the Structure?

“So, you want your team to feel like a family, at least an extended family?” I asked.

Andre was thoughtful. “You have heard the expression, familiarity breeds contempt? That is the behavior I see. Petty grievances. Subtle discord. You would think that, as a family, they would get along better and, in turn, be more productive. I want them to work together, collaborate, support each other, you know, real teamwork.”

“All, noble ideas. But, could there be a paradox? Could it be, that effective group collaboration, teamwork, does not stem from a feeling of family, but rather a clear recognition of individual team members, each with individual accountability in clearly defined working relationships? Could it be structure that creates the feeling, not the feeling that creates the structure?”

It’s Family Feeling

“The biggest problem I have,” Andre complained, “is getting my people to work together. I want them to be like a family. I want them to feel like they belong to a tribe, you know, an extended family.”

“Oh, really,” I looked surprised. “It is a noble feeling to impart to a group of people, to get them to feel like they are part of something bigger than themselves. So, what seems to be the problem in getting them to work together?”

“There always seems to be petty bickering between the personalities. It’s not overt passive-aggressive behavior, but the conversations that end up in my office are petty transgressions. Someone borrowed a stapler and didn’t return it. Someone took a snack out of the company refrigerator. Someone had a bright idea that the group ignored or made fun of. Someone got passed over on a new project. Someone got passed over for a promotion.”

“So, what do you think the problem is?” I asked.

“I think it’s the culture of the group,” Andre nodded.

“And, who sets the culture?” I prompted.

“Ultimately, I set the culture,” he thought out loud. “Funny, I want the group to feel like a family, an extended family, but I end up with sibling rivalry.”