Tag Archives: productivity

Toxicity

“You may think that your company stands for integrity, honesty, that it holds trust as an abiding theme?” Pablo raised an eyebrow.

“Yes,” I nodded. “I would agree on all those things.”

“I don’t think so,” Pablo countered. “You don’t stand for those high ideals. You stand for what you tolerate.”

I let that sink in a moment. “You are right. It is often easy to spot a toxic employee. Their toxicity sticks out like a sore thumb. But, we are very slow to react. We fret about the confrontation, the optics, the perceived impact on our culture. And, so we tolerate it, if only for just a little bit longer.”

“And, what happens to the company in that interim? What happens to surrounding team members? What is the impact on the pace and quality of work? What happens to the frequency and cost of re-work? Not just an emotional drain, but hard costs.”

Never Enough Time To Plan

“I don’t understand,” Calvin shook his head. “It was only a two week project. We are almost finished. Why do you think we need a plan, now? All we have to do is get the last of the barcode labels on the product boxes we missed.”

“You tell me,” I said. “How did the barcode project turn out so far?”

“Well, we’re still working on it. It’s a lot of boxes, and we missed some as we were going through the inventory.”

“How did you find that out?”

“Well, my boss showed up late in the afternoon and started to look around. It’s amazing how he can always find the stuff we missed. It’s almost like he went straight to it. Boom. In five minutes he found 36 product bins that we missed completely. Now he is making us go back through and check every single item.”

“What is that doing to your completion schedule?” Calvin, just looked at me. No answer.

“So, there wasn’t enough time to plan this thing up front?” I said. “There wasn’t enough time to do it right, but there is enough time, now, to do it twice?

“Calvin, I know it seems you are really behind the 8-ball, but I want you to stop. Right now. Stop, and get your team around. I want you to draw out each of the steps with your team on a big piece of butcher paper. I want you to plan how you are going to get all the labels on and then plan how you are going to check for accuracy. You should be able to get that plan done in a half an hour. That half hour will end up saving you eight hours on the back end, and you shouldn’t have to do it a third time.

“Remember, doing it a third time is always an option.”

All in the Way You Think

Management is about leverage.

Most people work on a ratio of 1:1. They work for an hour and they get one hour’s productivity. Managers have to get far more leverage from their time than 1:1. A manager cannot afford to get only one hour’s productivity for one hour worked.

How can you get two hours productivity from one hour worked? It’s a fair question.

The obvious answer is delegation. But the challenge continues. How can you get three hours productivity from one hour worked?

But here’s the real challenge – How can you get 50 hours productivity from one hour worked?
Chicken feed. How can you get 100 hours productivity from one hour worked, every month, month in and month out?

Most managers view delegation from the perspective of time management. Dumping. If you dump enough stuff, you can get five, six, even ten hours of time back, but you are still working on a 1:1 ratio.

Only if you look at delegation as development, do you begin to understand true leverage. One hour can turn into 100 hours productivity. How would you like to work for 5 hours and gain 500 hours productivity over the next 30 days? It’s all in the way you think. So, how do you think?

What’s the Benchmark?

“So, what do you think?” asked Lenny. “How do you think my team is doing?”

“I don’t know. How do you measure how you are doing?” I replied.

“That’s the thing. We aren’t sure what to measure against. We got some studies of companies that are sort of like us, but the benchmarks they use seem so different. They just don’t make sense.”

“Two things,” I said. “Pick what you think is important. Start measuring now.”

“But, what do we measure against? How do we know if we are doing okay or not?”

“Measure against yourself. So many companies chase each other’s tail around and end up back where they started. Figure out what is important to your customer and measure that. That’s all your customer cares about. What else matters? Measure the second day against the first day. Measure the third day against the second day. Pretty soon, you will see a trend. Before you know it, you will have one year’s worth of data. Start measuring now.”

Just a Little Bit of Truth

One inch higher on the left and the magnetic white board would be level. It had been the subject of much speculation on the shop floor that morning. There were several theories floating around, but no one had correctly guessed what the boss had in mind.

While the shop floor was organized according to a logical work flow, production had gotten further and further behind. The right jobs were late, the wrong jobs were early.

Last Friday, the boss had taken an informal poll. “George,” he said, “tell me, how do you know if we are ahead of schedule or behind schedule?” It was a fair question, but one that George did not know how to answer. “Well, boss, I guess if we were behind schedule, someone would come out here and tell us.”

It was an interesting response, seeing as how the floor was running only 28% on-time delivery. The boss walked over to the foreman’s office, leaned in and asked, “Say, John, when we are behind schedule, which I know is most of the time, do we ever tell anyone out on the shop floor?”

“Oh, no, boss, if we did that, they might get discouraged and quit.” Another interesting response.

You see, the boss had just heard of an experiment in a plant where they simply published production numbers on a daily basis to everyone in the plant. Every time there was an improvement over the previous day, the manager would circulate and thank everyone. No bonuses, no pizza, just a complimentary remark. The slow group in the plant improved from 83% efficiency to 87% efficiency. The fast group, however, improved from 96% efficiency to 162% efficiency (62% beyond predicted capacity.)

One inch higher on the left and the magnetic white board would be level. I wonder what your numbers would be?

The Link Between Morale and Competence

“So, if morale suddenly improved as the speed of the line improved, what changed? What changed inside your team?” I asked.

“Remember, before, we were talking about competence and incompetence,” Emily thought out loud. “I didn’t believe you when you said the problem was incompetence. But now, I see such an improvement, I think you were right.”

“So, what changed inside their heads?” I asked again.

“Before, the team didn’t know the daily target number. That single number became a tool for them to get better. They became more competent.”

“They are on their way to mastery,” I said. That word mastery hung out there like a full moon. Inescapable.

“I never thought of it that way.”

“Put the two together.”

Competence and mastery,” she said.

“Why do people perform at a high level?” I asked.

“Because they can,” she replied. “Give them the tools to become competent and you will see progress.” Emily smiled. It was beginning to sink in.

“At least, that is half the story,” I announced.

“There’s more?” Emily asked.

Not a Problem of Morale

Emily’s white board had been in place for three days when I got the call. The tone in her voice was quite cheery.

“My team is absolutely amazing,” she reported. “The first day was tough because production was pretty much the same as before. The daily target was 175 units and we only managed to produce 86. I thought the team would implode, but when I got to work the next day, they were all there early and the line was already running. Instead of shutting down the line for break, they took breaks one at a time to keep things moving. We still only got 110 units, but they saw the improvement. Yesterday, they changed a couple of more things and we produced 140 units.

“What’s funny,” she continued. “All I have done, as a manager, is post the target number on the board in the morning and make comments about their improvement. All the changes, they have done on their own. It’s like everything has shifted. This is no longer my problem. They are working to fix it like it is their problem.”

“And, what about your morale problem?” I asked.

Emily’s face curled into a smile, “Oh, I don’t think the problem was morale.”

Caught Off-Guard, by Simplicity

Marcus was already in the conference room when I arrived. He had some papers spread on the table. I could tell by the look on his face he already had the answer. We were drilling down on an installation project that was under water.

“I knew when you asked for the production reports,” he started, “that we would find the problem within 30 seconds.”

“And?” I queried.

“You don’t even have to read the reports. The first three weeks, things are very repetitive. So repetitive that, starting in the fourth week, you can tell someone just photocopied the reports from the week before. The only change is the date at the top of the page. Then starting in week six, the reports stop.”

“And what does that tell you?”

“Well,” Marcus grimaced, “the quality of these reports follows exactly the real production curve in the field. We were meeting targets for the first three weeks. Things began to slide in week four and by week six, things went to hell in a hand basket.

“This is a very repetitive job, and it is very apparent that the weekly planning process just stopped. Everyone figured they would just keep working instead of stepping back to check progress and adjust. It seemed so simple, they lost the discipline of planning.

“The managers probably saved three hours per week in planning and checking, but lost more than 180 man hours in productivity. And they didn’t even know it until it was too late.”

“What’s the lesson?” I asked.

“Don’t relax by the appearance of simplicity. You still have to plan and check. In this case, the payoff would have been three hours to save 180 hours.”

How to Troubleshoot Productivity

I don’t know what happened.” Marcus grimaced. “Sure we were working under some tight restraints,” he explained. “During the first part of the contract, things were going well, but by the end, the wheels were coming off.”

“What do you think happened?” I asked.

“The contract called for several thousand feet of installation. We hit it with enthusiasm, high energy, everything clicked. I don’t know, but midway, we began to fall behind. Because of the working conditions, we could only work eight hours each day. Maybe we got sloppy, in the end, trying to finish, our quality got so poor that we had to go back and re-work several sections. First our margins disappeared, then our budget went completely underwater.”

“What do you think caused the erosion?”

“I don’t know. It was like we ran out of gas. I mean, everyone knew what to do. Technically, everyone was trained. The daily punch out was identical from start to finish. In the beginning, it was easy. In the end it was impossible. We just couldn’t keep up the momentum.”

“So, it wasn’t a matter or know-how or training. It wasn’t a matter of external conditions. Was it a matter of incentive or motivation?”

“No, you could see it in the eyes of the crew. They were in it, they were with it. They just could not produce.”

“Tell you what,” I interrupted. “Let’s pull the production records of the crew for the past six months and see what we find.”

Marcus went silent. I could tell he had mentally stumbled upon the reason. Before he left the room, he said he would have the records by the next morning.

Wishing for More Productivity

“They just don’t get it,” protested Kyle. “Why are they so stupid?”

“Why are they so stupid? Or why are you so stupid for expecting them to understand?” I asked.

Kyle did not expect my response and I could see him stiffen in the chair. He didn’t know how to react to the challenge, so he countered with a question.

“What do you mean?” he said, stalling for time. I was quiet. The seconds ticked by. Kyle finally broke the silence. “Okay, they are not stupid. I just wish they could be more productive, and solve problems better, work smarter.”

“You have exactly the kind of team you have designed,” I said. Kyle’s face lightened a bit.

“You know, you are probably right,” he replied. “So, how do I make it better? How can I improve the design?”

I waited. “It’s not a matter of improving the design. It’s a matter of improving the designer.”