<![CDATA[Gawker: valleywag, layoff memos]]> http://tags.gawker.com/assets/base/img/thumbs140x140/gawker.com.png <![CDATA[Gawker: valleywag, layoff memos]]> http://gawker.com/tag/valleywag/layoffmemos http://gawker.com/tag/valleywag/layoffmemos <![CDATA[Tough times, unoriginal blog posts]]> Mahalo founder: "Tough times, hard decisions." Zillow founder: "Difficult times, difficult decisions." Seesmic founder: "Tough times. Tough decisions." The only thing easy in these times is what to headline your post about the employees you just laid off. Also, make sure to note that you are sad.

]]>
http://gawker.com/index.php?op=postcommentfeed&postId=5067396&view=rss&microfeed=true
<![CDATA[Jerry Yang's no-layoffs-yet layoff memo]]> As mysterious to Yahoo CEO Jerry Yang as the location of his keyboard's shift key is the trick to communicating layoffs. Jerry, you should deliver them the way Steve Jobs unveils the latest Apple products: All at once, and tell the audience they can get them now. Instead, in his latest no-caps memo, Yang informs Yahoo employees that 1,400 of them will lose their jobs, but they won't find out any details for "several weeks." Jerry, you're doing it wrong. Here's Yang's latest botched communication to his staff:

yahoos,
 
i feel it's important for me to reach out to you after our earnings announcement, and before our all hands meeting tomorrow.
 
we as a company have been through a tremendously challenging year; and managing the increasingly turbulent global advertising climate has been an important focus for the last three months.
 
throughout the first three quarters of 2008, we have been balancing between investing in our top priorities, and managing our cost structure.  beginning in september, with the help of Bain & Co., we initiated a series of steps to determine how we can become more efficient and productive as an organization.
 
we heard from you through the YEES survey, and through your suggestions on backyard, and we've identified many areas that we all feel we can improve upon.  our productivity efforts, based in part on what we heard from you, will involve initiatives such as streamlining our organizational structure through reducing layers and increasing spans of control, and eliminating redundancies.  longer term structural efficiencies include consolidating facilities, improving procurement, and standardizing our global technology platforms.
 
today as part of our q3 earnings release, we said that our goal is to reduce our current annualized cost run rate of roughly $3.9 billion by more than $400 million before the end of 2008.  we are targeting non-headcount expenses wherever possible, such as facilities and outside services.  however, because compensation expenses are the single largest part of our costs, we anticipate a reduction of at least 10% of our global workforce by year-end.
 
affected employees will be notified of layoffs in the next several weeks.  we understand that hearing this news now creates uncertainty, but we are moving ahead in a way that balances speed with a clear focus on accomplishing what is necessary to set the organization up for long term success.  going forward it will continue to be important for us to make the right decisions to keep our business efficient and strong.
 
having layoffs is very difficult, particularly in light of all we've experienced this year.  but we don't take these decisions lightly, and are committed to treating affected employees fairly, offering severance and outplacement services.
 
the steps we are taking are not easy for us as a company, but as we become more fit as an organization, decision-making will be faster and it will be easier for us all to get more done and stay focused on our strategy. these changes will also prepare us to better deal with the macroeconomic downturn.  as with previous downturns, yahoo! continues to be a place where consumers turn for information and communications, and is an integral part of their internet day.  as the global economy improves in the future, i certainly believe that we will be stronger and benefit from the actions we are taking now.
 
as always, i thank you for all you do as yahoos.
 
best,
jerry

]]>
http://gawker.com/index.php?op=postcommentfeed&postId=5066825&view=rss&microfeed=true
<![CDATA[Layoff PDFs are best]]> A longtime reader sent me this classic post-layoff notice in response to our plea for more crowdsourced content. Instead of just telling me a story in text, he gave me a Word document mailed to all employees, so I could screencap it for you. This would've been an awesome post ... in July, when the doc is dated. Yahoo did everyone a favor by including Valleywag in its training video All Hands, the Movie. The lesson? Tipping us isn't about whether or not you get caught. It's about watching how long those idiots in HR take to figure it out.

]]>
http://gawker.com/index.php?op=postcommentfeed&postId=5062644&view=rss&microfeed=true
<![CDATA[Laid off before sunrise]]> We've got our first layoff-memo story — and it's actually about a layoff conducted without a memo. Read on, and don't forget to send in your own:

I was in the parking lot of the small consulting firm I worked for meeting my boss to fly to Seattle for business. It was 4am on a Monday morning, I was about to pull my luggage out of my trunk, and he laid me off right there. No memo, it wasn't even in the office, and heck, it wasn't even LIGHT outside! Mind you, I left the week before that thinking I had a job. Two months earlier I had questioned if he was going to lay me off and he said, "I have plenty of money to put into this company."

He gave me 2 weeks severance, no insurance benefits (he didn't actually offer plans through work).

At least at Yahoo I'd have my resume a little more updated. Hell, I would have taken a memo if I could have slept in that morning!

After I told him I WANTED it in writing (that he laid me off vs. firing me) he gave me a huge run around, saying stuff like "who's your audience? why would you need this?"

He was shady for sure.

]]>
http://gawker.com/index.php?op=postcommentfeed&postId=5061803&view=rss&microfeed=true