Monday, December 29, 2008

No Layoffs at Microsoft, and a Round-up of other Recent Comments

NO LAYOFFS: first, I think it's fair to give some time to comments in the last post that wanted to absolutely dismiss any sort of Microsoft layoff rumor, starting off from one from 12/28/2008 (various comments edited to be condensed a bit):

NO LAYOFFS @microsoft

Yes, Executives are looking for measures to cut cost. And that can be done without any layoffs. Current hiring rate is slow at MS and considering the natural attrition, we will have lesser workforce at the end of FY09.

We are not immune to recession and our bottom line will see a hit for few quarters. We expect a full recovery by FY10 Q3. We are very optimistic that this recession is an opportunity for us and we will play our cards well. Urge all Microsoft employees to stay focus and keep doing the great work. You will hear more from SteveB soon on his plans. Thank you !!

and another from 12/27/2008:

For the last time folks -- THERE ARE NO LAYOFFS HAPPENINGS IN JANUARY..[...] beyond Jan...well we dont have a crystal ball -- but if the economy doesnt improve and the company misses targets -- it would get uglier for everyone -- from no raises/no bonuses to {maybe}cutbacks/layoffs... but then, those are the rules of the game in corporate America..

so for now -- enjoy your holidays, have a new year blast and then get back and work your ass off in the coming months --- for the overwhleming majority of you there -- things would be just fine!!!! PLEASE DONT PANIC!

From 12/23/2008, a more likely scenario that feels like a layoff but gives corporate cover:

MS will not do straight layoff. It will re-org, and cut groups/projects. Say 2000 FTE are given 4 weeks to land a new job within MS, I bet 1500 will find nothing and will be forced to leave. So no layoff, let's call it "reorg-off" and MS can even save layoff package.

In-line with that, from 12/21/2008, bringing up an interesting point about H1Bs:

[T]his company simply could not go through a round of layoff (mind you I did not say a RIF, as we've all seen those) but the H1-B rules would force all of the cheap labor to be shown the door first, regardless of ranking. And Microsoft lives for ranking. Microsoft wakes up in the morning and get an enormous boner over rankings. So don't suggest for a second that there is some dismal, far reaching lay off coming down the river. Microsoft would never give up the chance to use selecting RIF'ing to demote the lowly ranked. If anything there will be selective investments, as has been stated time and time again. But no, Microsoft will not be showing the H1-B employees the door. Never going to happen, in my opinion.

When is a layoff not a layoff: which teams are at risk to re-orgs / cut-backs / RIF'ing? This comment from 12/29/2008 talks about Entertainment and Devices:

We (E&D management) had a meeting with Ballmer around eight-weeks ago. Ballmer discussed the GE approach to laying off the bottom 10% every year. When asked how Wall Street would respond to our layoffs, he said they would be happy.

We will be handing out a list of names to teams within E&D. This list will contain the 20% / Exceeded from the last review period. Teams will cherry pick who they want.

The original plan was to announce the layoff prior to Christmas. When we notified the [governor], we were asked to hold off until after the holidays.

Other things going on (from 12/27/2008):

  1. Several big customers have not renewed SAs. This isn't just Vista, but also Exchange and other major revenue-generating products. Several contracts are going from being in the top-5 to zero. 2009 Q1 and Q2 are going to be horrific.
  2. The whole worldwide economy is in a major slump. Toyota is losing money, for crying out loud. Microsoft leadership is working very hard to avoid mass layoffs -- unlike many other software companies that are cutting even if they don't have to. There's lots of creative thinking going into finding ways to cut costs without harming employees.
  3. One of the more likely solutions to be employed is no bonuses in 2009 reviews. What are you going to do, quit?
  4. Hiring is way, way down. Except for a scattered few positions here and there (SQL Server, Live Services, Search, etc.), Microsoft has almost no openings for external hires.

From 12/24/2008:

One of the "rumors" I've heard around the watercooler is that we are looking at a 10% layoff, and part of those heads will come from the open headcount that is out there.

I'm on one of the teams that are still caught in the middle of a re-org that keeps getting postponed and our Director has told his direct reports to start looking for other positions. Outside of that, nothing has funneled down to the individual teams.

Contractors are being dropped (from 12/22/2008):

I have been asked to let go of two of my contractors end of the month even though they have a month remaining in their contracts. Funny because on Dec 1 we were talking of renewing their contracts. Something big seems to have happened in the past couple of weeks, I suppose. However I still see our Director of Development hanging on in the team despite having no work. He was removed from the team about 6 weeks back and has no one reporting to him or no say in the product.

Regarding what's going on the the Field (12/22/2008):

Thanks to the wonderful mergers in the financial world…Technical Account Managers at Merrill Lynch, Wachovia, and Morgan Stanley were kicked out of those accounts. In central region the automakers basically kicked every Microsoft rep/engineer/consulting out till Mid 2009.

And let’s talk about the rest of the field…ya know the people who support our customers and our products….people in Premier/Consulting/DPE. As our customers are cutting back our PFEs and consulting FTE’s have been forced to fight with each other on getting meager engagements with customers. Services management was talking as recently as August about hiring upwards of 2000 in FY08.

Now with so many people sitting on the bench and not engaged at customers…is it the fault of the services employees or Corp’s fault for over hiring? There have been several internal calls within the last week where RIF planning was discussed.

Comment from 12/22/2008 regarding Microsoft Advertising:

Rumor confirmed from Microsoft Advertising. There are several areas within the organization that I can confirm an upcoming "reorg." Leaders of undisclosed groups have been asked to represent materials around their groups' long term plans and feasibility. I think this one is going to be big, hopefully they just cut the fat. There is plenty of it from my experience.

On cost-cutting:

Groups everywhere are being forced to cut costs - but good thing the Zune guys had a nice holiday party. At least they're profitable so they can cover the costs... oh wait. Probably cost as much as the annual salary of a couple L60-61s

And to the commenter about Robbie's group being on a hiring freeze for awhile - true, but the only reason they got there is because of "crazy hiring"... 800+ people in Zune alone?

Teams not at risk? Office seems to be at the top of that pile. OfficeGuy writes on 12/29/2008:

Layoffs: Office and Windows are unlikely to reorg/lay people off in the near future and are [relatively] safe - we need to ship a high quality product soon (and we will this time, no doubt), so losing even the bottom 10% or whatever could have a negative effect on these two cash cows (and it is too late to replace the fat with new blood this late in the cycle). Having spent a few years in Office I can say that this org is huge but I haven't seen real slackers or dumb useless people (maybe I'm just lucky). By looking at my team that has a lot of junior developers/college hires, I'd hate to lose even the bottom 10% - all these folks do try hard and the team is really respectable in Office.

Office again (from 12/22/2008):

College recruiting (at least in Office) is still firing on all cylinders - managers are being told that there will be a seat ready for every great college candidate we want to hire. The pool of highly qualified grads desperate for a job is as deep as it's ever been in recent years.

So if that is true, I'm skeptical that MSFT will announce anything that even remotely sounds like layoffs. Can you imagine the lawsuits if people are ushered out one door with a pink slip while fresh college grads walk in the other door?

Instead we'll see tightening of performance standards and aggressive managing-out of the low performers. The last thing anyone is going to call it is "layoffs"...

One commenter from 12/22/2008 warns:

Don't assume that firing 10%'ers == 10% cost cutting - it doesn't. To reduce salary costs approx 10% requires cuts into the bottom of the 70% bucket too.

January 15th: so do I think anything is going to happen January 15th? Well, it is after CES (we certainly don't want any bad news before that - though look carefully at the groups there and not there) and before quarterly results (no bad surprises delivered with results - check). But after the rather alarming attention the previous rumor-driven post got, even if something was going to happen January 15th I'd completely expect that's off the table now. Sorry, Oppenheimer & Co.

Gossip Grrrls: did I hear any solid facts during all the snow parties I slushed around at during the Christmas holidays? Nope. Just still a bunch of second hand rumors, probably filtered through people's own agendas and likes and dislikes. Stuff like:

  • Pffft, layoffs, come on! That jerk-ass blogger. Don't-worry-about-it, it's just the loss of open headcount and no backfill for attrition.
  • It's not just the bottom 10% being moved on but also folks in the lower Achieved/70% range (like people who worked themselves up from 10% or are on the way down to 10%). A commenter above had the same observation.
  • Some products and some teams are just gone.
  • Note that we've read a lot of comments about Entertainment and Devices and Server and Tools. All the gossip I hear swirls around them.
  • Prototype, redundant, and pie-in-the-sky teams are going to be re-org'd into everyday meat-and-potato teams. We're going to have a bunch of spare code names soon.
  • It's a layoff masked as rhythm-of-business reorganization plus performance management plus Not To Exceed staffing budgets being strictly enforced.

That last point is interesting around labor laws that I don't begin to know anything about, laws like when a layoff comes that the H1B hires are supposed to be the first to be let go and the Working Adjustment and Retraining Act one commenter brought up. If this is a stealth layoff due to a lot of RIF'ing and those people leave because there are no matching open positions, does Microsoft have legal cover against this being an honest to goodness "layoff?"

I think a requirement like having to shed all the H1B hires absolutely nullifies Microsoft doing a classic layoff. We just wouldn't let go of those people.

Oh, and in closing, the following question came in with a comment from 12/27/2008:

Mini - the entire premise of your blog is that MSFT needs to reduce in size, be more efficient, be more cost-effective. While the reason is not the ideal one (forced upon MSFT by outside economy, rather than developed as part of smart strategy), the end result will be the same. If MSFT is a capable company at its core at all, it will survive, evolve and thrive.

If there truly is a round of layoffs, and MSFT ends up becoming the leaner, meaner, smarter, more innovative company you wanted... shouldn't you be ecstatic?

It's a pretty tempered ecstasy. Yes, I want a smaller Microsoft because I believe that Microsoft has exploded in size for no good reason. Going back to 2004. Even with the continued hiring binge since I started this blog, I had a small glimmer of hope that reason would be seen and discipline enacted to hire a limited set of high caliber contributors - and flush out the employees who are better suited working elsewhere. That never happened. And now we're in a, "golly-gee-wilikers the cash ain't coming in like it was and we've done gone and hired all these people! Yeep! How'd that happen?!?" mode.

In a year, when this all passes, we'll be back to hiring like crazy, learning nothing. Unless the leaders at Microsoft that run tight, well managed organizations can step up during this time and flush out the binge-hirers. There's my little glimmer.

(Edit: put in links to the appropriate sources for the comments I quoted above.)


Sunday, December 21, 2008

Rumors of Upcoming Microsoft Cut-Backs

Rumors. Microsoft layoff and cut-backs and Reduction In Force rumors. That's all I have for you. Rumors and second-hand speculation and the comments left by the fine, good-looking folks who participate in the conversation here. So pour yourself some holiday cheer and dive in.

What have those fine folks been sharing over the past couple of posts here? Bad news on the rise and with perhaps January 15th 2009 as an interesting day for Microsoft news. Bad news. 15 Jan is a week before FY09Q2 quarterly results and it's better to share as much news, good and bad, before the results are released vs. surprising Wall Street (something I think we've learned).

It all starts with...

Just heard on the finance grapevine. MSFT layoffs are coming on January 15th.

They are substantial.

And then some curious meetings:

they lost 12 people in STB [...] looks like "feedback" reviews are underway to get the a-10's out of the picture as well.

What kind of meeting? Perhaps like:

I got invited into one of those special "manager" meetings on thursday which resolved to absolutely zero activity other than asking opaque questions for which the answer was already known.

"fact" finding in order to dismiss an argument OR dismiss me :)

shall find out 1/15

In Live Meeting:

Live Meeting is one of the worst places to be right now - and it has gotten downright hostile and strange in recent times. People are pulled into meetings with management where they get interrogated about what they are working on ("We want to hear what you think you know about XYZ, this is not a knowledge-sharing session..."), people are given impossible tasks like coding things not yet designed, automating things not get coded, documenting unfinished ideas (all subject to being cut next week too). On top of that they must account for their time by the hour. Live Meeting is in its death throes.

Breaking-up when you have no budget is another tactic (in STB):

Our 120+ person org has just been broken up due to lack of budget. About 1/2 the team is staying, the other half is going to a number of different teams within the larger org. So far, we all appear to have jobs, but man, what a shocker, I thought ours was one of the more stable teams.

Not sure what happens to our Director, he seemed a bit shocked himself when he delivered the news today. I also don't know if this is the first step towards a lay-off, but for now, it seems we'll have jobs for a few more months.

Ugh, not good, not good at all.

STB again:

I got pulled into a lunch 2:1 today and got given good news on "you have 4 weeks left"

STB - > Server

Rumors! Like the following that I've heard wandering around chatting with folks before the holidays:

I've been hearing some stealth layoffs around the SQL and BOSG groups, around 70+ people were given 6(?) weeks to find another position within the company, otherwise they are laid off.

Anyone know others?

Is the following a list of head-count cuts or expected percent cuts?

  • 3 in omps
  • 9 in stb
  • 12 in msd
  • 7 in devdiv
  • 18 in UA
  • 5 in MSX

Beyond product groups:

Finance is cutting 10% of work force.

I will agree that we'll be casting a hard eye at consistent 10%-ers during MYCD:

If you have to 10% an employee who was in this bucket last review you may well find yourself showing them the door. This means that we can meet VP goals of no lay-offs (we are pruning poor performers) yet be seen to be reducing OE

But who is taking the cut?

The news is in. All the money making groups cut 10% of the work force. The money losing groups hires.

Vendors get it, too:

Vendors are also having it bad. The funding for our project stopped and our vendor team of 28 people have been asked to leave immediately. All of us have been asked to move to India by our parent company. [...]

Who should be taking a cut? One commenter points to GFS:

Do you know who was killing Microsoft economically from past several years- think think think? Being one of the 65 level in this organization and spending most of my career here - I can tell you that this group was living lavish life from past many years (thank god – we have some economic crisis now and people are asking some tough questions from the managers here). I know many of you have already guessed and you are right - this group is called "GFS - Global Foundation Service" and DebraC is leading this group. (Did I use the word leading?) If you want to know how capable she is to lead this group, I encourage you to watch her latest all hands streaming that you can find on MSW. [...] There are billions of dollars hardware purchased every year across this group without any planning and I can assure you that 50% of them are not even used or required at first place. Most of the hiring in this group is not for getting things done or being innovative in datacenter world but each manager here trying to build their own empire by just hiring whether they really need it or not.

Local impact? One commenter muses:

As someone whose product was recently whacked, I sure hope there are some RIFs before there are out-and-out layouts (at least in my area!) Scary... 'cause in this climate, it's going to be darn tough on the economy to dump a bunch of talented folks to the curb and have them competing for slim pickings out in the rest of the world. The ripple effect on the Puget Sound economy alone (assuming the layoffs are substantially here) would be staggering. :-(

Okay. So first I'd love to hear what you have heard or know as well, though I realize some of you might want to stir the pot with made-up fluff sprinkled with schaedenfruede - please don't.

Second: you have to realize that the upcoming 2009 Mid Year Career Discussion review process is one of the most important career inflection-points for you that we've had in a long, long time. Already my team is being asked to review people on the HR Watch List deeply and especially look at any two-time-plus 10%'s, no matter whether they are Situation I (eh, should be fired) or Situation II (effective but have reached their career maximum - again, a horrible, horrible concept). The upcoming Stack Rank for Mid-Year is going to be super-important for determining who has to go first if your team is given an n-percent budget to cut-back on. And yes, if we fire the current 10%'ers we drop down the lower 70%'ers into the 10% bucket. So just because you don't end up in the 10% bucket don't get all happy about yourself unless you're well into a high Achieved / high 70% bucket.

My suggestion to you: know when your team's Stack Rank (aka Calibration) meeting is and be very aggressive about enumerating your accomplishments this past year with your manager and asking your boss where they believe you rank within the team. Hey, I hate this system too, folks, and by me giving you advice I'm trying to prescribe some preventative medicine, not endorse the lifeboat drill that is Stack Ranking. And if you have Skip Level meetings with your upper management, you'd better figure a way that you walk out of that room with them loving you.

And if you get your six weeks, you're going to have to depend on your existing Microsoft networks. Folks I know with open positions have really ratcheted up their choosiness about who they want to bring into their group and are exceptionally uninterested in unknown RIF'ed people wanting informationals, assuming that they are 10%-ers.

Third: let's say we are having intensive cutbacks and/or RIFs and layoffs. It is absolutely essential that Microsoft steps back and asks, "Whoa, how did we get here and who was leading us?" How did we go on a drunken hiring binge and continue it even though a year ago most of us realized we were dropping into a recession? It's irresponsible leadership. It's especially irresponsible to the people we've hired and to the people incoming with recent offers. If you don't think too deeply, it's easy to be sipping on your Starbucks in Crossroads Mall typing away at how Microsoft needs to mass fire people so that it can refocus on essential business. But when you do it at a time when the economy is in the crapper and job openings at Microsoft is near nil is unforgivable.

An important consequence is to ensure we never do this again. The first step is to cut out the people who got us here, especially by making weak hires. Everytime someone who you said "Hire" to on an interview loop gets a 10% review your ranking on hiring goes down. If they become good attrition you get dropped from interviewing. You obviously aren't a very good judge when it comes to hiring for Microsoft. Likewise, if you said "No" to someone with a bad review or "Yes" to a star performer, your ranking goes up. And all of this is made very clear to you, versus you wondering one day, "Hey, how come I haven't been on an interview loop in a while?"

Next, if you've been in the way of quickly load balancing within your division according to needs vs. empire building: *poof* you're either gone or demoted.

Come 22 Jan 2009 Microsoft will be asked by the analysts what it is doing to contain costs. And I believe Microsoft will have an answer. I think this is one solution that you don't want to be a part of. I'm all for cutting back, but it should have been done long ago, responsibly, vs. forced upon us. Because I believe when things turn around, groups will be lighting the sparklers and cracking open the Kristal and hiring madly again.

(Edit #2: added links to all the comments I quoted so that readers - especially first time visitors - understand the source material. Edit #1: fixed a double paste.)


Tuesday, December 16, 2008

Supply Chain Management in Dynamics AX - a new Microsoft blog

For quite some time now, the MDCC (Microsoft Development Center Copenhagen) team has been nurturing the idea of launching our own blog about the Supply Chain Management area in Microsoft Dynamics AX.

And yesterday, it finally happened!
We posted the first article about Quality Management upgrade process for TQM solution (by Fullscope) users.

http://blogs.msdn.com/DynamicsAxSCM
http://blogs.msdn.com/DynamicsAxSCM

I recommend all of you to add this link to your favorites, as we plan to post on a regular basis, and about things important to all of you. That said, I would like to invite all of you to post article ideas or questions related to Microsoft Dynamics AX SCM modules as comments to this message or directly on the SCM blog. We, in turn, will try to cover those in our blog posts.

Thursday, December 11, 2008

Tool for protecting your Dynamics AX source code

"Is there a way to protect/hide my X++ code?"
People asked me this question a million times by now.

To most of them, I described 2 possible ways to go, that I know of:
- Do not share the source code, but instead provide the customers with an AOD file.
- Use a tool that would produce obfuscated code out of your modifications.

Both ways are not perfect, of course. If you provide the code as an AOD file, you need to be sure that the customer does not have X++ license. If you provide obfuscated code, the customer developers (if they are present) will have a hard time interacting with your code. And, eventually, both ways leave the customer at a disadvantage. As soon as the vendor is not there to support (provide fixes in terms of an updated AOD file or XPO with obfuscated code) them for whatever reason, the customer has no way of supporting the add-on solution on their own.

But this post is not about the cons of trying to protect your code.
It's about the possibilities. Today, finally, I can support my previous suggestion #2 with an actual link to such a tool: Next Innovation Code Scrambler Homepage

Here is a screenshot of how the code looks after Code Scrambler is finished with it:


Note, that the tool is not free, and I have not actually tried it out.
But there is a sample project showing the resulting scrambled code. You can download it for a first impression, and contact the company if you are interested in the tool.

Another note - this is not an advertisement, I am not in any way related to Next Innovation Company.