Quantcast
Channel: Business Insider
Viewing all articles
Browse latest Browse all 67596

AOL CAVES: Tim Armstrong Restores The 401K Plans For Employees (AOL)

$
0
0

AOL is restoring its policy of offering matching 401ks to employees without any catches or wrinkles: 

For the past week AOL has been dealing with the fallout of changing its 401k policy

Instead of matching employee contributions to 401ks when employees invest in their 401k, AOL was planning to match 401k contributions at the end of the year. 

This was bad for employees in two ways. 

If an employee left mid-way through the year, then the employee didn't get the contribution.

Or, if an employee stuck around, the employee was missing out on all the gains in the market for the year. So, it was basically a pay cut. 

The 401k issue was upsetting enough on its own, but CEO Tim Armstrong made things worse by misspeaking on a conference call with AOL employees. He had a gaffe, and made it sound like he was blaming the 401k changes on Obamacare and two babies.

To illustrate that despite the fact that AOL was changing its 401K policy, it still cared about employees, Armstrong told a story about two women at AOL who had complicated pregnancies. As a result of the extended care for the women, AOL paid $2 million "above and beyond" what was necessary.

Instead of just saying that though, Armstrong said that Obamacare was going to add $7.1 million to AOL's costs. That extra cost plus the costs of supporting unusual cases like the two women that had complicated pregnancies meant that AOL need to find cost savings elsewhere, and so AOL was changing its 401k to protect itself.

To employees it sure sounded like Armstrong was blaming two women for changes to the 401k.

Sources at AOL close to senior management insisted that Armstrong just goofed and he never meant to blame employees. 

Whatever his intentions, AOL's staff went into a state of revolt. Employees were sending letters to Armstrong, and AOL's Huffington Post was giving it big coverage.

As a result of the outcry, Armstrong changed his mind and is restoring the matching 401k.

Kara Swisher at Re/Code has the letter. Here's Armstrong:

 

AOLers -

 

We began our journey together in 2009, and for the last four years have had an employee-first culture. As I have said before, the ability to change is a strategic advantage for us. With benefit costs increasing, we made a strategic, financial decision last year to revise our employee matching 401K program from a per-pay-period contribution to a yearly lump-sum contribution. We then communicated this decision in the fall through multiple channels to every AOL office in the US.

 

The leadership team and I listened to your feedback over the last week. We heard you on this topic. And as we discussed the matter over several days, with management and employees, we have decided to change the policy back to a per-pay-period matching contribution. The Human Resource team will be in contact with all employees over the next week to explain the change and to answer any other benefits related questions you might have. We are proud to provide AOLers with a robust benefits offering that spans from exceptional healthcare coverage to 401K’s to AOL fitness programs and beyond. On a personal note, I made a mistake and I apologize for my comments last week at the town hall when I mentioned specific healthcare examples in trying to explain our decision making process around our employee benefit programs.

 

Thursday we announced an outstanding Q4 and end to our fiscal year. More importantly, it validated our strategy and the work we have done on it. AOL is positioned for future growth and our long-term strategy to be one of the world’s leading media technology companies.

 

Now, as we begin 2014, let’s keep up our momentum. Thank you for the great 2013 year and for your ongoing passion. And know that I am a passionate advocate for the AOL family – TA

 

Join the conversation about this story »


Viewing all articles
Browse latest Browse all 67596

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>