Skip to main content

Opportunity loss by not upgrading

When deciding on an upgrade, whether its a new piece of software, a new computer, or a new process to automate a task, the math is fairly simple to determine if the cost of the upgrade is worth it. To figure out if the price is justified you need to figure out the cost of the tool, the time saved by using that tool, and the cost of the labor gained or lost.

For simplicities sake I will use examples with easy round numbers. Lets say that you have an employee that makes $100,000 per year. Now take that annual salary and divide it by (52 weeks per year, times 40 hours per week, times 60 minutes per hour). You have $100,000 divided by 124,800 minutes worked per year, resulting in $0.80 paid to that worker per minute. Meaning that if the upgrade cost you less per minute saved than that worker is being paid per minute, you should make the purchase immediately and begin saving money.

Lets take a look at some upgrade prices to see how much they cost based on how much work they save.

Minutes Saved per day





Total Minutes saved per year

Again the math here is pretty simple. Take the cost of the upgrade and divide it by (the number of minutes saved per day, times 5 days worked per week, times 52 weeks worked per year). As you can see above, there is almost no reason a $100 upgrade won't be worth the investment. The $1,000 upgrade will have to save your worker at least 5 minutes per day to be worthwhile, and at $10,000 you would need to see a massive savings of 60 minutes per day for that investment to be worth it in 1 year.

There are some additional factors to consider, if the upgrade will last long than 1 year, that pushes the price out over a longer period of time and thus lowers the price per minute saved making larger purchases more reasonable. Just because an upgrade doesn't completely clear the profit line doesn't mean it can't be valuable. Employee satisfaction is a factor that can't easily be quantified and should be considered if the value proposition isn't obviously in favor of making the purchase.

Some upgrades won't be worth the cost, but it takes surprisingly little increase in productivity to justify the purchase of anything under $1,000.


Popular posts from this blog

Converting a Large AngularJS Application to TypeScript Part 1

I work on a project that uses AngularJS heavily. Recently we wondered if using a preprocesser like CoffeeScript or TypeScript for our JavaScript would be beneficial. If our team is going to switch languages, we would need to be able to convert existing code over without much pain and we would have to find enough value in switching that it would be worth the conversion. I had read an article that stated that because TypeScript is a SuperSet of JavaScript, you could convert a plain JavaScript file to TypeScript by changing the extension to .ts and not much else would need to change. I wanted to test out this claim, so I took a file that I was familiar with, an Angular Controller, and tried to convert it to TypeScript to see how much effort it would take and then try to figure out where we would benefit from using TypeScript. This is what the controller JavaScript file looked like to start out with: ( function () { 'use strict' ; angular .module( 'app'

Interns: Taking off the training wheels

My intern team has been working for several weeks now on our new website. We have already completed one deployment to production and are finalizing our second one. We started with a plan to release often adding small bits of functionality as we go and so far that plan has been working really well. We already feel like we have accomplished a lot because we have completed many of our project's requirements and should easily be able to complete the rest giving us time to do even more than just the original requirements. One of the things I have had some difficulty balancing has been how much to lead the interns and how much to let them figure out on their own. In deciding what our team process should be and how we should allocate our time, I think it was important for me to do more leading. I saw some deficiencies in how we were currently working and brought up some ideas for how we could address them. We had moved into spending all our time just working through stories and did not

My idea for Hearthstone to add more deck slots

Recently someone asked the Blizzard developers for more slots for decks in the game Hearthstone. The response was that they are talking about it and looking into it, but no decision has been made yet. One of the concerns over adding deck slots is that it could complicate the UI for Hearthstone and make it more difficult for new players to understand. I have what I think would be a good solution to add more deck slots without increasing the learning curve for the game much if at all. First I would take a look at the current selection screen for starting to play a game. It defaults to showing the decks that are custom built by the player if they have any custom decks, and there is an option to page over to the basic decks. This basic deck screen is perfect for how I would change this process. Instead of having 2 pages of decks, 1 for basic and 1 for custom, you would just see the select a Hero screen. Then once you selected the Hero you wanted, you would see all of the decks that