Category Archives: Teams

What Else Can You Delegate?

It was a big difference in Nathan’s meeting. Instead of barking out the quota numbers for daily production, he had assigned that task to Rachel. The team had responded.

“What else could you delegate during the meeting?” I asked.

“Well, when Rachel announced the quota number, the first questions were about raw materials and machine setups. So, I was thinking about asking Edward to get with Rachel before the meeting so he could report on the status of raw materials. And I was thinking about Billy, he is our line mechanic, to get with Rachel to plan the machine setups for the day. So he could report those in the meeting.”

“Sounds like an agenda is coming together for this daily meeting and you are having other people become responsible for each line item?”

Nathan laughed. “You know, I thought, as the manager, that I had to do all the talking in the meeting. I am beginning to think, maybe, I should just call the meeting to order and sit at the back of the room.”

They Began to Ask Questions

“So, what was the big difference?” I asked. Nathan was getting pushback in his production meeting whenever he went over the schedule. Especially when he talked about the daily quota number for production.

“I assigned Rachel to announce the number,” Nathan replied. “It was the funniest thing. When I talk about production, people grouse and mumble. When Rachel described the quota number, people began to ask questions. Did we have enough materials on the floor and how many different setups would be required on the machine. It was like they wanted to do the work.”

“So, what did you learn?” I asked.

“I learned that I don’t have to do all the talking. I can delegate out important stuff. Instead of me telling people what to do, when they become involved, they actually step up and participate.”

Delegate It Out

“But, I still feel there is some tension in the meeting, especially when I start talking about quotas for the day and some of the production problems that need to be corrected,” Nathan explained.

“So, delegate it out,” I said.

“What do you mean?”

“Look, Nathan. Where do the quota numbers come from?”

“Well, there is a Production Release report that gets posted at 5:00pm for the next day. That is the number that I go over in my morning meeting.”

“So, it is just a number that comes off of a report? And, you are the bad guy because you know the number and report it in the meeting?”

“Exactly,” nodded Nathan. “I feel like a tyrant, when it is just my job.”

“So, assign the Quota Number report to another team member. During your meeting, ask them to talk about the number from the Production Release report.” I could see Nathan pondering my proposal. “Who could you assign that to?” I asked.

“I could assign that to Rachel,” Nathan replied. I could see a sense of relief wash over his face.

“Let me know the difference in your meeting tomorrow.”

State of Mind of the Group

“It’s the difference between work and non-work,” I said. “Both work and non-work are states of mind. Non-work is an unconscious state of mind. Work is a conscious state of mind. Non-work just happens on its own with no particular direction. Work only happens when there is a purpose.”

Nathan and I had been discussing a simple start to a meeting where he asked each team member to contribute a piece of good news to start the meeting.

“So, I am connecting this exercise at the beginning of the meeting with a state of mind?” Nathan asked.

“Absolutely,” I responded. “Thoughts drive behavior. And if your thoughts connect to a purpose, then you are more likely to engage in work. If your thoughts are not connected to a purpose, then your behavior is likely to be unconscious and non-productive. How you think is everything.”

Sidelined by the Team

Nathan, a new manager, had been sidelined by his team. “What happened?” I asked.

“I don’t know. I was giving orders for the day and a couple of the guys wandered off and before you know it, I was in the room by myself.”

“What do you think happened?” I continued.

“Well, Troy had been on my case since I was first made manager. Seems he thought he was in line for the job. But the company picked me.”

“So, now, what do you think your challenge is?”

Nathan was quiet, then finally spoke, “Somehow, I have to get them to trust me.”

“Nathan, it’s a long road, to get your team to trust you, even if they have known you for a long time. Where do you think you will start?”

Nathan was still quiet. I poked my head out the door. His team hadn’t abandoned him. They were all at their workstations, doing their work, but it didn’t seem like Nathan was having his way.

“Nathan, I think your team will work okay for the rest of the day. The schedules that were posted yesterday haven’t changed that much. Let’s take a hike down to the coffee shop and talk about a new strategy. It’s tough being the new boss.”

Managing Conflict?

This meeting was different. Business as usual was shattered like crystal on a marble floor. The usual comfort level was suddenly traded for a stomach flipping tension-filled discussion.

“I am sorry, but I have to disagree.” The silence dropped, eyes got wide, butts in chairs started shifting. Someone cleared their throat. This team was at a cross roads. The next few minutes would determine whether it engaged in productive work or disengaged to avoid the conflict currently on the table.

This is not a question of managing conflict, more a matter of managing agreement. In fact, the more the group tries to manage the conflict, the more likely the agreement will be coerced and compromised with the real issues suppressed, perhaps even undiscussable.

Conversely, if the group engaged in a process to manage agreement, the conflict might be heard, even encouraged, thoroughly discussed. Opposing viewpoints might be charted out and debated. Expectations might be described at both maximum success and dismal failure. Indicators could be created with contingency plans for positive and negative scenarios.

Does your team manage conflict to make sure discussions are comfortable and efficient?

OR…

Does your team encourage spirited discussion of both sides of an issue? When things get uncomfortable, can your team live through the stress of conflict to arrive at a well argued decision?

When I look around the room and see that each person is comfortably sitting, I can bet the issue on the table is of little importance. But, if I see stomachs tied in knots, this issue on the table is likely to be important.

Cross Department Committees

From the Ask Tom mailbag –

Question:
Many times when there is an issue that affects more than one department in the company, we assign committees involving members from each department to solve them. While this seems nice from a cultural standpoint, it seems strange that we would ask people in an S-II or S-III role, to solve issues that span multiple departments, typically an S-IV function. I recently experienced this myself where I established a committee, set a clear direction (I thought), and checked in occasionally. The end result was I now had a group who had reached a consensus, but it was the wrong one! We are still able to move forward and correct it slowly, but it feels like we wasted effort. What’s the right answer to this? Be more involved? Assign another committee leader with level 4 capabilities? Provide better direction? Make a larger committee?

Response:
Quick review on general accountabilities at levels of work.

  • S-I – Production
  • S-II – Making sure production gets done, coordination and implementation.
  • S-III – System work, designing, creating, monitoring and improving a single serial system (critical path)
  • S-IV – Multi-system integration

So, your intuition is correct that, where multiple departments are involved with either output or impact, department integration is appropriate.

Your question – Be more involved? Assign someone with S-IV capability? Provide better direction?
Answer – Yes.

In any managerial role, with team members one level of work below, the manager cannot simply call the meeting and then not show up. Undirected, the team will make the decision or solve the problem at their level of context. Each level of work understands its decisions and problems from their level of context. That context is measured in timespan.

Problems or decisions involving multiple departments generally require looking at longer timespan outputs, more correctly, longer timespan throughputs. A single department is usually heads-down, internally focused on efficient output. Multiple department throughput typically looks at two things. Does the efficient output of one department provide the correct input for the next department as work moves sideways through the organization?

  • Does the output of marketing (leads) provide the correct input for sales?
  • Does the output of sales include all the data necessary agreements for proper project management?
  • Does the output of project management provide all the accurate data necessary for operations?
  • Does the output of operations provide all the necessary checkpoints for quality control?

Multiple department integration also requires a look at the output capacity of each department as they sit next to their neighbor department. Is is possible for sales to sell so many contracts that it outstrips the capacity of operations to produce? A lower timespan focus might say we just need to communicate better. A longer timespan focus (throughput) will realize that no communication solution will fix a capacity issue.

So, yes, the manager has to be more involved, include another team member at S-IV, provide better direction on the requirements of any solution. A larger committee might actually be counter-productive if it contains team members at the wrong level of the problem. I offer these same guidelines as those of a couple of days ago.

  • What is the problem?
  • What is the cause of the problem?
  • What are the alternative solutions?
  • What is the best solution?
  • How will we test the solution to make sure it solves the problem?

They Act Like Zombies

From the Ask Tom mailbag –

Question:
Working with my team, trying to get them to solve a problem. But, I think my solution is better than anything they might come up with. And, I don’t have time to have a meeting, and besides, I don’t think my team wants to be creative. Sometimes they act like dolts. I can solve problems like this pretty easy. I have been in the business for six years. I have the experience. But when I tell them what to do, they’re like zombies from the Night of the Living Dead. Some of them walk around like they still don’t know what to do, even though I gave them the solution.

Response:
What are you training them to do? Are you training them to solve a problem as a team, or are you training them to act like “dolts.”

Whenever you solve a problem that the team should solve, you cripple the team from solving future problems. And, if your solution fails, who carries the burden?

As a manager, you have to figure out your purpose. If your purpose is simply to have a problem solved, then solve the problem. You don’t have to be a manager to solve the problem.

If your purpose is to train the team to solve a problem, then understand, you are now a manager, and everything you do sets a precedent for what comes after. Try this simple method of questions for the team.

  • What is the problem?
  • What is the cause of the problem?
  • What are the alternative solutions?
  • What is the best solution?
  • How will we test the solution to make sure it solves the problem?

It’s Personal

Carly met me in the conference room that overlooked the plant floor. She was a new supervisor running a parallel line to another crew. On the job for three weeks, she had been having difficulty with her crew’s productivity next to the other crew.

“It’s amazing to me,” she said. “We start ten minutes earlier than the other line. In fact, they just stand around talking for the first ten minutes of their shift. But, within half an hour, they catch up and then hammer us the rest of the day.”

“Interesting,” I said. “Let’s get Jarrod up here and find out what he is doing differently.”

As Jarrod joined us, he talked about a number of things, but he saved the best for last. “One thing, I know you have overlooked, is our team huddle at the beginning of the shift. It is our team check-in. I have found the most important obstacle to productivity on a line like this is the personal stuff that’s going on. It has nothing to do with work, but has a bigger impact than anything else. It makes a difference in hustle, covering someone’s back, taking an extra measure for safety. That daily check-in helps my team to work together. It’s only five minutes, but makes all the difference.”

Practiced, Grooved Behavior

“But, I thought my team was competent. They have worked under this kind of pressure, solved these kinds of problems before,” Marion reported.

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

“I know we spent a lot of time working from home over the past couple of months. And, now we are back in the office most of the time. Things are different. People stick to their cubicles, practice social distance. It’s like Men-in-Black erased the memories of how well they used to work together.”

“What’s missing now, that was there before?”

“They seem out of practice. It’s not like they are screwing everything up, but they used to be tight. Now, every hiccup creates a little team stumble.”

“Marion, you say they are out of practice. What have they been practicing?”

She chuckled. “They have practiced being apart, practiced being disconnected, working alone, not talking to each other.”

“We are always in practice,” I said. “Just sometimes we practice stuff that’s counter-productive to where we want to go. We get good at what we practice. If we practice being lazy, we get good at being lazy. If we practice enough, it becomes a habit. Don’t practice things you don’t want to get good at.”