Microsoft's 'Cannibalistic Culture'
theodp writes "In the provocatively titled Microsoft's Downfall: Inside the Executive E-mails and Cannibalistic Culture That Felled a Tech Giant, Vanity Fair offers a teaser for a story that will appear in its August issue on Microsoft's Lost Decade, which promises an unprecedented view of life inside Microsoft during the reign of Steve Ballmer. 'Every current and former Microsoft employee I interviewed — every one — cited stack ranking as the most destructive process inside of Microsoft, something that drove out untold numbers of employees,' contributing editor Karl Eichenwald writes. 'If you were on a team of 10 people, you walked in the first day knowing that, no matter how good everyone was, 2 people were going to get a great review, 7 were going to get mediocre reviews, and 1 was going to get a terrible review,' says a former software developer. 'It leads to employees focusing on competing with each other rather than competing with other companies.' Also discussed is the company's loyalty to Windows and Office, which induced a myopia that repeatedly kept Microsoft from jumping on emerging technologies like e-readers and other technology that was effective for consumers. Having seen an advance copy of the full piece, GeekWire offers its take on what it calls an 'epic, accurate and not entirely fair' tale."
That may be the mother of misleading book titles. Microsoft has lost a step in some areas (as much due to Apple's ascendence as anything MS did wrong), but this sounds like one of those apocalyptic books you see about finance ("The Coming Great Depression" and stuff like that). It's essentially a tabloid headline on a book cover.
Life is hard, and the world is cruel
There's one number that isn't bigger than last time: the amount Microsoft is charging to upgrade to the new version of Windows.
What does that tell you?
...and it has the same results. Law schools grade this way. It simply adds a very real incentive to undermine those in your group. It forces competing against one another for individual gain, often to the detriment of group progress.
It sort of makes sense for law students whose focus will be litigation, since they are training for an adversarial environment. It also ensures that the lowest performers are consistently swept out.
However it rests on the assumption that the lowest performers are necessarily and always detrimental to a group overall. This of course isn't true, since every single group will have a highest and a lowest performer. The other downside is of course that it promotes individual interests over group interests.
MS has always hired some of the best and brightest, but for years the output has been unable to match. So if you have top people, but you can't produce stuff people want than what is the issue? Management. Duh. I know, and I'm sure many others do too plenty of smart people in the biz. The difference between the Apple, Google, and MS guys is slim at best. But what gets produced is obviously not favorable to MS in quality or innovation. Innovation to Balmer seems too "out of box" and scary to be worth it, so instead he comes late to every. single. party. in the last 10 years.
They had very similar performance reviews at Enron
We had something like this where I worked for a couple of years. It's gone now (at least, nobody talks about it), everyone hated it from the middle managers on down. It was based on the "lifeboat", which they mention briefly in the article. The term I got from the article "learned helplessness" is so perfect I wished I'd known it when this was going on.
The first year they ranked everyone in the same "grade" together. If your manager tried to do what HR said and rank people then there would be a few other managers who said everyone on their team was perfect, and therefore you'd get pushed to the bottom of the list for raises. Also, unpopular or inexperienced managers would get their entire team screwed.
The second year it was just among members of your team but the managers HAD to have some percentage who sucked (who would get the ranking you were normally given before you got fired). It didn't matter if that person was productive or not... their thinking was every team must have a slacker who can be fired. Small teams were the worst off here.
HR sucks everywhere.
Go to
and set it to 10yr, Google even lets you compare it to the Nasdaq and Dow Jones averages (putting your money into a fund that tracked the Nasdaq over the last 10 years would have netted you 100% more money than MSFT stock).
As a former Microsoft exec, my observation was that most blue badges above level 62 spent 30% of their time on work and 70% of their time maneuvering
This concept was foisted upon the world by former GE CEO Jack Welsh. It has ruined one company after another and is an example of the cure being worse than the disease. Watch out when your company hires in HR people from places like GE, IBM, Microsoft, Nortel, AT&T, etc.. They will try to get a promotion by implementing a slightly different version of this which will have about the same results.
Wansu, th' chinese sailor
A summary of an article about a story about an as-yet-unpublished article.
What a wonderful world.
You are welcome on my lawn.
We had the same at HP - if you got the bottom ranking twice in a row you were asked to leave. We had a stable team of 10 engineers, all of which were good at their job but one had to be ranked as incompetent.
We working through the list alphabetically, so everybody got it once in a while but never twice in a row.
It was great for five years or so, then the third generation of this family-owned started flexing their muscles, invoking a new unsaid policy that unless you could prove otherwise, the assumption was that you were a lazy goof-off who should be demoted or fired.
Thus was born the semiannual evaluations from hell process.
I would typically spend 20-40 hours applying loads of manure to my evaluation in an effort to be spared the axe. So would every other salaried employee in the billion-dollar company. This was time that could have been used in improving our production numbers via technology (I was an intranet developer). Instead, we had to slather our way though an incomprehensible eval process that forced us to make predictions based on absolutely no data. Basically, we had to try to read the minds of a couple of dysfunctional family members who now found themselves in officer positions.
They probably couldn't get warehouse worker jobs for Wal-Mart, thank God (for them) that they were members of the family.
I've been gone about a year now, others are going over the wall as other jobs make themselves available. The company has managed to grow in a bad economy, but when things get better, I predict a Microsoft-like turn for the worse, as folks who can afford Hostess or Dolly Madison snack cakes leave in droves.
I'm not saying that the psychotic salaried evals are causing the downfall of the company, but they certainly are a barometer of how things in general are going. Just like Microsoft.
According to Wikipedia: Decimation (Latin: decimatio; decem = "ten") was a form of military discipline used by officers in the Roman Army to punish mutinous or cowardly soldiers. The word decimation is derived from Latin meaning "removal of a tenth".[1] A unit selected for punishment by decimation was divided into groups of ten; each group drew lots (Sortition), and the soldier on whom the lot fell was executed by his nine comrades, often by stoning or clubbing
OK a valid if harsh form of management, but note the critical distinction that the Romans reserved this very harsh technique for unusual events. They were not dumb enough to do this to every unit on a routine basis!
Your odds of surviving thirty years of this is approximately zero. Everybody has an off year eventually. Once people realize that, their commitment also goes to zero.
Help stamp out iliturcy.
When using a review system like this, few things are more valuable to a manager than some really terrible employees.
Imagine I have 2 amazing developers in my team and 3 very good ones, and the ranking system is going to force me to give one a bad review: It will not only make that one very good developer mad, but sour things for the other two, that have to keep beating the poor sob I randomly chose as the one getting the bad review. However, what if I transfer one of my very good developers to a different team in exchange for a worthless chump? Give the chump nothing important to do, and then the rest of your team can continue unhindered and unafraid of getting an awful review just because they are associated with a competitive team.
I used to work at a place like this. If a new hire was just way too good, he was moved to a different team that had lost a top performer, and team quality was kept relatively even: We had to protect the good developers we had. Any team that was too good just had to be split up, or they'd quit anyway.
To be fair to Microsoft, the "Cannibalistic Culture" is alive and well in many other corporations
However, this does not mean M$ does not suffer any damage because of it
I'll just take one example - Michael Abrash
http://en.wikipedia.org/wiki/Michael_Abrash
He is the author of the book "Zen of Assembly Language Volume 1" published in 1990.
Mr. Abrash worked for Microsoft, twice - and at both times, had come face to face with the cannibalistic culture inside Microsoft
FYI, Mr. Michael Abrash is not a run-of-the-mill programmer
This guy is a super top notch programmer
He could have contributed much more of his talent to M$ had the cannibalistic culture is not so prevalent there
Muchas Gracias, Señor Edward Snowden !