I’m working on a project and my computer is quite slow. I would work more efficient and get less irritated if I get a better developer machine.
How can I convince my boss to give me a better developer machine?
|
I’m working on a project and my computer is quite slow. I would work more efficient and get less irritated if I get a better developer machine. How can I convince my boss to give me a better developer machine? |
|||||||||
|
|
You have to sell him the idea. The most powerful sales technique I know is Solution Selling.
Find his pain related to your problem Every single human on this planet has multiple pains. Most bosses pain is related to ROI. When they don't get the productivity (and then money) they require, they suffer a lot. That's your target. You will have to put emphasis on that since this is what you are talking about. Your productivity. Come with a solution & facts You must calculate the gain on time a new machine can provide you. There are plenty article online you can find by googling. Converts the time you gain in money. His pain. Be cautious about the figures you will send to him. He could use them against you. (see Tim's comment below) Conclusion Don't talk about your problem. Talk him about his problem. |
|||||||||||||||||||
|
|
Do a calculation about how much productivity is lost because of your slow machine. Multiply with your salary and show him that the ROI (return of investment) time for a new machine is 2 months. Add "better motivation" and "better response times in case of emergency" as reasons to buy you a decent machine. |
|||
|
|
|
I asked a similar question over on StackOverflow: It is of course specific to Visual Studio. But the idea (the accepted answer in that case) is that you come up with some numbers to which management and non-technical folk can understand. Measure slow machines as well as fast machines in your company. Hopefully they won't all be slow. Depending on the size of the company, your boss (unless he/she is CFO or in charge of finance) will need to give a reasoning to his/her boss behind purchasing new equipment. What you want to show is the time or money it costs the company by not upgrading to faster machines for developers. Idle time, time waiting for the computer to compile a solution, to return data, is generally what you'd want to look for. If you're idle for 30 minutes, 1 hour, or even 2 hours per day waiting for your workstation to finish something. It adds up over the course of a week, month, year, etc. You will want to plot these out. Also, avoid using the term "me". It's not about "you" to a company. It's about the company. If things go well, may end up getting a new machine, and your boss will get credit for saving the company x amount of money. |
|||||||||||||||||
|
|
I just sent my development manager an email the other day where I timed how long it took me to restart my computer, as well as things like opening Visual Studio, compiling, etc. Then I multiplied this by an estimate of how many times per day I do these things, then by the # of working days per year, then by our number of developers, and then finally by our normal costing rate for developer time. The dollar amount of lost time was compelling enough for him to look into getting us better machines. Nothing has come of it yet, but a man can dream... |
|||||||||||
|
|
Buy the new one based on what you want using your money first. Do best your job, show the result to your boss. If your boss gets profit from your job, ask him to reimburse you. I usually do this in my lab. :-) Very fair, isn't it? |
|||
|
|
|
Do a simple trial. If you have some tasks that take a long period of time, that are repeated by other members of your team, show your boss the numbers, and have one person get a real machine. When that person is able to do so much more, then use the data from that test to prove that a new machine for everyone would be beneficial! |
|||
|
|
|
If you work at a small company or if the manager sometimes sits beside you to watch what you're doing, or if you get the opportunity to show him/her something, genuinely show how much time something is taking that shouldn't take so long in the first place. Subtly complain about the machine. If you do it right, the person might "feel" it's time for a better computer. My friend did that once and he got new monitors, keyboard, etc. |
|||
|
|
|
A lot of the answers here relate to making a business case for buying you a new workstation. By all means, make that case. But that shouldn't be the primary argument you should be making to your employer. The primary case should be "I'm frustrated because my computer is so slow". And I'm not just saying that out of some ideal that managers need to cater to all of their employees' desires. I'm saying it because that's the best business case you could possibly make. In the grand scheme of things, the cost of replacing a developer who (presumably) gets things done is by far greater than the $3-4k that they could have spent to get a new workstation. Besides that, what percentage of your income is a new workstation? Hopefully, it's a pretty low one. In other words, the cost of finding and paying good software developers is the greatest cost any software company has to pay. Buying those programmers the tools they need (or even the tools they want) is tiny in comparison. |
|||
|
|
|
I have long since given up trying to convince people about the amount of computing power I need to do their bidding. I will do things with their equipment for a short time, and then what I will often do is bring in my own system (usually, my desktop from home) and sit it next to the computer that they have. Then I sit them down and I show them everything "normal" on their system, and again on my system. My system only cost me about $500 to build, piecemeal, and it runs circles around everything that I have seen in a business environment, even a technicial business environment. It's a sales technique, of course: the Kirby people (you know, those people that come to your home and demo their "home cleaning system"s to you) call this "killing the old machine," and I have found that at least when it comes to the argument for a more modern, reasonably powerful workstation, or for dual-displays, it is pretty easy to "win" by "killing the old machine," which is really about killing the perception that "everything is fine because it's not broken and/or burning up in a ball of flames". |
|||||||||||||
|