Ask HN: Have you ever saved your employer big money through simple change?
I work in an office and I have to lock my machine when I go away from my desk. 15 minutes after I lock my machine a screensaver kicks in showing all things bank related and after a further half hour the monitor goes into standby. One morning, after being horribly hungover, I noticed that in my vicinity around 25 machines all had screensavers on (the team adjacent to mine were in a meeting). This got me to thinking how much money and energy was being wasted by screensavers alone.
So after speaking to some people and doing various presentations (it's amazing how convulated the process is to change something simple!) it was agreed the company branded screen saver was to be replaced for a blank one (this was needed to ensure the machine was put into lock mode) and monitor standby initiated 44 minutes earlier than the original configuration. This saves 44 minutes of power at 35 watts, where previously the monitor would display a company branded screen saver. With over 100,000 desktops in the estate, this saved energy costs when the PC is not in use in the region of £75k p.a.
From a technical perspective this was a simple, low risk change to implement and was delivered on time and with zero budget (aside from platform development man hours).
I wondered if anyone else had saved money through simple change? If you work for a large company you may also want to ask the question 'do we need a screensaver'!
Would love to hear some of the ways you have saved money for your company!
[+] [-] edw519|15 years ago|reply
- We upgraded our hardware and our forecasting software vendor wanted a one time $600,000 charge. I convinced my boss to replace them with in-house written software. Took 6 weeks to write.
- Our 400 worker factory was $30,000 under-absorbed per month. I wrote both standard costing and data collection software. Supervisors compared the standards to the actuals to discover where they were losing money. We were over-absorbed by $30,000 per month 6 months later.
- We budgeted over $1 million for a new ERP system to "solve all of our problems". I helped others solve most of their problems by identifying them and coming up with solutions from the existing software. We never did buy new software.
- (My favorite). Our HCFA feed from the U.S. Government was broken and no one knew why. I dug in and changed 1 byte of code (1 byte, not 1 line). The next day, our bank account had $6.5 million more in it. I never had the heart to tell them how easy it was to fix.
[+] [-] danilocampos|15 years ago|reply
That's just gangsta. Can you expand on that last story? I can't wrap my head around such a simple problem costing so much.
[+] [-] sga|15 years ago|reply
Seems like you have a real eye for this type of thing!
[+] [-] pavel_lishin|15 years ago|reply
[+] [-] kls|15 years ago|reply
Several consultants had came in and told the CEO that there was no way to graduate out of the system, that it would require a total rewrite of the system. The CEO had went through 3 failed attempts to build a new system with external vendors the second of which folded shop and then the CEO got a call from an Indian company saying that they had been working on the system for over a year and had not goten paid. Apparently the front company that folded was subbing everything to offshore firms without letting the customer know.
Anyway, all attempts failed and the one most critical business issue was that the rates and allotments for hotel rooms needed to be available to customers like Hotels.com, Travelocity, and Expedia in real time. It was a read only problem. I set up an export from fox-pro to a database cluster (I can't ever remember which one now (Oracle or MSSQL). Built some web services on top of it to expose the data and published the WSDL. All tolled we (2 people full time) spent a week building the services and added over 30 million in revenue, the first year. I have done some others, but that is probably my best time to money ratio of my career.
[+] [-] parenthesis|15 years ago|reply
[+] [-] SteveEvans|15 years ago|reply
[+] [-] chaosmachine|15 years ago|reply
One day we started receiving a massive flood of calls all about the same problem: the default ISP homepage wouldn't load, and people thought their internet was broken. The call queue was growing exponentially, and no one could figure out what was wrong. This went on for a few hours, with no solution in sight.
Long story short, while troubleshooting with one of these customers, I found the source of the problem (a new firewall setting in the ISP's free av/fw package), reported it to my supervisor, and a fix was quickly implemented.
Given the volume of calls and the size of their subscriber base, I probably saved the ISP at least 5 digits in phone fees, and got a lot of angry customers off their back.
For my efforts, I was rewarded with a company branded pen.
[+] [-] bsk|15 years ago|reply
[+] [-] mgkimsal|15 years ago|reply
And I bet the person who approved the push out of that av/fw package had nothing come back on them, right?
[+] [-] midnightmonster|15 years ago|reply
The client had just had a customer service issue where one of their customers discovered many months later that her card was still being charged for her subscription even though the card had expired. She didn't know that many cards continue to work after they expire, and had never bothered to cancel her account.
So the client wanted me to make sure that we don't charge expired cards in the future. As far as I knew, this was the first time the issue had come up in the more than a year since we switched payment gateways, so I generated some new reports, and it turns out they had charged almost $4,000 to expired cards just in the previous month. Some of those customers would correct their card data if we notified them, but the reality of subscription businesses is that there's a lot of inertia involved. It's safe to say that the client would simply lose a fair portion of those dollars every month if we stopped charging expired cards with active subscriptions. Much better to refund the one customer/year who complains that they thought an expired card meant they unsubscribed than to forgo all that revenue. Of course they agreed and we didn't make the change.
FTR, this is the same client that a few months ago was complaining that I was the only programmer they'd ever worked with who bills them for email and phone conversations. I'll be reminding them of this case if it ever comes up again.
[+] [-] JanezStupar|15 years ago|reply
Otherwise... A guy that entices his customers to rip-off their customers. Plus he charges for emails written and phone calls made. You make me proud actually you'd make a fine CEMEA CEO!
[+] [-] variety|15 years ago|reply
[+] [-] patio11|15 years ago|reply
[+] [-] city41|15 years ago|reply
[+] [-] pmjordan|15 years ago|reply
For some reason, fixing this situation was not a terribly high priority for those in charge. Someone did create a crash reporter that emailed a stack dump plus any user comments to a central email address. The quota for that account was soon full.
I decided to spend an hour or two here or there on going through the crash dumps. Within a week or so, I'd fixed the bugs causing 99% of the crashes. After rolling that out, we were still getting tens of crashes a day. Fixing 90% of those was pretty easy, too. When I left the company, we were getting maybe 2 crashes a week.
As you can probably imagine, this made me rather popular among some of the artists and designers.
The editor was fairly ancient, they'd been using it for well over 5 years. I can't begin to imagine how much effort was lost in total.
Incidentally, that sequence of events also cured my fear of large, horrible code bases. This thing was written using a proprietary extension library to MFC plus some creative use of DirectX. I think the only code that can scare me now are life-or-death systems.
[+] [-] StavrosK|15 years ago|reply
I wrote a simple CRM web app in my spare time, which every salesperson in the company just loved. It enabled them to see each client's history with a single click.
I asked for a bonus, the manager waved me aside saying "sure, build it and I'll give you $100". I never saw an extra dime other than the $5/hr I was making (I probably earned them thousands in sales that would otherwise be lost, not to mention productivity). They still use the system to this day.
[+] [-] pavel_lishin|15 years ago|reply
[+] [-] SteveEvans|15 years ago|reply
[+] [-] sw1205|15 years ago|reply
[+] [-] singlow|15 years ago|reply
I knew a little trick from my days in the school Mac Lab. I would have the customer flip the power switch, wait ten seconds, then flip it off and back on again (not too quickly). Often I would have the customer stand up and spin around or some other humorous ruse before the second step. The Macintosh would boot up and work fine. I would order a new motherboard battery ($2.50) and the retailer would pay 75 bucks for a tech to go install it. Still much cheaper than what they were doing before.
[+] [-] DevX101|15 years ago|reply
[+] [-] sw1205|15 years ago|reply
[+] [-] perucoder|15 years ago|reply
Using a web app I developed, I suggested removing these numbers from all public sites and advising customers to call the help desk for them. You'd be surprised how much pushing I had to do and how much resistance I faced, especially since I was working in the marketing dept.
Anyway, they finally implemented my idea. Total fraud for 2009 was approx. 300k. For 2010, its approx. 50k.
[+] [-] lotharbot|15 years ago|reply
One day, we completely lost the ability to log in from our building, and therefore, to do billable work for that client (though they had space for 2-3 of our employees to work in one of their offices.) The other company insisted they hadn't changed anything on their end, so it must've been something I did. I did research, packet logging, analysis, and so on, and couldn't find anything. This went on for days. Eventually I walked over to their server room, and found the screens said "Windows 2000" where they had previously said "Windows NT". Apparently they hadn't changed anything except for the operating system on the servers handling logins, which was clearly unimportant and not worth mentioning. Another five minutes of research and I discovered Win2K server used an additional service (triggered from their end) to log in, which was being blocked by their firewall and therefore never appeared in my logs.
I opened one port on my end, their firewall guy opened one on their end, and a problem that was costing us half of our revenue was solved.
[+] [-] rrhyne|15 years ago|reply
[+] [-] rrhyne|15 years ago|reply
Due to the generic nature of some of their keywords, the display network wasn't working for them, none of their users would find them on a mobile, and the timing of their visitors is very 9-5 to name a few of the changes I made.
These specific changes were simple, common sense Adwords settings that many users gloss over or do not address.
My biggest effect on the company was when I dove into their keywords, setup conversion tracking and adjusting the site for lead conversion. I doubled leads, halved conversion costs, etc.
I've since gone through their campaigns granularly and doubled their leads.
[+] [-] topcat31|15 years ago|reply
[+] [-] pbhjpbhj|15 years ago|reply
[+] [-] zackattack|15 years ago|reply
[+] [-] masterponomo|15 years ago|reply
[+] [-] bsandbox|15 years ago|reply
[+] [-] eftpotrm|15 years ago|reply
My former organisation had a collection of MI reports in their core application to let them track any number of sales metrics. These were all decidedly hard-coded and a pain to change; manually added to the menu screen via source code and linked in with Crystal Reports templates. Frankly I don't think anyone in the IT team liked using Crystal, particularly as the reports were largely just straight results tables.
Myself and a colleague were less than fond of this system to put it mildly. I had new business area I was supporting and they needed reports. So, we talked to them about what they wanted and how they'd use them. Discovered Crystal was just being used to export to Excel, so....
One database table was set up to let us bang in new reports without code changes. One class was added to format results sets from the database into a relatively tidy file in Excel.
Total time to do those two changes was, I reckon, less than the total time to add a couple of reports the old way, and gave much faster deployment of new reports. On top of this, over the next few months this business area gained more MI reports than the entire rest of the business put together because they were now so quick to produce. If they needed a new stat and we weren't backed up on something else they could normally get it that day.
Cost savings? New area, new function, almost impossible to quantify. But I'm sure we saved development cost just on the initial set they'd requested, I know we were this way able to automate some reports they were having to do laboriously by hand before and if they couldn't get more sales off the back of the increased range of stats they asked for and got then I'd be disappointed in the sales & marketing team.
[+] [-] GFischer|15 years ago|reply
One of my coworkers found a flaw in the way the company set aside money to pay for the car repairs. He talked to the CFO, and the ensuing change ended up making the company quite a bit of money through interest (definitely much more than 75k pounds).
The technical change itself took all of 15 minutes (a badly written SQL select).
I'm still impressed at how insurance companies (and banks and other financial institutions) can still make money while being massively inefficient.
At least in my country's case, I believe it's a combination of a huge cost of entry and stifling legal regulations, but banks at least are having their lunch eaten on the consumer lending front by smaller competitors (still no good alternative on other services like payroll and big corp. money management which is where the big margins are I guess).
[+] [-] aasarava|15 years ago|reply
So several business departments and the IT department entered into a series of long debates about whether to spend time adding extra functionality to the homegrown search or to just upgrade to something like Google Custom Search / Google Search Appliance -- both options that would have taken a long time, given the bureaucracy at the organization.
Meanwhile, in looking at the site's logfile analyses, I noticed that the analysis software they were using was really good at letting you see stats on GET queries in URLs. A quick look at the HTML for the site's search form revealed that the form was using POST.
I suggested to the IT dept that they simply change the search form to use GET instead of POST and call it a day. Done.
[+] [-] rhettinger|15 years ago|reply
With a five-line change, $250k/yr was saved (you don't have to remit sales taxes for money you never received).