Originally posted August 9, 2014
One of the phrases we would hear a lot at the coal-fired Power Plant in North Central Oklahoma was “Safety is Job Number One”. It’s true that this should be the case, but at times we found that safety was not the highest priority. It is easy to get caught up in the frenzy of a moment and Safety just seemed to take a second row seat to the job at hand.
Making Safety Job Number Two was usually unintentional, but sometimes on rare occasions, we found that it was quite deliberate. Not as a company policy, but due to a person’s need to exert their “Supervisory” Power over others. I mentioned one case in the post titled: “Power Plant Lock Out Tag Out, or Just Lock Out“.
During the summer of 1993, everyone at the plant learned about the Quality Process. I talked about this in the post: “A Chance for Power Plant Men to Show Their Quality“. I had joined the Action Team. This was a team of Power Plant Men that reviewed proposals turned in by the quality teams in order to determine if they had enough merit to be implemented. If they did, we would approve them. If we decided an idea was not appropriate enough to be implemented, we sent it back to the team that had written the proposal with an explanation why it was rejected.
Our team had turned in a proposal to create a Safety Task Force. One that would act like an Action Team similar to the formed for the Quality Process. It seemed like a logical progression. I was the main proponent of the Safety Task Force, but to tell you the truth, it wasn’t all my idea.
Not only had other members of our Quality Team mentioned forming a Safety Task Force, but so did our Electric Supervisor, Tom Gibson. He had called me to his office one day on the pretense of me getting in trouble…. I say that, because whenever he would call me on the gray phone and respond, “Kevin. I want to see you in my office right now.” that usually meant that I had stepped on someone’s toes and I was in for a dressing down…
— Was I the only one that had this experience? It seemed that way. But then, I was usually the one “pushing my bubble” (as Charles Foster would say). When I arrived at Tom’s office, he asked me if I would ask our team to create a proposal for a Safety Task Force. I told him that I’m sure we would. We had already talked about it a couple of times in our meetings.
I didn’t mind playing “Bad Cop” in the game of “Good Cop, Bad Cop”. That is, it never bothered me to be the one that pushed an unpopular issue that really needed pushing. Where someone else would follow-up as the “Good Cop” in a way that takes away the bitter taste I left as “Bad Cop” by proposing the same solution I proposed only with a more positive twist.
At the time, I figured that Tom Gibson was going to be “Good Cop” in this effort since he had pulled me aside and asked me to initiate the proposal. As it turned out, I ended up playing both Bad Cop and Good Cop this time. I played the Good Cop when Ron Kilman had met with me to discuss a new Safety Idea. The Behavior-Based Safety Process. See the Post: “ABC’s of Power Plant Safety“.
I proposed the Safety Task Force in a sort of “Bad Cop” negative manner. That is, I had pointed out how our current system was failing, and other negative approaches. When I explained how the Behavior-Based Safety Process works as “Good Cop”, Ron had told me to go ahead and form the Safety Task Force.
I asked for volunteers to join the Safety Task Force. After I received a list of people that wanted to be on the Task Force, I chose a good cross-section of different roles and teams from both Maintenance and Operations. I had lofty visions of telling them all about the Behavior-Based Safety Process, and then going down the road of implementing this process at the plant.
I didn’t realize that the Power Plant Men had different ideas about what a Safety Task Force should be doing. They weren’t really interested in trying out some new Safety “Program”. I tried explaining that this was a “Process” not a “Program”, just like the Quality Process. They weren’t buying it.
We had Ground Rules that we created the first day that kept me from ramming anything down their throats, so I went along with the team and listened to their ideas. It turned out that even though the Power Plant Men on the Safety Task Force didn’t want to hear about my “beloved” Behavior-Based Safety Process, they did have good ideas on how to improve safety at the plant.
We decided that we would ask for Safety Proposals just like the Quality Process did. It was felt that the Safety Task Force didn’t have any real “authority” and a lot of people at the plant thought that without the authority to really do anything, the task force was going to be an utter failure.
We decided that the best way to show that the Task Force was going to be a successful force of change toward a safer Power Plant, we would ask for ideas on how to improve the safety at the plant. When we did, we were overwhelmed by the response. Safety Concerns poured in from all over the plant.
At one point we had over 250 active safety ideas that we had decided were worth pursuing. The members of the team would investigate the ideas assigned to them and see what it would take to make the requested changes. Because of the overwhelming response, it didn’t make much sense taking all the approved requests to the Plant Manager. So, in many cases, we decided that a trouble ticket would be sufficient.
I posted the progress of all the active ideas each week on every official bulletin board in the plant. This way, everyone could follow the progress of all of the ideas. As they were successfully completed, they went on a list of Safety Improvements, that I would post next to the list of active proposals.
I think the members of the Safety Task Force might have been getting big heads because at first it appeared that we were quickly moving through our list of plant Safety Improvements. A lot of the improvements were related to fixing something that was broken that was causing a work area to be unsafe. I say, some of us were developing a “big head” because, well, that was what had happened to me. Because of this, I lost an important perspective, or a view of the ‘Big Picture”.
I’ll give you an example that illustrates the “conundrum” that had developed.
We had created some trouble tickets to fix some pieces of equipment, and walkways, etc, that posed a safety risk. After several weeks of tracking their progress, we found that the trouble tickets were being ignored. It seemed that this came on all of the sudden. When we had first started the task force, many of our trouble tickets were being given a high priority, and now, we were not able to succeed in having even one trouble ticket completed in a week.
After going for two weeks without one of the trouble tickets being worked on, I went to Ron Kilman, the Plant Manager to see if we could have some of his “Top Down” support. To my surprise, he gave me the exact same advice that our Principal, Sister Francis gave our Eighth Grade class at Sacred Heart School in Columbia, Missouri when we ran to her with our problems.
Ok. Side Story:
Three times when I was in the eighth grade, our class asked Sister Francis to meet with us because we had an “issue” with someone. One was a teacher. We had a personal issue with the way she conducted herself in the class. Another was a boy in the 7th grade, and the fact that we didn’t want him to go with us on our yearly class trip because he was too disruptive. The third was a general discontent with some of the boys in the 5th and 6th grade because of their “5th and 6th grade” behavior.
In each case, Sister Francis told us the same thing (well almost the same thing). In the first two cases, she told us we had to handle them ourselves. We had to meet with the teacher and explain our problem and how we wanted her to change. We also had to meet with the boy in the seventh grade and personally tell him why we weren’t going to let him go on our trip. In each case it was awkward, but we did it.
In the case of the 5th and 6th graders, Sister Francis just said, “When you were in the 5th grade, if you acted the way these 5th graders acted to an eighth grader, what would happen? Well. Deal with this as you see fit. We all knew what she meant. When we were in the fifth grade, if we treated the eighth graders the way these guys treated us, they would have knocked us silly.
So, the next morning when I was approached by a fifth grader displaying the disrespectful behavior, I gave him a warning. When my warning was greeted with more “disrespect”, I did just what an eighth grader would have done when I was a fifth grader. I pushed him down the stairs. — Not hard. He didn’t tumble over or anything, but he ran straight to Sister Francis and told her what I had done.
Sister Francis came up to our room and told me to go to the principal’s office. — We only had 14 people in the Eighth Grade, so it wasn’t hard to find me. I protested that I was only doing what she authorized us to do the previous day. She agreed, but then she also explained that she had to respond the same way she would have responded to the eighth graders three years earlier if they had done the same thing.
I could tell by her expression, that my “punishment” was only symbolic. From that day on, the 5th and 6th graders that had been plaguing our class were no longer in the mood to bother us. We had gained their respect.
End of Side Story.
So, what did Ron Kilman tell me? He told me that if we were going to be a successful Safety Task Force, then we would need the cooperation of Ken Scott. Ken was the Supervisor of the Maintenance Shop and the one person that had been holding onto our trouble tickets. Ron said, “You will have to work this out with Ken yourself.” — Flashes of Ron Kilman wearing a black nun’s robe flashed through my head, and suddenly I felt my knuckles become soar as if they had been hit by a ruler. — No, I’m not going to draw you a picture.
So, we did what would have made Sister Francis proud. We asked Ken Scott to meet with us to discuss our “issue”. We pointed out to him that the trouble tickets we had submitted were safety issues and should have a higher priority. We also pointed out that we had not had one safety related trouble ticket completed in almost three weeks.
Then it was Ken’s turn…. He said, “Just because you say that something is a safety issue doesn’t make it one. Some of the trouble tickets submitted were to fix things that have been broken for years. I don’t think they are related to safety. I think people are using the safety task force to push things that they have wanted for a long time, and are just using “safety” as a way to raise the priority. Some of these ideas are costly. Some would take a lot of effort to complete and we have our normal tickets to keep the plant running.” — Well, at least when Ken stopped talking we knew exactly where he stood. He had laid out his concerns plain and clear.
The Safety Task Force members used some of the tools we had learned during the Quality Process, and asked the next question…. So, how do we resolve this issue? Ken said that he would like to be consulted on the ideas before a trouble ticket is created to see if it would be an appropriate route to take.
It was obvious now that we had been stepping all over Ken’s Toes and our “demands” had just made it worse. Ken felt like we had been trying to shove work down his throat and he put a stop to it. After hearing his side of the story, we all agreed that we would be glad to include Ken in all the safety issues that we thought would require a trouble ticket.
From that point, we had much more cooperation between Ken Scott and the Safety Task Force. Ken really wasn’t a problem at all when it came down to it. The way we had approached the situation was the real issue. Once we realized that, we could change our process to make it more positive.
This worked well with Ken, because he was forthright with us, and had spoken his mind clearly when we asked. This didn’t work with everyone of the people that pushed back. We had one person when we asked him if he could explain why he was blocking all our attempts to make changes, his only reply was “Because I am the barrier! I don’t have to tell you why!” That is another story. I’m not even sure that story is worth telling. I know that at least one person that reads this blog regularly knows who I am referring to, because he was in the room when this guy said that…. He can leave a comment if he would like….