It's been a long time since my last post - partly because I've been working and partly because I was working on one of my other blogs, Packaging: The Forgotten Medium.
My inspiration for this post - and for the next few - came from a meeting I had yesterday with a person in Human Resources, and we were discussing taking employee relations a step up into employee engagement.
When I moved from the world of Consumer Packaged Goods marketing into B2B sales and marketing, the general manager of the company I then worked for brought me into his office and gave me some of the best advice I've ever received.
He told me to buy some safety shoes and spend 30% of my time on the shop floor. I asked why, because I thought sales and marketing people needed to be out on the road in front of customers. He said I needed to know everyone in the plant on a first name basis because, as part of the management team, we would be going out just prior to the Christmas break to extend our holiday wishes to all employees, and he wanted it to be more than just a perfunctory handshake.
Our plant had two unions and a history, under previous ownership, of bad management-union relationships. There'd been a few strikes in the past and the current owners wanted to make a fresh start. Our GM told me that, in the past, it was like there were two worlds in the plant - shop floor and office - separated by a wall. We needed to break down that wall and make the management more accessible and responsive to the union personnel. Knowing everyone in the plant on a first name basis was an important part of this.
I followed his advice and remember putting on my safety shoes in preparation for my first time on the shop floor by myself.
I'd already been introduced at an all-employee meeting as a new member of the management team, so everyone knew I was the new kid on the block. I'd also been around through the plant a number of times, but never on my own - usually giving customers a tour with my boss.
I walked up to the first of several laminators we had in the plant and approached the operator. I asked him what this machine could do and how it worked. For the next hour, I was taken on a thorough tour of the machine by the operator and learned a lot! I appreciated the tour and what I could see was a sense of pride the operator had in his machine centre and a willingness to share that.
This was the start of a process of learning how to make a plant work more effectively, and my next few posts will be structured around this topic.
Showing posts with label responsibility. Show all posts
Showing posts with label responsibility. Show all posts
Wednesday, June 26, 2013
Tuesday, July 22, 2008
MAKING INTERNSHIPS WORK
When we hire students for summer jobs or internships, how many of us really challenge the students with work assignments? How often do we give them “safe” assignments or menial work just because it is easy and risk-free to do so.
My last summer job, before graduating with my engineering degree, was working in a process control laboratory for a large multinational. Technically, my job was to fill in for the regular chemists while they were on vacation. The plant relied on the data from the lab to control its operations, so it was an important role in keeping the plant running efficiently.
I was especially excited because my employer trained me to operate a million dollar mass spectrometer to analyze the ore samples for trace minerals/metals. It was a new technology we hadn’t really learned about in school, but the actual operation was really not that complicated, since the machine did virtually all the work.
However, one evening, when I was on night shift, the mass spec would not operate. The chemist who had been working with it during afternoon shift told me he’d been having problems with it.
The tests needed to be run somehow to keep the plant operating, and the only alternative was to use “wet” analytical chemical tests, for which we had a manual, but on which I’d had no training or experience. I called in to the main lab at headquarters and explained the situation and asked if they could send someone to check my results because I was unfamiliar with the wet tests and wanted to be sure I was providing reliable data to the plant.
About halfway through the shift, a chemist finally came over from the main lab and began to check the results of my testing by duplicating the procedure. Fortunately, his findings corroborated mine, and I felt very relieved and we worked together for the balance of my shift. Afterwards, my supervisor commended me for coping with the challenges of that evening and ensuring the plant had reliable data to operate by.
What I took away from this experience was that, by entrusting me with an important function and leaving me to operate an expensive piece of equipment, my employer was taking a big risk. I think this instilled a sense of responsibility in me that helped drive me to ensure I didn’t let them down. Something did, in fact, go wrong, but they had a backup plan and it was well enough documented that, even without training, I was able to follow it.
Dealing with a challenge such as this one built my self-confidence, and the commendation from my supervisor reinforced this.
Now fast-forward to about 30 years later, and our design department was hiring a summer intern.
Our design department manager wanted to assign the student to “assist” the other designers with some pretty safe tasks. However, during our interviews with the student, we discovered she has learned how to operate the same CAD software we used, so I told the design manager I wanted her to be able to produce workable designs on our CAD system.
As the summer progressed, she started out by doing some basic designs and we gave her opportunities to do more creative projects. Most importantly, on one project for our parent company, we used one of her designs and she got to see the project through to completion. She became very proficient with our software and was pumping out basic designs faster than the permanent staff. We were very pleased with her work.
As the summer came to a close, we took her out for an interview over lunch. During this, she mentioned enthusiastically that she felt she was the luckiest member of her class because she actually got to produce real designs. Most of her classmates were given menial tasks and never got the hands-on experience she got with us. She would have no hesitation about coming back with us for her next work term.
Internships or summer jobs are supposed to help students apply the skills they have learned in school and hopefully learn some new skills as well. These positions are an excellent way for an employer to assess a student as a potential permanent employee – but only if we take some risks and honestly give them the opportunity to apply their skills.
From the example I cited at the outset of this posting, that summer job in the lab helped me develop as a person as well as learn some very new technology. I suppose that experience influenced me, as a manager, to give our student designer a similar opportunity. That risk was rewarded with a very productive, motivated employee who exceeded our expectations.
Isn’t this what we all want?
My last summer job, before graduating with my engineering degree, was working in a process control laboratory for a large multinational. Technically, my job was to fill in for the regular chemists while they were on vacation. The plant relied on the data from the lab to control its operations, so it was an important role in keeping the plant running efficiently.
I was especially excited because my employer trained me to operate a million dollar mass spectrometer to analyze the ore samples for trace minerals/metals. It was a new technology we hadn’t really learned about in school, but the actual operation was really not that complicated, since the machine did virtually all the work.
However, one evening, when I was on night shift, the mass spec would not operate. The chemist who had been working with it during afternoon shift told me he’d been having problems with it.
The tests needed to be run somehow to keep the plant operating, and the only alternative was to use “wet” analytical chemical tests, for which we had a manual, but on which I’d had no training or experience. I called in to the main lab at headquarters and explained the situation and asked if they could send someone to check my results because I was unfamiliar with the wet tests and wanted to be sure I was providing reliable data to the plant.
About halfway through the shift, a chemist finally came over from the main lab and began to check the results of my testing by duplicating the procedure. Fortunately, his findings corroborated mine, and I felt very relieved and we worked together for the balance of my shift. Afterwards, my supervisor commended me for coping with the challenges of that evening and ensuring the plant had reliable data to operate by.
What I took away from this experience was that, by entrusting me with an important function and leaving me to operate an expensive piece of equipment, my employer was taking a big risk. I think this instilled a sense of responsibility in me that helped drive me to ensure I didn’t let them down. Something did, in fact, go wrong, but they had a backup plan and it was well enough documented that, even without training, I was able to follow it.
Dealing with a challenge such as this one built my self-confidence, and the commendation from my supervisor reinforced this.
Now fast-forward to about 30 years later, and our design department was hiring a summer intern.
Our design department manager wanted to assign the student to “assist” the other designers with some pretty safe tasks. However, during our interviews with the student, we discovered she has learned how to operate the same CAD software we used, so I told the design manager I wanted her to be able to produce workable designs on our CAD system.
As the summer progressed, she started out by doing some basic designs and we gave her opportunities to do more creative projects. Most importantly, on one project for our parent company, we used one of her designs and she got to see the project through to completion. She became very proficient with our software and was pumping out basic designs faster than the permanent staff. We were very pleased with her work.
As the summer came to a close, we took her out for an interview over lunch. During this, she mentioned enthusiastically that she felt she was the luckiest member of her class because she actually got to produce real designs. Most of her classmates were given menial tasks and never got the hands-on experience she got with us. She would have no hesitation about coming back with us for her next work term.
Internships or summer jobs are supposed to help students apply the skills they have learned in school and hopefully learn some new skills as well. These positions are an excellent way for an employer to assess a student as a potential permanent employee – but only if we take some risks and honestly give them the opportunity to apply their skills.
From the example I cited at the outset of this posting, that summer job in the lab helped me develop as a person as well as learn some very new technology. I suppose that experience influenced me, as a manager, to give our student designer a similar opportunity. That risk was rewarded with a very productive, motivated employee who exceeded our expectations.
Isn’t this what we all want?
Monday, June 30, 2008
FAMILIARITY BREEDS RESPECT
One of the best lessons I learned came from the general manager who recruited me from the packaged goods industry into the packaging industry.
The plant we worked in had two unions and a history of poor labor relations. The first week I was there, we had a communications meeting, and the union reps were not only very vocal about their views on management, but also seemed very aggressive.
The general manager’s advice to me was to get a pair of safety shoes, spend at least 25% of my time in the plant and to get to know everyone in the plant by name.
That first week, I tried to put it into practice and walked up to one of the machines, introduced myself to the operator and asked what his machine did. I think we spent about an hour together as he showed me what the machine could do and what capabilities weren’t being used. He took time to answer all my questions.
The company eventually suffered a financial setback, and we had to lay people off. Now, when I walked through the plant, you could sense the employees were scared. Because I was not only on the management team, but also the Marketing Director, I had some insight into the fortunes of the company.
When I encountered the union reps, the tone was very different from what I’d seen in the first weeks. They wanted to know what the future was for their members (and probably themselves), but the tone of communication was much more sober and the questions came not as “the union line” but at a more personal level.
I told them that quite honestly, I didn’t know what the future held. I didn’t promise everything would work out. I think they sensed and appreciated the candor in what I said, even though what I’d said didn’t really put their minds to rest.
At this point, it dawned on me that our role as managers was not just to run the business profitably, but we had a responsibility to the employees for their jobs. Their livelihood, in fact, depended on our ability to keep the business going. We had more control over their employment than they had – even with the unions – and therefore if we let the company go down, we were also letting down a whole team of employees who relied on us.
The lesson from this is that managers must remember that their employees are dependent, in more ways than we generally realize, on their actions. There is a need for mutual trust to make the organization work effectively and the best way to build that is to get out of the office and put a face to every employee in the organization. For the employees, it means there is a face to management and they can see managers as humans. Similarly, for the managers, it is an opportunity to remember a business is more than numbers: there are people whose livelihood depends on their actions.
The plant we worked in had two unions and a history of poor labor relations. The first week I was there, we had a communications meeting, and the union reps were not only very vocal about their views on management, but also seemed very aggressive.
The general manager’s advice to me was to get a pair of safety shoes, spend at least 25% of my time in the plant and to get to know everyone in the plant by name.
That first week, I tried to put it into practice and walked up to one of the machines, introduced myself to the operator and asked what his machine did. I think we spent about an hour together as he showed me what the machine could do and what capabilities weren’t being used. He took time to answer all my questions.
The company eventually suffered a financial setback, and we had to lay people off. Now, when I walked through the plant, you could sense the employees were scared. Because I was not only on the management team, but also the Marketing Director, I had some insight into the fortunes of the company.
When I encountered the union reps, the tone was very different from what I’d seen in the first weeks. They wanted to know what the future was for their members (and probably themselves), but the tone of communication was much more sober and the questions came not as “the union line” but at a more personal level.
I told them that quite honestly, I didn’t know what the future held. I didn’t promise everything would work out. I think they sensed and appreciated the candor in what I said, even though what I’d said didn’t really put their minds to rest.
At this point, it dawned on me that our role as managers was not just to run the business profitably, but we had a responsibility to the employees for their jobs. Their livelihood, in fact, depended on our ability to keep the business going. We had more control over their employment than they had – even with the unions – and therefore if we let the company go down, we were also letting down a whole team of employees who relied on us.
The lesson from this is that managers must remember that their employees are dependent, in more ways than we generally realize, on their actions. There is a need for mutual trust to make the organization work effectively and the best way to build that is to get out of the office and put a face to every employee in the organization. For the employees, it means there is a face to management and they can see managers as humans. Similarly, for the managers, it is an opportunity to remember a business is more than numbers: there are people whose livelihood depends on their actions.
Subscribe to:
Posts (Atom)
