Positive Reinforcement in the Real World

“So, how does that work around here?” Travis asked. Using the analogy of video games and expert levels made the reinforcement process understandable, but we were running a loading dock, not playing a video game.

“Travis, the guys loading the trucks, have you noticed the different colored t-shirts they wear, the ones with the company logo on the front?”

“Yeah, I noticed. We started that about three weeks ago. The new guys get a white t-shirt to start. We had a meeting about it.”

“And when does the new guy get his white t-shirt?”

“The first day,” Travis smiled.

“No, the first day he punches the timeclock reporting for work on-time,” I clarified. “What is the most important first behavior?”

“Showing up for work on time,” Travis said.

“And when does he get his second white t-shirt?”

Travis was catching on. “The second day he punches in for work on time.”

“And when does he get a yellow shirt?” I continued.

“Five days on time, consecutive days on time.”

“And when does he get a green shirt?”

“When he passes forklift training.” Travis stopped. “I think I get it.”

How to Coach Increasing Competence

“Sustained, discretionary effort. That’s what we are after,” I said. “The training period requires more attention and focus from the manager. But as time passes and new behaviors become competent skills, the reinforcement changes.

“In the beginning, the manager has to overcome push-back and fear of failure. But, as the new behavior turns to competence, the issues change.”

“So, what does the manager do differently?” asked Travis.

“Lots of things, but let’s start with the easy stuff. In the beginning, the manager may reinforce good old fashioned effort. But as time goes by and the effort becomes accomplished, the manager changes to reinforce a specific sequence. As the specific sequence becomes accomplished, the manager may reinforce speed or efficiency.

“Let’s go back to our example of the video game. Modern game designers structure training sequences into the lower levels of the game. Leveling up requires certain fundamental skills be demonstrated. Once accomplished, the player is introduced to more complex scenarios where mastery of the fundamentals must already exist. Each level becomes increasingly complex. The schedules of reinforcement change, but the principle remains the same. What gets reinforced gets repeated.”

Performance Improvement Depends on This

“Have you ever watched a parent teach their child to walk?” I asked.

“Yeah. I have a niece that is learning to walk. Her parents go goo-gah regularly, but still it’s a wobbly process.”

“Does a parent ever say – No, that’s not the way to do it, let me show you. Don’t fall down like that?”

“Well, no. They just get all excited, clap their hands and gurgle baby talk.”

“Somewhere along the way, we lose our natural instincts in the training process. Behavior that is reinforced gets repeated. The two elements that were missing from your training last year were practice and immediate positive reinforcement.

“Initial attempts at a new skill or new behavior are usually terrible, but that’s not the point. Your job as a manager is to get excited and encourage. Put people in a place where they can try again and get better.

“Look, Travis. When do parents give up encouraging their child to walk?”

Travis was still mentally drawing lines in the analogy. “They never stop, I guess. Only when the kid learns to walk.”

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

What Went Wrong?

“What do you think is the most difficult, planning or execution?” I asked.

“Planning is no slouch,” Travis replied, “but execution is where things go wrong. We may have a perfect plan, but we don’t have perfect execution.”

“Travis, sometimes I look at all the things a company wants to do, process changes, re-engineering, efficiency programs. They are all good ideas, yet, most fail. Why?”

“Execution?” pondered Travis.

“So, why did the execution fail? I saw the written plans. I attended some of the meetings. I observed the training. I watched the pep rallies. I saw the teamwork posters on the wall. I know incredible amounts of money, resources and energy went in to make it happen. In the end, not much changed. So, what went wrong?”

Travis hesitated, “Execution?”

“I saw team members trying new sequences, working with new equipment, handing off projects in new ways. But in the end, it didn’t stick. A new process would get shortcut. The old way worked faster. The enthusiasm faded into push-back. The word on the floor was, if we stiff arm it long enough, the re-engineering would go away. Morale plummeted. Ultimately, the initiative was abandoned. What stopped the execution?”

Travis wasn’t sure.

“Management focused all of their attention prior to the change. Little or no thought was given to how the new behaviors would be positively reinforced. What gets reinforced gets repeated. What does not get reinforced will stop. Dead in its tracks.”

What Gets Reinforced

“What gets reinforced gets repeated,” I said. “That’s why measurement and feedback loops are so important.

“Here is the insight. Most managers focus their time before the behavior. Most managers provide training and give lectures on the way things should be done and then wonder why they don’t get the desired behavior. Most managers think their biggest influence on behavior occurs before the behavior.

“The payoff, the big influence is after the desired behavior occurs. That’s when to pay the most attention. What gets reinforced gets repeated.”

Bottom Up or Top Down?

Yes.

There are a number of management moves (Agile being one) that demands bottom up orientation. I say yes. There are other management moves that that demand top down. Yes. How to reconcile the inevitable conflict?

The problem with those who would argue that top down is bad, they ignore the reason for higher levels of work and misconstrue the reason that management exists in the first place. Those who would argue against top down believe it is for control. It’s not.

The reason for top down, is context, not control.

It’s not about reporting. The fact is, we report to lots of people in the organization. I always ask, who has direct reports? All managers raise their hands. I have to deliver the bad news – you are not a manager so people can report to you.

It’s not about control, it’s about context.

Managerial roles exist to create context. That context is based on timespan. It is the role of the supervisor to think beyond what has to be done today, this week, this month. What is today’s work in the context of this week, this month?

It is the role of the manager to think beyond what has to be done this quarter, this year. What is today’s work in the context of this quarter, this year?

It’s not about control, it’s about context.

Managerial Attention

“Positive reinforcement isn’t money. Don’t think the only element you have as a manager is to give someone a bonus, or a spiff, or a raise. Don’t get me wrong, money is important, but it is not the only touch you have, nor is it the most powerful.

“See that production line over there,” I asked, pointing toward three lone workers alongside a bank of automated machine presses. Travis looked. He was familiar with that work area.

“Did you ever wonder why those three workstations still exist?” Travis knew that seven other stations in the line had been replaced with automated presses.

“Yeah, sometimes, it’s like why do we still have people doing that?”

“Initially, that’s what we thought, but when we benchmarked the automated production with the manual production, we found one worker not only kept up, but exceeded the output of the automated machine. We started asking questions. How could this be?

“Turns out the workstation on the end, Rochelle’s station, is right by her supervisor’s office. Every time the supervisor comes out, he stops, looks at Rochelle’s production and smiles at her. It’s the only station he stops at. He never says a word to Rochelle, yet she has the highest production rate.

“Do you think she has the highest production rate because she thinks she is going to get a bonus? Or because she might be replaced with a robot. I don’t think so.”

What is VUCA?

There is term used in the vernacular of Agile that describes the challenge of every organization.

VUCA

It’s an acronym for the world in which we live. Volatile, uncertain, complex and ambiguous. VUCA. Without any further definition, Agile offers many good ideas in dealing with that world.

Acknowledging that we live in this VUCA world, can we do more than spitball solutions?

And, that is where Timespan comes in. Most people clearly understand there are some problems more complex than others, some decisions more complex than others. There are different levels of VUCA. Timespan gives us insight into those levels.
S-I – (0-3 months) – trial and error problem solving
S-II – (3-12 months) – best practice and SOP problem solving
S-III – (12-24 months) – root cause analysis
S-IV – (24-60 months) – systems (multi-system) analysis

When the Deepwater Horizon blew up in 2010, the world looked, aghast, at a terrible environmental accident. I watched the coverage, the cameras on the ocean floor in real time and the engineers struggling with the problem. They tried this, they tried that. They tried the blowout preventer, that didn’t work. They tried the blind shear ram, that didn’t work. They were in a mode of trial and error problem solving. Why?

The engineers were not trying to solve a three year problem. No one said, “guys, let’s go back to the drawing board and over the next three years, let’s develop a better oil well so this never happens again.”

They said, “guys, we have to solve the problem today. We don’t have time to design the real solution. Figure out a way to cap it!”

Our understanding of timespan gives us insight in the levels of VUCA, and the level of problem solving required to make sure Deepwater Horizon doesn’t happen again.

Levels of Work and Morale

From the Ask Tom mailbag –

Question:
Let’s say I buy this stuff about levels of work. What will it help me do as a manager? What results should I see?

Response:
Immediately, as a manager, understanding levels of work will assist you in figuring out what you can delegate and what you have to self perform. As you look at task assignments, understanding levels of work will help you understand who to delegate work to.

Here is the immediate impact, you can make sure there is enough challenge in the work for your team to feel engaged at the highest level, stretched to their maximum capability. When people find challenge in their work, using their full attention and competence, what happens to job satisfaction?

There is no managerial trick. As a manager, you do not have to become a motivational speaker. It’s all about the work. Match the level of work in the role with the capability of the person. Maybe it is a little like magic.