Category Archives: Teams

Being a Manager, Different From Being a Supervisor

Joel was not shaking, but he was certainly shaken.

“I just don’t know,” he said. “Since I was promoted from being a supervisor to a manager, things are different. It is certainly not as easy as I thought, a bit out of control.”

“Being new to management is tough. No one prepared you for this, they just promoted you and expected you to figure it out,” I replied.

“And what if I don’t figure it out?” Joel asked.

“Oh, you will figure it out. But that is no insurance that you will succeed. There are a number of reasons that managers don’t make the grade. The first reason is commitment. This is harder than you thought it would be. Being a manager requires a passion for being a manager. Being a manager is a lot different than being a supervisor.”

“You are right about that. Being a supervisor was fun, fast paced, things were always changing and I had to respond quickly. Being a manager, things move slower. I have to think about things. And the worst part, most everything I do is accomplished through other people. Other people are hard to control. They don’t always show up the way I want them to.”

“So, you are facing the first challenge of a being a manager. Do you really want to be a manager? Do you have a passion for it? Just saying yes doesn’t make it so. Why do you have a passion for it?”

Power of Peers

Phillip’s team looked at each other, across the table, and for the first time saw something different. No more were they simply co-workers, but now interdependent members of a group whose success depended on those connections.

“No one succeeds by themselves,” I said. “At least for anything of significance. Sure you can think you are the Lone Ranger and prance around like you are someone important, but to achieve anything of real significance, you need a team. Each of you will, at some point, stumble, make a mistake, misjudge a situation. Each of you will, at some point, become discouraged, or become a Prima Dona, full of yourself.

“And when that happens, you will not recognize it in yourself, soon enough. You need each other to tell you those things, to make each of you better. Without each other, you will end up in ditch somewhere and no one will notice.”

Why Do You Need a Team?

Phillip’s team looked at each other, across the table, and for the first time saw something different. No more were they simply co-workers, but now interdependent members of a group whose success depended on those connections.

We were talking about changing habits.

“No one succeeds by themselves,” I said. “At least for anything of significance. Sure you can think you are the Lone Ranger and prance around like you are someone important, but to achieve anything of real significance, you need a team. Each of you will, at some point, stumble, make a mistake, misjudge a situation. Each of you will, at some point, become discouraged, or become a Prima Dona, full of yourself.

“And when that happens, you will not recognize it in yourself soon enough. You need each other to tell you those things, to make each of you better. Without each other, you will end up in ditch somewhere and no one will notice.”

How to Prevent Improvement on a Team

Ernesto was on a roll. Emily was now seated in a chair at the front of the class.

“Emily, you think there is a morale problem on the production line, but that’s not the problem. You know your team is not meeting the daily target, but you haven’t shared the numbers with them.  ‘A little short today, try to do better tomorrow.’  Bottom line, you are not telling the truth because you are afraid to hurt someone’s feelings. By not telling the whole truth, the accurate truth, you have made them incapable of improvement.”

Emily’s body language was retreating. Ernesto continued.

“And you have created co-dependents out of them. They are just fine not knowing what the target is. As long as they don’t know, they don’t have to perform to it.

“When you tell them they are short, they think it’s your problem not theirs. They are perfectly willing to continue this non-accountable relationship. No skin off their nose.”

The color in Emily’s face began to pale. I called a time out. The room was very still and quiet.

I jumped in.  “The problem we name is the problem we solve. That is why it is so important to name the problem correctly,” I said. “How will we name this problem?”

How Does Culture Retain the Team?

Ray was looking at his list. “So, I can count on losing this person. They already gave their notice. And I know they will continue to have contact with the other team members, so I know they will talk with each other.”

“Yes, they will talk. And they will talk about money. And money will appear to be the only reason to work at one company versus another. In what way can you, as a manager, put this in perspective for your team. In what way can you effectively communicate, effectively remind people about the other reasons people work, the other reasons people work here?”

Ray was shaking his head, then nodding his head. “So, it turns out that our team culture is really important after all.”

“Yes, when we sit and talk about job satisfaction, matching people’s talents with job requirements, matching people’s capability with the challenge level in the position, creating a trusting work environment, you think I am talking about being warm and fuzzy. The reason that stuff is important, the reason you have to pay attention, is to win this war against competitors. And you can’t win it with money.

“And if all your competitor has to offer is money, then you will make it very expensive for them. And in the end, their cost structure will be out of whack, and you will still win your customers. Culture eats the competition for breakfast.”
____
Amazon’s promotion on my new book Hiring Talent continues. Special pricing.

No Respect

“Tell me about that picture of the next step for you, as a manager.” I was talking to Jeanine.

“I can’t. I can’t do it until I have the authority to do it.” She was struggling with her new position in the company. She was handed a project to help solve some communication issues between several teams inside the company. “I just don’t have their respect. If I had the title, it would just be easier.”

“Jeanine, I can’t give you the title. You have to earn the title. I cannot make people have respect for you, it has to be earned.”

“But, if I don’t have the authority, how can I get their respect?”

I paused. “Jeanine, it is really very simple. All you have to do is bring value to the problem solving and decision making of those around you. Stimulate their thinking, help them move to the next level, show them how they can solve their own problems.

“People will always seek out others in the organization that bring value to their thinking and their work. If their manager is not bringing value to the party, the team member will always seek out the person that is.

“If you want respect, forget the title. Bring value to the problem solving and decision making of those around you. You will earn it.”

Didn’t Leave for Better Wages

The resignation letter stared at Adrian. His best team member, Eric, had just quit. Eric was employee of the year last December and just received a raise two months ago. He was in line to become lead technician in his department. What could be better? What else could Adrian, his manager, have done?

I inquired about the exit interview conducted by the HR coordinator. The form stated that Eric left for better wages.

Adrian was worried. Three years ago, Eric entered the company as an inexperienced recruit among a group of seasoned veterans. Over time, his personal productivity outpaced the entire team. In Eric’s absence, Adrian feared the overall output of the team would falter. Eric often carried the whole group.

I called Eric, already gainfully employed (at a lower wage) in another company. Happy with his decision, Eric shared his story. On a crew of six, Eric had consistently accounted for 50 percent of the output. The other team members were slackers riding on his coattails. I asked what Adrian could have done differently. The advice was quick and simple. “Cut the dead wood. Release the poorest performers and productivity would have increased, even with a reduced headcount.”

Adrian is left with the remnants of a mediocre team. But before he can heed the advice, he has to find another Eric.

Group Accountability?

“At first, this group dynamics stuff looked interesting, you know, everyone together under a team incentive bonus. It sounded exciting in the seminar, but in real life, this is painful,” Naomi explained. “The worst part, is we’re not getting any work done.”

“So, who is accountable?” I asked.

“I think everyone has to take a small part of the responsibility for the team not cooperating,” Naomi replied.

“No, I don’t mean who is responsible for the mess. I mean, who is accountable for the goal?” I insisted.

“The goal? We’re not even talking about the goal. We are just talking about cooperating better together, as a team.”

“Perhaps, that’s the problem,” I suggested. “You are spending so much time trying to cooperate as a group, that you forgot, we are trying to get some work done around here.

“Is it possible,” I continued, “that you have been misdirected to think more about shared fate and group dynamics than you have about your team. A team is not a group. A group may be bound together by shared fate, but a team is bound together by a goal. Stop thinking about group dynamics and start thinking about the goal. That’s why we are here in the first place.”

Pace and Quality Output of the Team

From the Ask Tom mailbag –

This is Part 2 of 5 in a series. This post is in response to a question by Herb Koplowitz, contributing editor to Global Organization Design Society. It is based on a discussion about Collins’ organizational model.

  • Level 5 – Level 5 Executive
  • Level 4 – Effective Leader
  • Level 3 – Competent Manager
  • Level 2 – Contributing Team Member
  • Level 1Highly Capable Individual

Question:
I didn’t read Collins’ levels as layers, but as personality fit to being a good manager. (He actually describes behaviors and then ascribes them to the manager as though ones manager has nothing to do with ones behavior.) Please explain how you see Collins’ levels as relating to Jaques’ strata. What is Stratum I about being a capable individual, what is Stratum II about being a contributing team member?

Response:
Yesterday, we looked at Collins’ Level 1. Today, Level 2.

Level 2 – Collins – Contributing Team Member. The central decisions in Stratum II roles (Requisite Organization), are also about pace and quality. But no longer, necessarily about my pace and my quality (individual output), but the output of the team. Calibrating Stratum II roles, I typically see job titles like supervisor, coordinator, project manager. This enlarged role requires a higher level of capability in solving problems and making decisions. It is the first layer in the organization where I hold the supervisor (coordinator, project manager) accountable for the output of the team. These roles require cumulative processing, adding many elements together in a coordinated recipe, with longest Time Span task assignments landing between 3-12 months.

Tomorrow, we will look at the decisions associated with Stratum III.

Practice

We were running north with a hint of a tailwind. The bike computer said we were running an easy 23 mph. Six cyclists in a pace line. The lead cyclist created the forward wind tunnel, expanding larger as each team member passed through. Even with a 5 mph tail, at 23, we still had 18 mph of head wind. The efficiency of the pace line allowed the team to run quicker than a single cyclist alone. The leader on the nose can put maximum effort into the wind, with the rest of the pack safely tucked in behind. The pace line rotates its leader to keep fresh legs up front.

In the dark, the approaching car was easy to see, its headlights piercing out from a hidden driveway. The halogen beams continued to brighten the road in front. We could see the car, the car couldn’t see us.

“Car right! Car right!” echoed off the passing buildings. The pace line, which had been a steady snake for the past 7 minutes suddenly began to bunch, alternating riders cheated left and right. “Slowing!” yelled the lead. Each rider focused simultaneously on bike separation, an escape path and the intersecting car. What would happen next? The riders were bunched, speed had dropped to 18, the efficient wind tunnel disappeared, each bike now flaring its own path into the resistant air.

The headlights stopped. The lead rider made eye contact with the driver and held up a stopping hand. The driver clicked to high beam and back to low.

The lead rider came out of his saddle and pressed hard into the wind, pushing back to 20. The second rider came back from the left and tucked in behind the lead 24 inches off the wheel. Each successive rider adjusted position, pressing into the forming tunnel.

The last rider hooks on and the lead hammers back to 23. In the short space of 8 seconds, the pace line approached danger, lost its effectiveness, then regrouped into a highly interdependent efficient team.

How does your team run its pace line? When circumstances throw it off course, how quickly does it react to protect itself? How does your team re-establish its operating groove? What is communication like? How quickly does the wind tunnel return? Does your team practice this drill?