I have been rather lax lately in keeping up with my posts. I can partially blame this on my ADD, and partially on the fact that it was the start of the best weather for rock climbing, and have been spending quite a bit of my time the last several months engaged in that in some way. I had considered combining the blogs, but decided against this course, as the two disparate subject matters would not mesh well. So, onward with two separate blogs.
I had made a post on an internet forum several months ago in response to a new manager's inquiry on how to deal with a problem employee. My response saw several other newly minted supervisors to email me and ask for some advice on how to deal with problem employees who were also older than them and had been with the company for a longer period of time. This seems to be a rather common issue, so I figured that I would share my answers here.
The way that this seems to manifest is something like, "Why won't s/he listen to me? I ask them to do their job, and they get snippy/passive-aggressive/combative with me, and they are really dragging morale into the gutter."
The solution, like it is for most problems, is to find out the root cause behind these actions while making sure to engage in a little damage control. This is a situation where simply attempting to assert your authority will ultimately result in entrenched factions sniping at each other from behind cubicle walls.
The first thing I always ask is, "Have you sat them down and spoken with them about their actions?" Most of the time, the answer is, "Yes." The next question is always, "And did the problem go away?", to which the supervisor will usually say, "No." Clearly, your communication wasn't effective. You didn't take the time to not only try and dig to the problem's root, but you did not set a clear expectation of acceptable actions and potential consequences.
Many tenured employees will "act out" for one of two reasons:
1) They feel threatened
2) They feel marginalized
In the first scenario, they may feel threatened by someone younger moving into a position of power, someone who may have shown aptitude in areas that they have not been able to suss out, or that this is a sign of them aging out of the workforce. They may also know that they are not as effective at their jobs as they could be, and this new manager may decide to change things around in a way that will see them have to work harder or be phased out (though this is not limited to older workers, but on all workers who don't do their jobs). In these cases, the worker will act out in a way to stake out their territory, or to infer that they are not intimidated by the new boss.
In the second scenario, there may be a case where they were overlooked for a promotion (possibly the same promotion that you just received), and may feel that their seniority and expertise in the organization is being overlooked. Regardless of whether or not this is true, their perception of events is what shapes how they interact with their workspace, and that perception must be taken into account.
Regardless of the scenario, the answer is always better communication. Take some time to not just speak with, but listen to, the employee. Let them air their grievances and ask them how they would suggest the issues may be fixed. A better solution is to do this out of the office, over a cup of coffee or a hot dog. This is a less intimidating environment and will help put the employee at ease. This will help you tease out the little details that will clue you in to their behavior.
The best solution is to make sure that you include them when making decisions, even if it is for just a little input here and there. If they feel as though they are being recognized for their expertise and tenure, many of the problem behaviors will start to disappear.
However, there is a flip side to this coin: don't let them run the place or run over you. If their behavior is problematic, make sure that you discuss with them what is acceptable action and what is not. Depending on the severity of their behavior, you may need to outline consequences that will occur should the behavior not improve (use a performance improvement process in this scenario, though it does not have to be a grim conversation). Explain to them the position that they put you in when they choose to act a certain way at work, whether it is them going outside of established procedures or talking trash in the break room.
Do not, under any circumstances, talk to them about attitude. This equals death. You cannot, repeat cannot coach attitude. You can, however, coach actions. Focus on their actions, and coach to their best performance.
This is a delicate balancing act, dealing with established employees, especially as a younger or first-time supervisor. I made this mistake when I was a manager at REI. There was a long-time employee in my department who clearly had a disdain for managers. I tried to simply let him do his job and speak to him minimally, you know, just stay out of his way, but this backfired. He felt as though I was not including him on decisions and not appreciating his deep knowledge of the store's inventory and product movement. This lead to him resenting me even more, and my resenting his attitude towards me. When I tried to assign him projects, they would be completed, but not to what I had imagined (though to the letter of what I asked of him), and the cycle continued. I actually tried to coach him because he refused to shake my hand one day.
I think that after that incident that I reactivated my brain and took a different approach. Rather than simply making decisions and communicating them to my staff, I started making a much more concerted effort to ask their opinions before acting. I specifically went to this "problem" employee and gave him free reign to complete the projects that he was best at, and our working relationship, while never warm, improved greatly.
Tuesday, July 14, 2009
Monday, March 9, 2009
Answering Stupid Questions
A friend of mine recently made a post in their blog about the stupid questions that high school students sometimes ask. The truth as (as is shown by some of the questions the students ask) is that yes, there is such a thing as a stupid question. We only tell people who ask stupid questions that there aren't stupid questions to make them feel better.
As a manager, have you been asked a stupid question? Of course you have. We all have. At a recent position, there was one member of the sales team that routinely asked stupid questions, usually asking me to explain something that I had just spent the last hour training her on.
She definitely got on my last nerve, and though I thought that I his it, everyone around me knew when I was training her just from my change of demeanor. The only saving grace in this was that it wasn't just me...she was this way with everyone, to the point where people cringed at the very mention of her name. She was, without a doubt, in the category of stupid.
And it was my fault.
It wasn't my fault that she was not a relatively intelligent human being; it was my fault that she got a job with this company. It was my fault for not screening her more thoroughly.
In the words of the immortal Mr. Miyagi, "Best way to block punch: no be there." The best way to stop performance issues is to not hire people who are going to be problematic. Simple enough, but rarely followed.
Most managers rely on the time-honored approach of the interview process. This usually begins with screening some resumes. This is followed by a phone interview, and then a face-to-face interview with one or more managers. Sometimes, there will be a second interview. A hiring decision is made, the new hire comes on board, and within six months, the hiring manager knows regret that can only be equated with eating bad Mexican food from a shady sidewalk vendor.
Other businesses rely strictly on testing to make hiring decision. This is excellent for determining a candidate's skill set, but does little in determining a candidate's fit with the company and the team.
The real way to weed out the, oh, let's call them "weird" ones, is to not only use a combination approach (both behavioral-based interview questions and objective testing), but include a sample of their work. For example, in a sales position, ask them for a sample proposal, a demonstration their cold-calling technique, and references from their customers. Any salesperson worth their salt will be able to cold call you, show you their boilerplate proposal, and offer a list of customers who are happily satisfied.
We (one of the other managers and I) did not do this last step. We had the aforementioned candidate interview with both of us and take a test, but did not ask for other proof of her accomplishments. Turns out that she was nothing but a performance issue from the start, one that not only monopolized our time, but did not sell much of anything for 6 months. Had we been more thorough in the interview process using the above techniques, we could have avoided the entire mess, and who knows, hired a salesperson that could...well, you know, sell.
As a manager, have you been asked a stupid question? Of course you have. We all have. At a recent position, there was one member of the sales team that routinely asked stupid questions, usually asking me to explain something that I had just spent the last hour training her on.
She definitely got on my last nerve, and though I thought that I his it, everyone around me knew when I was training her just from my change of demeanor. The only saving grace in this was that it wasn't just me...she was this way with everyone, to the point where people cringed at the very mention of her name. She was, without a doubt, in the category of stupid.
And it was my fault.
It wasn't my fault that she was not a relatively intelligent human being; it was my fault that she got a job with this company. It was my fault for not screening her more thoroughly.
In the words of the immortal Mr. Miyagi, "Best way to block punch: no be there." The best way to stop performance issues is to not hire people who are going to be problematic. Simple enough, but rarely followed.
Most managers rely on the time-honored approach of the interview process. This usually begins with screening some resumes. This is followed by a phone interview, and then a face-to-face interview with one or more managers. Sometimes, there will be a second interview. A hiring decision is made, the new hire comes on board, and within six months, the hiring manager knows regret that can only be equated with eating bad Mexican food from a shady sidewalk vendor.
Other businesses rely strictly on testing to make hiring decision. This is excellent for determining a candidate's skill set, but does little in determining a candidate's fit with the company and the team.
The real way to weed out the, oh, let's call them "weird" ones, is to not only use a combination approach (both behavioral-based interview questions and objective testing), but include a sample of their work. For example, in a sales position, ask them for a sample proposal, a demonstration their cold-calling technique, and references from their customers. Any salesperson worth their salt will be able to cold call you, show you their boilerplate proposal, and offer a list of customers who are happily satisfied.
We (one of the other managers and I) did not do this last step. We had the aforementioned candidate interview with both of us and take a test, but did not ask for other proof of her accomplishments. Turns out that she was nothing but a performance issue from the start, one that not only monopolized our time, but did not sell much of anything for 6 months. Had we been more thorough in the interview process using the above techniques, we could have avoided the entire mess, and who knows, hired a salesperson that could...well, you know, sell.
Sunday, March 1, 2009
"Patience, young Skywalker"
Random observation: As I'm sitting here in Starbucks, I am wondering to myself: how many covers of Ah-Ha's "Take On Me" do we really need?
I am finding that one of my "pain points", to use an awful sales training term, is being pushed repeatedly as of late: I am not what most would consider a patient person. I have a proclivity for instant gratification, that when I have an idea, I want to see it come to fruition yesterday. As it turns out, starting a business requires some ample amounts of the stuff.
I have the basic frame work laid for Auspex, have started some marketing and some networking, but have yet to see any of these efforts bare fruit. I am trying to take the Jeffrey Gitomer approach and grab attention through networking, but I am finding this an exceedingly difficult chore. Whether this is because I am not terribly good at it, or because it requires some degree of patience, or a combination, I do not know.
One such networking group seemed like it would have helped put Auspex on the right track, but then there was a catch: they wanted $300 for an annual membership, $100 for a start up fee, and $15 per week for the weekly lunch meetings. So, in total, over $1100, plus I would have to turn in a certain number of referrals each week to maintain membership. Not that I'm doubting the efficacy of this approach, but the fact that they wanted the entire membership fee up front, rather than providing for a payment plan, completely put this out of reach.
This has lead me to two thoughts this week about effective leadership:
Its the patience end of things that I need the real work. I need to work on being able to just wait and not expect instant results in certain circumstances. I think that most managers/leaders need to, if they haven't already mastered it, develop this skill and dedicate time to its cultivation. It is one thing to expect projects and tasks completed by a hard, yet resonable deadline; it is another thing entirely to demand instantaneous results.
Where patience plays its largest role is in employee development. This can and will be the most time-consuming task a leader will undertake, and the results will be subtle and gradual. Where most leaders fall short it when, after teaching a new skill or having a conversation about performance, they expect immediate and sustained improvement in performance. In most cases, not only is this not the typical outcome, it is also unlikely that the employee is able to perform to that standard. The patient leader needs to realize that to build real teams, to develop the strongest employees, that there is a certain investment of time, and that requires patience.
I am finding that one of my "pain points", to use an awful sales training term, is being pushed repeatedly as of late: I am not what most would consider a patient person. I have a proclivity for instant gratification, that when I have an idea, I want to see it come to fruition yesterday. As it turns out, starting a business requires some ample amounts of the stuff.
I have the basic frame work laid for Auspex, have started some marketing and some networking, but have yet to see any of these efforts bare fruit. I am trying to take the Jeffrey Gitomer approach and grab attention through networking, but I am finding this an exceedingly difficult chore. Whether this is because I am not terribly good at it, or because it requires some degree of patience, or a combination, I do not know.
One such networking group seemed like it would have helped put Auspex on the right track, but then there was a catch: they wanted $300 for an annual membership, $100 for a start up fee, and $15 per week for the weekly lunch meetings. So, in total, over $1100, plus I would have to turn in a certain number of referrals each week to maintain membership. Not that I'm doubting the efficacy of this approach, but the fact that they wanted the entire membership fee up front, rather than providing for a payment plan, completely put this out of reach.
This has lead me to two thoughts this week about effective leadership:
- Leaders must be patient.
- Leader must know when to stop pouring money into something.
Its the patience end of things that I need the real work. I need to work on being able to just wait and not expect instant results in certain circumstances. I think that most managers/leaders need to, if they haven't already mastered it, develop this skill and dedicate time to its cultivation. It is one thing to expect projects and tasks completed by a hard, yet resonable deadline; it is another thing entirely to demand instantaneous results.
Where patience plays its largest role is in employee development. This can and will be the most time-consuming task a leader will undertake, and the results will be subtle and gradual. Where most leaders fall short it when, after teaching a new skill or having a conversation about performance, they expect immediate and sustained improvement in performance. In most cases, not only is this not the typical outcome, it is also unlikely that the employee is able to perform to that standard. The patient leader needs to realize that to build real teams, to develop the strongest employees, that there is a certain investment of time, and that requires patience.
Subscribe to:
Posts (Atom)