Showing posts with label focal. Show all posts
Showing posts with label focal. Show all posts

Monday, April 30, 2007

Catching up...

A few comments have come in on the last couple of posts that I wanted to address here rather than replying with additional comments. Someone wrote:

I think we're all hoping that the old growth rate and stock price will come back.

imo, it's just not going to happen for a couple of reasons. Intel now has a market cap of $126B and is in about the top 30 worldwide. There isn't a lot of headroom there. GE is #3 in market cap with $380B, but they are tremendously diversified relative to Intel. Microsoft is number #4 with $295B, but they don't have to pay for fabs. Fabs cost a lot of money, and they depreciate relatively quickly. Another reason is Intel's stock price during the .com boom was simply unreasonable for a manufacturing company. The market does what it does, but the stock price is at a more reasonable p/e ratio now than it was in 2000. I'd love to see stock back up to $30+ as well. It's going to take a lot more revenue to get it there.

There were some good comments about focal from the In the news II post. I encourage you to read those few comments if you haven't done so. They reflect the diversity of options about focal. One commenter said:

Focal pushes employees to do what will look good at focal, not what's good for the company.

There's no doubt that's true. But I'm not sure it's significantly different at other companies. People always tend to do what's best for them, whether it's sucking up to the boss, or spinning their work to look better than it is, or lying, cheating, and stealing to get ahead. Some people do these things at Intel, just like they do everywhere else.

I'll admit to being very conflicted about the focal process. As an employee, and especially as a manager, I find it an unpleasant experience to go through. Some dislike it less than I do, but I don't know anyone who looks forward to it. The idea of focal is (I think) to put some process and objectivity around an inherently subjective process. It's by no means perfect, and it can be painful, but overall I think it tends to work. It yields results that generally puts the higher performing people at the top, and the lower performing people at the bottom. Generally. Every time I've taking people through focal I've going into it worried about the outcome, and I come out feeling like it was relatively fair.

I really struggle with the idea of forced distributions. I believe this is done largely because most managers don't deal with poor performers. I see this every day. Too often people get swept into a bad category because of a forced distribution. But conversely, far too many poor performers would never be identified if managers weren't forced to do so.

One year I ended up representing three different groups in focal by myself. I don't remember the circumstances, but two other managers were not there to take their people through the process. Most of the employees were in rank groups where I was the only manager representing them. My boss made me prepare work sheets and take them through the process. The two of us sat in a room for 4 hours discussing each person, with her asking hard questions about the deliverables, and my rankings and ratings. And I had to hit a distribution.

The point is that I wasn't able to go off and just do whatever I wanted to with those people. Going through the process made me think about the people differently than I would have otherwise, and it made me identify the (relatively) slower performers. It was unpleasant, but I got to a good result. My philosophy about focal is that it needs to be improved, and the forced distributions need to be reconsidered. I think of it as similar to the system of government in the U.S: It seems broken, inefficient, tedious, and stupid some of the time. But overall it seems to work, and I'm not sure I could replace it with anything that would work better.

Thursday, February 15, 2007

Focalization #3

I'm getting a fair number of questions about the focal process this year. People aren't sure if it's very different, slightly different, or completely different from the previous process, or what this means to them. From am employee perspective focal is about the same. You should have recommend some names to your manager for 360 feedback. You should have done a self-assessment, and by now most of you have reviewed a summary worksheet or draft of your final review with your boss. Employees are now in the waiting period where their manager has likely completed ranking and rating, but they won't know anything until after April 1. For me the process as an employee was about the same this year. The only difference was that my boss wanted my to write my complete review rather than a worksheet.

For managers things are significantly different. Previously managers would go into a room and discuss every person in a rank group, usually between 8-20 people, but sometimes smaller, sometimes larger. Different rank managers used different processes for going through a session, but it was invariably a long, painful process. You needed to represent a years worth of accomplishments for am employee in 2-3 minutes. These sessions were a real power play, with managers negotiating, influencing, and doing a lot of acting to try and get their people ranked and rated fairly. Most managers tended to do a good job. There was usually some asshole in the room who thought his people were more deserving than everyone else's. But with a good rank manager and/or HR person in the room, things were usually kept in check. Depending on the size of your team and the number of rank groups they fell into, you could spend 1-5 days in R&R sessions. I usually spent at least 40-50 hours preparing worksheets, and other 30-40 hours writing reviews. Then there was additional time for figuring out pay increases, dealing with last minute budget or stock changes, and other stuff. It was not unusual for me to spend 3-4 weeks of time working on R&R.

Things could tend to break down in R&R sessions where there was an uneven distribution of power, influence, and bias in the room. I had one boss who insisted on being in all our R&R sessions as an "observer" so he could direct the outcome. It was similarly bad when the rank manager had some obvious bias and would help influence the result rather than just facilitate. The worst rank sessions were those in which the rank manager was representing their own employees. I was actually in one session where two of those happened: our boss was in the room to observe, the rank manager was representing his own people, and both of them had an obvious bias toward the rank manager's team. They were aligned on the result they wanted to see, and the rest of us were working hard to bring a sense of fairness to the session. This was an extreme case, but it's a good example of what's been wrong with the focal process: it often had more to do with a manager's political and influencing skills than the performance of their employees.

This year managers are ranking and rating people on their own. I ranked my team as an in-tact rank group. I had someone at the top and someone at the bottom. Some people are outstanding, some are not performing very well. We are being held to a distribution within our teams - I can't have an unlimited number of outstanding employees, or promotions. And I am expected to identify a percentage as poor performers. This is still a difficult task, especially for those with small teams. But it's far easier than spending days lock in conference rooms with other managers, influencing and arguing to try and get the right result.

We had one 3-hour meeting with my boss where we reviewed each other's results and and rolled up summary for the team. My boss needs to hit a distribution as well, and we didn't. So we had some conversation about who else could or should be given a poor performance message, and who really didn't deserve to get a promotion. Some of the old behavior came out, and some managers were overly defensive about their people. That's always going to happen. Doing this in 3 hours vs. 3 or more days was a huge improvement in process and efficiency, and yielded about the same result we would have gotten with the old process. And we still aren't quite done and will need to spend another hour or two working on our distribution. But considering what we used to go through, it's big improvement. Focal isn't perfect, and still takes up more time than I would like. I credit Paul with challenging the old process and for allowing these changes to take place.

Thursday, November 16, 2006

Focalization #2

There were a couple of good comments to the last post. If you haven't read them, please do so, as they give some good background relevant to this one.

As one of the comments mentioned, focal has changed recently and rank groups are more focused on in-tact teams. The advantage to this is that you don't have managers of other organizations gunning for you rather than their own people. The disadvantage is that your manager now has to hit distribution numbers with his own people rather than going after someone else's.

The basic idea of focal is that the top people get rewarded well, the bottom people get a strong message, and everyone else in the middle gets about the same (typically mediocre) raise and stock package. For the sake or argument, let's say that top 15% of performers get 2-3x better annual compensation, and that the bottom 15% get nothing. That means that the 70% in the middle are treated about equally. The difference in effort between someone who ranked at the 84th percentile vs. the 16th can be huge. But they will get about the same compensation.

My recommendations for focal:

1. Know your peers and know your boss. Focal is all about you being ranked relative to your peers. If you want to be competitive, you need to know what they're doing, how well they're doing it, and what your boss thinks of them. I'm not recommending that you act duplicitously, just that you pay attention to what people are doing and the team interactions with your boss.

2. Know where you are, and where you want to be. Don't work to be near the top. An "almost there" doesn't count at focal, and working your butt off to get near the top will often result in frustration. If you aren't competitive enough to be at the top, or don't want to work that hard, being in the 40-50th percentile is the sweet spot. This generally keeps you far enough away from the bottom that nobody is questioning your performance, but it doesn't have you working as hard as those in the 90th percentile for no additional reward. Knowing exactly where you will fall is nearly impossible, but you should be able to gauge yourself relative to your peers after going through focal or mid-year one time.

3. Write a good work sheet. Over and over I see people turning in crappy, overly verbose summaries of their own work for focal. Your boss will get 2-3 minutes to explain to other managers what you did for the year, and the results and impact it had. They'll also get to cover 3-4 items - no more. So when you summarize your accomplishments, focus on impact. Don't write about what you thought was important, or on what you did particularly well, but what other managers will think was important to Intel. It's all about the result and the impact. If you can put a real dollar figure or some other quantifiable metric, it's even better. If you didn't quite hit expectations for an item, either don't mention that or have a good explanation. If you did better than expected, flaunt it. "Conceived of and drove the xyz project to target and removed redundant servers in Oregon. This resulted in 47 servers being identified and shut down. The program target was $125K in savings, but Bob's efforts resulted in $300K savings for support, maintenance, and licensing." This is short, specific, and demonstrates that you not only hit a goal, but exceeded it.

4. Take advantage of bad mid-year reviews. Not all groups do a mid-year review, and in those that do everyone hates it. But getting a bad performance message at mid-year is far better than getting one at focal. Your boss has an obligation to help you be successful, so if you have a mid-year performance problem, they will work with you to turn it around before the end of the year. It's a reflection on them if they don't. Mid-year documentation tends to be treated informally, so it's far less likely that a future manager will know that you had a performance problem. A formal performance problem at focal will stay with you forever. But here's the real kicker: your boss can take credit for a bad mid-year message at focal. If he needs to have 3 poor performers at focal to hit distribution, and gave 2 messages at mid-year, he only has to find one more at focal. So he hits his target and you don't get a permanent mark.

5. Poor performance messages should not be a surprise. Once focal starts, it can take on a life of it's own and the target goals may force a manager to give a performance message they don't agree with. Or they may think you deserve a performance message, but hadn't mentioned it to you previously. Either way, if you had no idea that you were performing poorly before your review the momentum is in your favor. If you're boss didn't give you an indication that you needed to do anything differently during the year, it's going to be hard to make a performance message stick at focal.

5b. Take advantage of good mid-year reviews. If your mid-year review is good or better, you should expect to have the same review at focal, unless something has changed. If you find yourself in a situation where you did OK at mid-year and poorly at focal, your boss really needs to have given you some indication of this. If not, you have a good argument for reversing the bad message.

5c. Use the open-door policy. Intel has an process that allows you to speak to HR or your boss's boss when you feel you've been wronged. People rarely take advantage of this at focal, but I've seen it work over and over. It won't change a poor performance message that you deserved, but if you were treated unfairly, there's a good chance of it being changed. And people often think that their manager will hold it against them for escalating. That could happen. But sometimes your manager is frustrated at being forced to hit a target, and would welcome HR overturning the poor performance message they delivered.

6. Make a job change if needed. If you're in a group where you can't be competitive, consider finding a group where you can. I've had peers that made me look positively below average no matter how hard I worked. I've also been the rock star in other groups. This is usually up to luck or circumstance, but when possible don't move into a job where where you be the weak link.

Wednesday, November 15, 2006

Focalization #1

I'm going to post a couple of entries about the annual review process at Intel, known to employees as "focal" or R&R, which is an acronym for Ranking and Rating. My goal is to explain how focal works, what problems I have with it, and to give some tips to employees to better deal with the process. Some of this material is going to be obvious, some of it may not. I've been on both sides of the focal equation for several years (as an employee and a manager).

For any non-Intel readers, focal consists of collecting information on each employee from several sources, going through an evaluation process where they are ranked and rated based on their performance, determining compensation, and then giving feedback and results to the employee. A manager collects information from the employee themselves, from peers or stakeholders the employee recommends (and possibly some they don't recommend). They then complete an short written assessment of the employee using that information and their own observations. A manager theoretically has a fairly well rounded view of an employees accomplishments, strengths, and improvement areas from several sources. People are grouped by job function and/or manager into "Rank Groups", and the managers representing the people in a group sit down in a room and go through the written evaluations. Basically, you end up ranking people from the top to bottom (largest to smallest contribution). Being at the top is always good, but being at the bottom is not necessarily bad. For example, if you are junior relative to the others in the rank group, you would expect to fall toward the bottom.

Employee compensation is largely determined based on how well employees performed relative to their peers in similar roles and at similar pay grades. So if people in similar jobs at similar pay grades ranked higher than you did, there would be questions about why you feel below your peers. Similarly, if you were ranked above your peers, you would appear to be doing a better job. At a high level, I think this is a good process that generally does a fair job of evaluating performance. But in practice, there are several pitfalls, and it tends to encourage and reward some bad behavior on the part of managers. I don't know of anyone who likes it.

Your performance is determined based on how you stacked up relative to the other people in your rank group, not by an arbitrary measure. There are some obvious implications to this: if you work with a bunch of overachieving geniuses who live to work, you're going to have a harder time competing than if you work with a people not as highly skilled as you, or who don't work as hard.

Intel pushes the idea of target distributions for rank groups. In general the top 10% of the rank group is considered to be doing better than everyone else, and the bottom 10% is considered to be doing worse. It's a little more complicated than this, and the percentages may be different, but the idea is that a distribution needs to be hit. It's considered a target by HR, and very few people at Intel will tell you that it's a hard target.

I've worked in about 5 different groups at Intel, and had a dozen managers. All but two of them have insisted on hitting our distribution targets in focal. In practice, these distributions are almost always hard targets that need to be hit. Finding high performers is easy - the highest ranked people at a given pay grade are usually your top performers. You start handing out higher ratings to them until you meet your quota. Then you start looking for poor performers. Sometimes you have an obvious candidate or two. But with smaller rank groups in particular, you may not see anyone who deserves a bad performance message.

Because each rank group rolls up organizationally, each org manager will look across rank groups for an average. But if they aren't hitting their numbers, managers are going to be asked to find more poor performers.

This explanation turned out to be longer than I expected. What you need to understand about focal is that just doing a good job may not be enough to get a good review. If you're doing a good job, and everyone you work with is a doing a great job, you'll be at the bottom of the pack. My next entry will cover some ways to help manage this and how to prepare for the process.

Tuesday, October 03, 2006

Do the Right Thing (#1)

During my time at Intel I've experienced a lot of good and some not so good behaviour. I've seen people role model good working values and do the right thing many times. I've also witnessed some bad behavior, and I intend to discuss both over time. I'll start with an exchange that took place a few years ago and, for a number of reasons, was eye opening to me.

A short preamble: I've thought about whether or not I should share these experiences. They're all historical, not current. And I don't expect to change what happened or their effects. But I'm hoping to shed some light on how things can work at Intel, and how individuals can impact them. Keep in mind that any less than ideal behavior I describe is typically exceptional, and is based on the actions of specific people, not corporate policy.

I was a new manager in a staff meeting. I knew most of the other managers on the staff, and we worked for two guys who both managed the team (two-in-a-box). We were discussing the upcoming focal sessions (Intel's annual employee review process). A few weeks earlier we had gone through a skills assessment exercise which was used for downsizing in some groups. Many employees were concerned that the skills exercise would be used as part of the focal process, which would have been a big change.

To address these concerns, HR had made it clear to all employees, especially managers, that the skills assessments would not be used for focal, that people would be evaluated with the standard process. Below is a discussion that took place in this staff meeting. The two bosses were middle managers who I'll refer to as "MM 1" and "MM 2." They considered another manager on the team a cowboy, so I'll call him "CB."

MM 1: To get through focal more quickly, we're going to use the skills assessment scores as a starting point for ranking. It's just a starting point, and rankings can change as we talk about people. Any issues with this?
CB: Well, we're not supposed to be using the skills matrix for focal.
MM 1: Why not?
CB: Because we told people we wouldn't use it.
MM 1: How will they know? Are you going to tell them?
CB: No, but we told people we wouldn't do it.
MM 1: Well, MM 2 and I have talked about this and we think it's the most efficient way to get through focal.
CB: But we're not supposed to do it.
MM 2: I don't see why not.
CB: Because we told people we wouldn't.
MM 2: But they won't know. All they care about are the focal results, and this will help get us done faster.
CB: I'm not sure it's legal.
MM 1: What are you suggesting?
CB: That we don't use the skills data for focal.
MM 1: We'll have to re-design our entire focal process.
CB: If someone challenges their focal results it's going to be a problem.
MM 1: Will you be ok if we call HR and get them to approve it?
CB: Sure.

MM 1 calls our HR rep and gives some background, then asks the question:

MM 1: So can we use the skills data to get first cut at ranking, just to get started?
HR: Absolutely not.
MM 1: But we're not saying that ranking won't change, we're just using it as a starting point.
HR: We told people we wouldn't use the skills matrix for focal. You can't use it.
MM 1: Can we compare our ranking to the skills data to see how it matches up?
HR: No. You can't use the skills matrix for focal.
MM 1: Not even for validation?
HR: No.
MM 1: Ok, thanks.
MM 1: I think we should still use it.
MM 2: I don't think we can. We need to redo our focal process.

I was surprised by several things. I didn't expect someone to challenge their manager(s) and hold their ground. I didn't expect the managers to continue to argue for a something that was clearly ethically wrong. I was shocked when one of them recommended continuing with the plan after being told they couldn't by HR. It didn't occur to me at the time, but looking back I'm surprised that nobody else spoke up, including me.

Watching this conversation unfold was a great lesson for me. Someone took a stand to do what was right, when there was nothing in for him. In fact, all he could gain from this was the ire of his management but he did it anyway. As I've matured at Intel I've tried hard to be more like CB, and it's not easy. When Intel is laying people off, who wants to be seen as the person who tells their manager that they aren't acting ethically. It seems easier and safer to be politically correct.

Intel is far better off when we challenge each other to do the right thing. Bad personal ethics can only exist if we allow them to. But doing this can be risky, and I haven't found the perfect balance between speaking out and being successful.

MM 1 and MM 2 are still middle managers at Intel. CB left Intel a couple of years ago, as did the HR rep who agreed with him.