|
|
|
|
|
by waterhouse
4272 days ago
|
|
I'm curious what you think of Ben Horowitz's "How to Minimize Politics in Your Company"[1]. He gives the specific example of an employee asking for a raise; he argues that responding by giving them a raise, even if it's reasonable, rewards behavior that has little to do with their job performance, which has undesirable secondary consequences. He says that the right way to deal with it is to have a good, regular, and standard process for evaluating employees and adjusting their compensation accordingly. To a person who works at a company that doesn't have such a process, I'm sure your lesson applies. But I wonder what you think about what the company should do. Take the company you worked at as an example: should they have had some process by which they would have measured your performance and come to you (and perhaps your co-worker) with a raise? (More regular and performance-dependant than "+$2k/yr each year if you haven't been fired".) Regarding the main topic of this thread: Perhaps Satya Nadella believes that Microsoft has such a process, and believes that no one should ask for a raise, and gave his advice as though all companies were like Microsoft. (Or perhaps someone has information contradicting this hypothesis.) pacaro's comment below suggests that, whatever else you might say about Microsoft's process, it doesn't reward asking for raises. [1] http://www.bhorowitz.com/how_to_minimize_politics_in_your_co... |
|
As for Microsoft, I have no idea how their process works or if they even reward ambition and results. I did work for a larger company later, 6 months in they gave me a $13k raise and 6 months after that another $20k raise when they made me a manager. I never once brought up my salary, what I did do was point out what I thought was being done wrong and then proposed how to fix it. In this case I went to the CTO as my manager really wasn't managing the product at all, I thanked him for hiring me but told him I didn't think I was going to stay. He asked why and I described what it was we were doing and all the problems it was causing. I then followed it up with a solution of how to manage the product. I did not expect, nor even go in there with thoughts of taking over my manager's job. It was just an honest assessment of how to fix and drastically improve the efficiency of the group. One week later the CTO came to see me, privately. He told me they were very impressed with the work I was doing and they wanted to give me the opportunity to manage the product and the engineers working on that project. The first 6 months were probationary, after that I would be made full manager and get a salary increase. At that company, I never needed to negotiate my salary. They were always generous, they listened and were very proactive in keeping their employees happy.
In general though, my experience has been more like the first job. The companies, while having a yearly review process are very stingy. When it's time to hire a manager they bring in someone from the outside as they don't want to hire another engineer and retrain them.
As for Ben Horowitz's article, I would have quickly left any company that followed his advice. Telling me to wait, the company policies etc. I would see them for what they are, a stalling tactic. I would recognize that I was being "handled". With me I voice my opinion, I lay out the facts. If they are ignored, I don't complain, I don't bring it up again. I just quietly look for a new job, and any counter-offers after that point are immediately turned down. As things have gone according to plan, I don't even have to deal with this anymore, because now I have my own company, products and clients.