Category Archives: Teams

One Crab in the Basket

“All my team wants to do is complain. I know things aren’t perfect, but we still have to get the work done. They shoot down every idea I have,” Chet shook his head.

“Have you ever been crabbing?” I asked. “Crabbing, you know, where you trap crabs, pull them out of the water and throw them into a basket?”

Chet looked at me a bit sideways. “What’s that got to do with my team?”

“Here’s the thing, Chet. If you only have one crab in the basket, you have to really pay attention, because the crab will crawl out of that basket lickety-split. The trick is to catch more crabs quickly. With a bunch of crabs, when one starts to crawl out, the other crabs attach to the legs and pull him back into the basket. You would think they would all try to crawl out, but that’s not what happens. Sometimes, teams are the same way.

“Before you describe a possible solution, go around the table and have each team member describe the major benefits if we are successful at solving the problem. If you can get them to focus on the benefits, they are less likely to focus on the crab (you) trying to crawl out of the basket.”

Huddle Meeting, Most Important Meal of the Day

“What’s the major benefit of a huddle meeting first thing in the morning?” I asked. The team looked around at each other to see who might jump in first.

“To share the plan for the day,” said Shirley.

“To make certain assignments,” chimed in Fernando.

“To schedule lunch,” smiled Paul. Everybody stifled a brief laugh.

“Lunch is important,” I said. “Now, most of you are too young to remember Woody Allen, but he said that 80 per cent of success is just showing up. One of the major benefits of a huddle meeting first thing in the morning is to firmly establish the starting point for the team.

“Lots of time can get wasted as people trickle in, fritter around, sharpen pencils (who uses pencils anymore?). But, if you have eight people on your team and you lose fifteen minutes, that’s two hours of production.

“A huddle meeting can start the day. Sharp and crisp. Five minutes. Let’s go. Hit it hard.”

Need a Heads Up

Frieda was frustrated. “I sit in a department managers meeting and get called on the carpet for an assignment that I knew nothing about. One of the other managers pulled an end-around and took a project directly to one of my staff members. I am not a mind-reader, how am I supposed to follow-up on a project I know nothing about. I told everyone in the staff meeting that if they want work done in my department, they have to work through me.” Frieda stopped. Calmed a bit. “That didn’t go over real well. Now everyone thinks I am a prima donna.”

“Do you think the other department managers are being malicious?” I asked.

“No, things are just busy. I think they just wanted to get their project done.”

“So, in busy companies, this kind of thing happens. We simply need to get work done and sometimes you may be out of pocket and one of your team members becomes convenient for the project. Don’t take it personally. The question for you is –How can you, as the manager, find out about these projects so you can schedule them appropriately?

“Do you have a weekly staff meeting in your department?”

“Of course, that is when we sit down and take a look at all the projects in-house, get a status report and talk about production issues.” Frieda was firm in her response.

“So, I want you to add an agenda item. –What are the projects that have been assigned that we don’t know about? This is actually pretty easy. These would be projects that your team is working on that are not on the project list. The purpose is to capture the project information so your team can respond appropriately. You get back in control and your fellow department managers see you as cooperative and helpful. AND, with your fellow managers, you can ask for an email heads up about the project, so you can make sure appropriate resources are deployed and that the due date has been effectively communicated and on your master schedule.”

Special Practice

“You did some training last year, tell me about it.”

“Well, first, we invested a decent budget. This was a new process we were working on. We spent a lot of time looking at different programs. We put together a decent PowerPoint, even hired an outside trainer.” Travis stopped.

“And?” I said.

“And, after all was said and done, a lot more was said than done.” Travis chuckled. “I heard that in a seminar once. But maybe it’s true. After the training, some of the people worked the new way, but some didn’t. Over time, the whole process was abandoned. ”

“You know your program really didn’t have a chance. It was missing something critical,” I said.

“I know, you are going to say positive reinforcement, but we all talked it up and everyone got a certificate when the training was over,” Travis defended.

“That’s all very nice, but I am not talking about being nice. I am talking about being effective. In the training you demonstrated a new process. This new process required a new skill, a new behavior.

“Travis, I can show you how to throw a ball, but if you want to get good at it what do you have to do?”

Travis looked puzzled, “Practice?” he said.

I nodded. “Very special practice.”

Avoid the Hazard

The paceline moved north, into a headwind, pulling 18mph. “Walker up!” The shout came from the lead cyclist on the nose. He pulled his right hand off the handlebars, arm straight out, pointing to the pedestrian in the bike lane. A second later, his right hand dropped, waved the pace line left, out of the bike lane into the active traffic lane. Though the group may not have seen the walker, each cyclist in the line knew about the hazard and knew to follow the lead bike into the active traffic lane to avoid it.

Intentional, agreed-upon communication. It was simple, efficient and effective. As the paceline continued north, there were other hazards to avoid, potholes, a tree branch in the road, narrowing traffic lanes, overtaking cars. Through a series of hand signals and audible shouts, the group made its way safely through urban traffic.

How does your team communicate in its daily routine? Do they have simple, efficient protocols to warn of impending hazards, delays, material shortages? Do they have agreed-upon signals to provide each other with feedback?

Chances are good that prior to a delay, prior to a material shortage, prior to a change in schedule, somebody knew. Someone could have warned the group and the group could have acted according to an agreed-upon protocol.

Get your team together and play the “what if” game. Find out what problems occur often and how they are best solved. Then create the “signal.”

“Walker up!”
____
We are putting the finishing touches on Hiring Talent 2019. Pre-registration is now open.

Practice in the Dark

It sounded like a beer cap hit a marble floor, then like a rifle shot. 100 pounds of air pressure escaped in a nanosecond. In the dark, before dawn, the sound ricocheted off the high condo towers, pierced the early morning silence. Bike number three had a flat.

The undercurrent of grumbling was short-lived. The back of the pace line maneuvered around as bike number three dismounted and hopped up the curb onto the sidewalk under a street light. Within ten seconds, the entire pace line assembled around this carcass of carbon fiber and limp rubber tubing called a bicycle. Two headlights brightened up the rear gear cluster. One held up the bike, another spun the crank moving the chain down to the highest gear. Another popped the brake, grabbed the quick release and jerked the axle free. Two bikers set up a perimeter to ward off errant traffic. Someone had already unfolded a fresh tube and spiked a CO2 cartridge. The old tube was out and careful fingers searched the inside of the tire for a shard of metal, a piece of glass.

Now, the rider of bike number three was doing very little through this entire process. He tried to look in control, but truth be told, his bike was being fixed without him. It was a smooth process, not a lot of talking, mostly joking going on. Seven minutes later, with a small tailwind, the pace line was back at 24 mph, snaking their way down the quiet city street.

When your team encounters a problem, what do they look like? When a team member runs up against an immovable obstacle, how quickly does the rest of the team pitch in? When the rest of the team assembles, how cooperative do they work, how synchronous are their efforts? How often does your team practice having flats in the dark and fixing them by flashlight?

Conflict Management

“I am sorry, but I have to disagree.” Silence engulfed the room, eyes got wide. 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 being able to manage the conflict, more a matter of managing agreement. 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 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 manage agreement, to 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 a 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, the issue on the table is likely to be important.

Difference Between Winning and Losing

In any sport, there is the game and there are the players. For both sides of the contest, the rules are the same, the playing pitch is the same. The two primary variables are techniques (methods, processes) and people. Methods and processes are important, but you don’t have to watch a sporting event for very long to see that the discussion is focused on the people, the players, the talent.

Most sporting teams commit considerable budget and effort in recruiting. What is the major difference between a winning team and a losing team? It is rarely technique. It’s all about the people.

The most important part of building any successful company is building the team. Often, we see team members as interchangeable commodities, always replaceable. What if that weren’t true. What if team members weren’t replaceable, interchangeable commodities? What would change about our hiring practices as we build this team?

Turn the Tables

From the Ask Tom mailbag:

Question:

I am at wits end. I have a weekly management meeting, but it seems I do all the talking, especially when it comes to accountability. And when it comes to accountability, all the ears in the room go deaf. Whenever there is underperformance, it is like the team cowers under the table until the shouting is over. I am tired of shouting. Besides, it doesn’t seem to do any good.

Response:

Most Managers are not aware of and do not leverage team accountability. Managers assume the role of the bad guy and essentially let the team off the hook when it comes to holding each other accountable for performance.

Turn the tables. In your next meeting, when a team member reports non-performance or underperformance, stop the agenda. Ask each team member to take a piece of paper and write down how this underperformance is impacting their part of the project. Go around the table and ask each person to make a statement. Then ask the team to create an expectation of how the underperformance should be corrected. Go around the table again. Finally, ask the underperformer to respond to the team and make a public commitment to action.

Team accountability is a very powerful dynamic.

State of Panic

“Tell me how it sounds, to focus the mental state of the group on the real issue,” I invited.

Darla took a deep breath. “I have been thinking,” she started.

“Good, using I-statements is good.”

She started again. “It seems to me that we are not making progress on the project we started last week. I expected to see some changes in our process already, measuring some of the samples coming off the line. AND, I see the same team doing the same thing we have always done. No sampling, no inspection. I am curious.”

“Good, I like I am curious.”

“I am curious about the way you feel about the project. We are all in the room. Everyone will have a chance to participate. I would like each of you to speak for yourself. Who would like to start?”

“I like it,” I said.

“But, what if no one says anything. What do I do then?” Darla was visibly off center.

“You put the issue on the table. Your team will now go into a state of panic. You have moved the mental state of the team from collusion behind your back to a state of panic. Every manager before you has always rescued them from this panic. Believe me, your team has specific feelings about this project. They have verbalized those feelings at the water cooler. They pair up at lunch and talk about the way they feel about the project. You are drawing those same conversations, that they have already practiced, into the team meeting, so the team can deal with them. Your primary goal at this point is to outlast the panic.”