We all have days when things are a bit slow. Perhaps your job requires you to run around nonstop for 8-10 hours every single day, but most people have periods when they’re sitting on their hands for a variety of reasons.
Personally I’d rather be too busy than too lightly loaded. Usually when I’m busy I feel like I‘m accomplishing something important, as long as it’s not just busy work. But when I’m bored twiddling my thumbs I feel like I’m wasting my time as well as the company’s, and not adding any value. And then there’s that nagging feeling that upper management is also aware of it, much to my detriment.
So at what point does boredom become a serious issue? If it’s a chronic problem, ask yourself why you don’t have more work assigned to you. Are you truly blocked in your work due to forces beyond your control, or does your manager not assign tasks to you?
If you are idle because of external factors, you should try to make effective use of your downtime. Perhaps the most productive thing you can do is to read technical books or browse technical web sites. Your employer may not be willing to spend money to send you to training, but by leveraging your downtime you can still learn new skills on the company’s dime.
If on the other hand you find yourself asking your boss for more work, and your boss pushes back, then you might want to be concerned. Perhaps your manager fears that you might not be able to handle important or complex assignments. In such cases it’s important that you go out of your way to earn your manager’s trust, by demonstrating whenever you get the chance that that you are reliable and can accomplish demanding tasks.
Thursday, February 19, 2009
Sunday, February 15, 2009
Probationary Hiring
Some people claim that the traditional interviewing model is broken, that it is inefficient and has a poor track record of identifying top candidates. They advocate the idea of probationary hiring. i.e., try a person out for 30 days, and if they don’t work out, just say good bye.
Another way this idea is presented is as a “Contract to Hire” position. The employee works as a contractor for the first X days, and then are presumably converted to perm status if the company finds it agreeable.
Personally I think this is a terrible idea regardless of how you label it. First of all, you could argue that pretty much all hiring is already probationary, especially in an “Employment at will” state like California. Under such conditions a company can let an employee go at any time for any reason (aside from those reasons barred by law, of course). Hence having a 30-day probationary period is just a fig leaf.
Secondly, 30 days is hardly enough time for someone to prove their worth. Unless a person comes into a job with exactly the skills and experience needed for the position, there will inevitably be a ramp-up time involved, which can take from a few weeks to a few months. Plus the person will need to establish a rapport with the team and other stakeholders. This is not something that can be done overnight, and it’s questionable whether 30 days, or even 90 days, is enough.
My advice? Give a new employee at least six months to settle in and prove themselves. That’s enough time for them to learn the ropes and make a real contribution. And if they are still struggling at the six month point, make it clear to them they need to shape up or ship out. And if they still have not improved by a few months after that, there is sufficient justification then to show them the door.
Another way this idea is presented is as a “Contract to Hire” position. The employee works as a contractor for the first X days, and then are presumably converted to perm status if the company finds it agreeable.
Personally I think this is a terrible idea regardless of how you label it. First of all, you could argue that pretty much all hiring is already probationary, especially in an “Employment at will” state like California. Under such conditions a company can let an employee go at any time for any reason (aside from those reasons barred by law, of course). Hence having a 30-day probationary period is just a fig leaf.
Secondly, 30 days is hardly enough time for someone to prove their worth. Unless a person comes into a job with exactly the skills and experience needed for the position, there will inevitably be a ramp-up time involved, which can take from a few weeks to a few months. Plus the person will need to establish a rapport with the team and other stakeholders. This is not something that can be done overnight, and it’s questionable whether 30 days, or even 90 days, is enough.
My advice? Give a new employee at least six months to settle in and prove themselves. That’s enough time for them to learn the ropes and make a real contribution. And if they are still struggling at the six month point, make it clear to them they need to shape up or ship out. And if they still have not improved by a few months after that, there is sufficient justification then to show them the door.
Sunday, February 8, 2009
Stuck at Above Market Pay?
Believe it or not, if you find yourself making above market pay for your position, that may not necessarily be such a good thing.
For instance, we’ve all heard stories about college seniors receiving six-figure offers straight out of college. Personally I’ve never seen this happen, but it’s not inconceivable. Still, it does point out that for whatever reason salaries can sometimes get out of whack.
Perhaps you’re really good at what you do, and perhaps you have a deep knowledge and understanding of your company’s systems that no one else has. Either way, your company has seen fit to reward you with generous raises. And now you think of yourself as having decent, but necessarily stellar pay.
So when you realize that your company doesn’t want you to grow beyond your currently very essential role, what happens? You’re surprised when you talk to recruiters and they only mention jobs with significantly lower pay than yours. And the jobs that do pay in your salary range are ones you’re not qualified for.
So what do you do in this case? It just so happened that while the great raises have fattened your wallet, they have also limited your career mobility. If your pay is too big for your britches at this stage in your career you have relatively few options. You could stay at your job, where your pay will eventually plateau and the market will catch up with your pay. Or else you could make a lateral move to another job that pays less than what you’re making, in the hopes that you’ll grow in that position and catch up to and exceed your previous pay level.
In my case, I once had a great job where I got double-digit % raises for several years in a row. Unfortunately all good things had to come to an end, and this company enacted a pay freeze (probably to make up for being so overly generous before). So when I decided to look around for new opportunities, I found that my pay was around 20% over market. I was a bit miffed, but there was not much I could do about it.
After much soul searching, I ended up taking a new job that paid about 10% less than what I had been making. And I did eventually catch up to my old pay level, but it took a couple of years.
For instance, we’ve all heard stories about college seniors receiving six-figure offers straight out of college. Personally I’ve never seen this happen, but it’s not inconceivable. Still, it does point out that for whatever reason salaries can sometimes get out of whack.
Perhaps you’re really good at what you do, and perhaps you have a deep knowledge and understanding of your company’s systems that no one else has. Either way, your company has seen fit to reward you with generous raises. And now you think of yourself as having decent, but necessarily stellar pay.
So when you realize that your company doesn’t want you to grow beyond your currently very essential role, what happens? You’re surprised when you talk to recruiters and they only mention jobs with significantly lower pay than yours. And the jobs that do pay in your salary range are ones you’re not qualified for.
So what do you do in this case? It just so happened that while the great raises have fattened your wallet, they have also limited your career mobility. If your pay is too big for your britches at this stage in your career you have relatively few options. You could stay at your job, where your pay will eventually plateau and the market will catch up with your pay. Or else you could make a lateral move to another job that pays less than what you’re making, in the hopes that you’ll grow in that position and catch up to and exceed your previous pay level.
In my case, I once had a great job where I got double-digit % raises for several years in a row. Unfortunately all good things had to come to an end, and this company enacted a pay freeze (probably to make up for being so overly generous before). So when I decided to look around for new opportunities, I found that my pay was around 20% over market. I was a bit miffed, but there was not much I could do about it.
After much soul searching, I ended up taking a new job that paid about 10% less than what I had been making. And I did eventually catch up to my old pay level, but it took a couple of years.
Wednesday, January 28, 2009
Pay Disparities
The person sitting in the next cube over from you may be doing the same type of work, perhaps even working on the exact same code that you are. However, she may be making 20% or 30% more than you. Sometimes the pay disparities are even greater. Of course, in most cases you won’t be aware of this since salary information is closely guarded.
Such disparities exist for a number of reasons. Technical skill sets, negotiating skills, etc. factor in, but often it’s just a matter of experience, or tenure if you will. The longer a person is at a job the more raises they’ll get. And even if those are just modest cost of living raises they can add up. If someone has the same job as you but they’ve been in that position for 10 years longer, with a 3% annual raise they could be earning 35% more. And with 4% annual raises the difference would be 48%.
But what if the other person has comparable levels of experience, or worse, less experience than what you have? What would explain the pay disparity then?
It’s possible that the other person may just better at their job. They could be more productive, writing more code with fewer bugs. They may be better at estimation and meeting their dates, and they may have more significant accomplishments. They may also work in a more high profile area and be more visible to management. They may also be better at advertising their accomplishments, as distasteful as that idea may be to some.
If you have accounted for all of these possibilities and still feel that you are underpaid, you need to look inward. Is there a reason why you might be underpaid? Or in fact, are you really underpaid at all? The only true way to tell is to test the job markets. You can probably get a feel for your market value from recruiters, or from doing a few interviews. You might very well find that you are already at market pay. And if not -- well, you already have a head start on finding new job options.
Such disparities exist for a number of reasons. Technical skill sets, negotiating skills, etc. factor in, but often it’s just a matter of experience, or tenure if you will. The longer a person is at a job the more raises they’ll get. And even if those are just modest cost of living raises they can add up. If someone has the same job as you but they’ve been in that position for 10 years longer, with a 3% annual raise they could be earning 35% more. And with 4% annual raises the difference would be 48%.
But what if the other person has comparable levels of experience, or worse, less experience than what you have? What would explain the pay disparity then?
It’s possible that the other person may just better at their job. They could be more productive, writing more code with fewer bugs. They may be better at estimation and meeting their dates, and they may have more significant accomplishments. They may also work in a more high profile area and be more visible to management. They may also be better at advertising their accomplishments, as distasteful as that idea may be to some.
If you have accounted for all of these possibilities and still feel that you are underpaid, you need to look inward. Is there a reason why you might be underpaid? Or in fact, are you really underpaid at all? The only true way to tell is to test the job markets. You can probably get a feel for your market value from recruiters, or from doing a few interviews. You might very well find that you are already at market pay. And if not -- well, you already have a head start on finding new job options.
Sunday, January 25, 2009
Performance: Perception vs. Reality
When providing feedback to employees, you will often find that employees respond to negative feedback with surprise. It’s inconceivable to them that anyone could fail to recognize the brilliance of their work. And if there were any problems with their work, it was due to someone else’s mistakes.
Of course I’m exaggerating, but not by much. Fact is, most people have a fairly high opinion of themselves (and I suppose that would include me as well). Most people like to think of themselves as stars, or at the very least above average.
And yet, it’s been shown (sorry, no link handy at the moment) that the true stars tend to rate themselves more modestly than the less stellar performers. Why is this? Perhaps it’s because the top people are well aware of their limits and acknowledge them, whereas the lower performers have no idea just how limited their skills are. And when confronted with those limits, they often deny the charge, blame others for their failures, or deem those limits not important.
So as a manager, how do you reconcile an employee’s inflated sense of self with your somewhat less flattering assessment? You need hard facts: metrics, examples, data points. The employee will typically try and shift the blame, and you need to be prepared for that with hard evidence that is undeniable.
Of course I’m exaggerating, but not by much. Fact is, most people have a fairly high opinion of themselves (and I suppose that would include me as well). Most people like to think of themselves as stars, or at the very least above average.
And yet, it’s been shown (sorry, no link handy at the moment) that the true stars tend to rate themselves more modestly than the less stellar performers. Why is this? Perhaps it’s because the top people are well aware of their limits and acknowledge them, whereas the lower performers have no idea just how limited their skills are. And when confronted with those limits, they often deny the charge, blame others for their failures, or deem those limits not important.
So as a manager, how do you reconcile an employee’s inflated sense of self with your somewhat less flattering assessment? You need hard facts: metrics, examples, data points. The employee will typically try and shift the blame, and you need to be prepared for that with hard evidence that is undeniable.
Friday, January 16, 2009
Providing Feedback
Far too many managers fail to provide any meaningful performance feedback until it’s time for a review. It’s no surprise then that many employees are sometimes taken aback by critical reviews, as they never see it coming.
In an ideal world managers would provide continuous feedback and course corrections to their employees. However, most people, managers included, hate giving negative feedback. They worry about a conflict that may arise, where the employee takes the news badly, gets defensive, or becomes argumentative.
Perhaps these people have read Dale Carnegie’s seminal book, “How to Win Friends and Influence People”. In it he urged readers to never engage in criticism, which some equate with giving negative feedback. They interpret the advice to mean that if a manager has only negative feedback, they shouldn’t provide any sort of feedback at all. i.e., if you can’t say something nice about a person…
However, this is poor advice, or at least a bad interpretation of what Carnegie meant. Most employees in fact would appreciate feedback -- any kind of feedback, even negative -- over getting no feedback at all. At least with negative feedback they know where they stand with their manager.
As an employee, you should welcome feedback of any kind. Good feedback is always nice, of course, but aside from the ego stoking it’s not particularly valuable. More useful is negative feedback, as long as it’s constructive. In other words, what you want is feedback on what you’re doing poorly, and how you can improve your performance.
If you do receive negative feedback, it’s important that you not become defensive. If you do become defensive, your manager may also become defensive, and it can turn into a “He said, she said” type of blame game. Instead, you should take the criticism to heart, even if it seems unwarranted. Even if the criticism seems totally off base, you should take time to think about why your manager sees things in that way. It might just be a matter of perception, for instance, which might be remedied by keeping your manager better informed and engaging in a little proactive PR.
In an ideal world managers would provide continuous feedback and course corrections to their employees. However, most people, managers included, hate giving negative feedback. They worry about a conflict that may arise, where the employee takes the news badly, gets defensive, or becomes argumentative.
Perhaps these people have read Dale Carnegie’s seminal book, “How to Win Friends and Influence People”. In it he urged readers to never engage in criticism, which some equate with giving negative feedback. They interpret the advice to mean that if a manager has only negative feedback, they shouldn’t provide any sort of feedback at all. i.e., if you can’t say something nice about a person…
However, this is poor advice, or at least a bad interpretation of what Carnegie meant. Most employees in fact would appreciate feedback -- any kind of feedback, even negative -- over getting no feedback at all. At least with negative feedback they know where they stand with their manager.
As an employee, you should welcome feedback of any kind. Good feedback is always nice, of course, but aside from the ego stoking it’s not particularly valuable. More useful is negative feedback, as long as it’s constructive. In other words, what you want is feedback on what you’re doing poorly, and how you can improve your performance.
If you do receive negative feedback, it’s important that you not become defensive. If you do become defensive, your manager may also become defensive, and it can turn into a “He said, she said” type of blame game. Instead, you should take the criticism to heart, even if it seems unwarranted. Even if the criticism seems totally off base, you should take time to think about why your manager sees things in that way. It might just be a matter of perception, for instance, which might be remedied by keeping your manager better informed and engaging in a little proactive PR.
Tuesday, January 13, 2009
Productivity Ratios and Negative Producers
Numerous management studies have found there can be a 10-to-1 ratio difference in productivity between engineers.
Of course, the widest performance spread can be greater than 10-to-1 if you take into account your worst engineers. Technically it could be 100-to-1, or infinity. In fact, the math can break down if your worst engineer is a net negative producer.
How does an engineer exhibit negative productivity? Typically they write awful code that causes breakages and which have to be cleaned up by teammates. Or they may waste time in meetings arguing contrarian positions just because they like to yank peoples’ chains.
As a manager it is your job to isolate these negative producers and insulate your team from them. Ideally you’d show these people out the door, but there are usually complicating factors that keep them at their jobs longer than you’d like.
Also, it’s important not to blind yourself to the possibility that it might not be the individual that’s at fault for negative productivity. It could be the environment, or the team chemistry, or the nature of the technical problem being tackled. As I mentioned previously, a person can be a star in one realm and flounder in another environment. It’s up to the manager to spot these problems and do everything possible to mitigate them.
Of course, the widest performance spread can be greater than 10-to-1 if you take into account your worst engineers. Technically it could be 100-to-1, or infinity. In fact, the math can break down if your worst engineer is a net negative producer.
How does an engineer exhibit negative productivity? Typically they write awful code that causes breakages and which have to be cleaned up by teammates. Or they may waste time in meetings arguing contrarian positions just because they like to yank peoples’ chains.
As a manager it is your job to isolate these negative producers and insulate your team from them. Ideally you’d show these people out the door, but there are usually complicating factors that keep them at their jobs longer than you’d like.
Also, it’s important not to blind yourself to the possibility that it might not be the individual that’s at fault for negative productivity. It could be the environment, or the team chemistry, or the nature of the technical problem being tackled. As I mentioned previously, a person can be a star in one realm and flounder in another environment. It’s up to the manager to spot these problems and do everything possible to mitigate them.
Subscribe to:
Posts (Atom)
