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

Idea Connection

“Why can’t I get more participation in my meetings?” Janet asked.

I nodded. “Some say that it is the fear of disagreeing with the boss, but I find it is a more universal fear. It is the fear of floating an idea that carries the possibility of rejection.”

I let that sink in a moment. “As a Manager, if you want to promote deeper, richer, more truthful conversations in your team, try this. As ideas are contributed, create a follow-up comment that expands the idea, creates an insight to that idea or connects the idea to a higher purpose, goal or solution. Breathe life into every contribution.”

Two weeks later, I overheard one of Janet’s team members talking at the water cooler. “Our meetings have really gotten better. Janet makes all of our ideas sound so smart.”

Ideas really are smart when you can connect them to a purpose, a goal or a solution.

Meetings De-Railed

“I’m tired of my team, whining and complaining in meetings. Then, they look at me, like I have to come up with the solution,” Janet shook her head.

“How are you going to fix that?” I asked.

“Not sure, every meeting seems to get de-railed.”

“Then why don’t you de-rail the meeting. Before the whining begins, re-state the purpose for the meeting (the problem to be solved), and ask everyone to write down two possible solutions. Only give them 45 seconds, they don’t need a long time.

This accomplishes two things:
1. It points everyone in the direction of a solution before the conversation has a chance to get de-railed.
2. It communicates that it is the responsibility of every team member to contribute in the solving of a problem.”

Never Run a Press Before

Cindy’s assignment was simple. As a successful supervisor in another division, she was transferred to a line unit that was having trouble keeping up. After her first meeting, she wasn’t so sure she was up to the task.

From the back of the room, “So, tell us about your background. Have you ever run one of these presses before?”

She admitted that she had not. “So, how do you expect to be our supervisor when you don’t know the first thing about how we do the job?” She had never been challenged so directly. Worse, it was a perfectly valid question.

Now Cindy was in my office. “Here is the central issue,” I asked, “how can you bring value to their problem solving and decision making?”

“What do you mean?”

“You don’t know how to run the press, but does that really matter? How do you bring value to their problem solving and decision making? How do they know when they are doing a good job? How do they know when they are doing a poor job?”

“Funny, I know the ops manager was complaining that they did not meet the production quota last month. But those numbers were never broken down on a daily basis so the line never had a clue whether they were ahead or behind. The last two days of the month, somebody came out and yelled at them to pick up the pace, but it was too little, too late.”

“So, you can bring value to the work by giving the floor feedback on daily production runs, perhaps accelerating things a bit, but avoiding a hysterical crunch at the end of the month.”

One month later, Cindy’s crew was ahead by 150 units, yet had worked no overtime, even taken the press down for a half day of preventive maintenance. Every morning, Cindy had a two minute huddle meeting and posted the day’s production goal. At ten and two she posted updates with a final count at 3:30 when the line shut down. Though she had never touched the press, she was bringing value to the problem solving and decision making of her production crew. The skills to be a successful supervisor are quite different than the technical skills of the crew.

The Porpoise

“Purpose?” Phillip squinted.

“Purpose,” I repeated. “The first step to having important meetings is to be crystal clear on its purpose. We tell Project Managers they need to have meetings, and then we wonder why their meetings fall apart. Bottom line is that most companies don’t train supervisors and managers on how to conduct an effective meeting. They just expect it to happen, like magic.”

“So we need to start with purpose?” asked Phillip.

“Everything starts with purpose. Meetings run amuck when there is no purpose, or where people attending have different purposes. Until we get those purposes out on the table, our meeting is going to meander aimlessly.”

“How do we do that? Send an email out before the meeting?” pondered Phillip.

“Yes, it’s as simple as that. But think about it. How many meetings did you attend during the past month where there was no stated purpose and no agenda?”

Phillip didn’t have to think long. “You know, I don’t think I went to a single meeting last month where there was a published agenda, much less, a stated purpose.”

“Now, I know some things managed to get done in those meetings, but they could have been much more effective. Do that one simple thing, and teach your PMs to do the same and you will see an improvement.”

Critical, But Never Taught

Phillip didn’t have to be briefed on the difference between meetings that were important and meetings that were a waste of time.

At the same time, he was uncomfortable. “You know, we do a pretty good job of training people on the technical stuff we do, how we make things, how we deliver our services, but we don’t train on how to run a meeting.”

“I know. Interesting, isn’t it? One of the most important things a supervisor does and your company doesn’t spend any time teaching it.”

“Okay, I’ll bite. What do we need to do first?” asked Phillip.

Third Leg on the Stool

“More?” Phillip asked.

“Phillip, one of the biggest mistakes a company makes when it hires people, is underestimating what is required for the person to be effective in the position. The role of a Project Manager requires a new skill set, a skill set that most companies never train.”

“We talked about schedules and checklists, but you said there was another tool, a third leg.”

I nodded. “Perhaps the most important tool. Meetings. Most PMs know they need to have meetings, but they just gut their way through. Nobody likes their meetings. The team would skip them if they could. Participation by team members hardly exists.

“Think what a meeting could be. It makes communication consistent because everyone hears the same thing. It provides the opportunity for interactive participation and questions. It encourages participation and promotes buy-in. It can be used as an accountability tool.

“But effective meetings rarely happen, because most managers don’t know how.” Phillip’s turn to nod. It began to sink in. Running the job is completely different than doing the job.

S-II Power Tool

Phillip was all ears. He slowly understood that the role of the supervisor was different. While the role of the crew member was to do the work, the role of the supervisor was to make sure the work got done. It required a completely different set of skills. It had nothing to do with hammers, saws or heavy equipment. It had to do with scheduling people and materials. It had to do with making sure the work was complete and finished on time.

“You said we need to teach our PMs how to put a schedule together?” Phillip asked.

“Yes, and a schedule is only one of the tools of the supervisor. Another is a checklist.”

“You mean, like the punch list we use at the end of the job to wrap up unfinished details?”

“Yes,” I nodded. “Why use a checklist only at the end of the job. Checklists can be useful through the entire project. There are a hundred things that need follow-up and no one can keep all that in their head. In fact, after a few jobs, a master checklist can be created for different parts of the project, like a template that can be used over and over.”

“And we should teach this to our supervisors?” Phillip was slowly getting on board.

“Yep. I know it comes second nature to you, but not to your junior Project Managers.” I stopped. Phillip had enough for today. “Tomorrow, I will come by and we can pick up the next Project Management tool.”

The Schedule and Reality

Phillip stared at me. His blood pressure was up, though he appeared calm, but not like a deer in the headlights.

“So, we should teach our Project Managers to schedule?” he asked, knowing the answer was yes.

“Look. Phillip. Think about this. What is the most frequent problem a Project Manager has to deal with?”

Phillip didn’t hesitate. “The contractor calls up and wants to know how come something on the job site isn’t happening the way he expected it to.”

“And what happens then?”

“Well, the PM starts scrambling. He jumps on his radio to find out what happened to the crew or the materials or the equipment. It can get a little chaotic.”

“Why doesn’t the PM immediately go to the schedule to find out what is happening?”

“The schedule?” Phillip almost started laughing. “His schedule won’t tell him anything.”

I stopped, waited for ten long seconds. “And why won’t the schedule tell him what he needs to know.”

It was Phillip’s turn to wait. He was trying to craft a response, but the only thing that came out was the truth. “I guess we don’t take schedules seriously enough to train our PMs on how to create them and use them.”

“So, Phillip. Yes, you need to train them on how to put a schedule together.” Phillip nodded slowly in agreement. “And that’s not all. There’s more.”

It’s a Different Level of Work

As Phillip simmered, he finally blurted out, “But they should know how to schedule. How hard is that?”

“I don’t know, Phillip. How complicated are your scheduling logistics?” I asked.

“It’s just getting the materials and the people scheduled. How hard could it be.” Phillip was firm.

“What is the biggest problem they face in scheduling?”

Phillip thought for a minute, hoping to tell me there were never problems, but he knew better. “I guess the biggest problem is coordinating with the other subs on the job, to make sure their work is finished and the project is ready for the work we do. Since the subs don’t work for us, coordinating is sometimes difficult.”

“So, how do you train your PMs to deal with that?”

“Train ’em. They’re just supposed to know that they have to go check.” It was not a good answer and Phillip began to backpedal.

I pressed. “On the job, do materials ever get back-ordered? Does a crew member ever call in sick or a whole crew get reassigned to an emergency? Does the contractor ever change something without a change order? Does a piece of heavy equipment get delayed on another project and not show up? Does a dumpster load sometimes not get switched out in time. Does a code inspector sometimes not show up?

“Tell me, Phillip. How do you train your Project Managers to create and maintain schedules?”

Phillip hesitated. He knew any response would just sound like an excuse.

“Phillip, here is the critical factor. Actually doing the work is completely different from making sure the work gets done. It’s a different role in the company. It has its own skill set. You didn’t hire for it, you didn’t train for it, and, right now, it’s killing you.”