Skip to content

Comment on Jeff Bezos Taught Me When to Quitparent

Comments

@larsberg's comment tells me (as an outsider) why Microsoft will die. It has the corporate equivalent of arteriosclerosis. Whether theirs products are good or not is beside the point.

All companies are both predator and prey. With inscrutable insider rules like this Microsoft cannot move fast enough to survive as either.

I was recently reading what I had written about Microsoft, Sun Microsystems, and Oracle in 2004 as part of a business plan. My outlook for Microsoft was simple: Painful days are ahead but Microsoft has what it takes to succeed. Sun, not so much. Oracle could go either way.

Seems I was right about Sun, not sure yet about Microsoft. I now think Oracle is in a better position than they used to be.

One of the major things I noted was that Microsoft, despite a major institutional aversion, has been slowly developing and expanding services businesses. They have continued to do this, for example now offering to host Linux VPS's via Azure. Their services offerings in 2003 were more anemic than they are today. They are on the right track to deal both with open source competition and long-extended upgrade cycles.

I don't think Microsoft is about to die. They may be cut down to size but I think their offerings are large and diverse enough that they are more likely to be pressured to evolve than disappear. Many businesses in fact do this, see IBM's transformation into one of the world's largest IT services firms in the world.

Just as a note on the factors I looked at:

1) Cash positive operations and cash reserves

2) Healthy services business (customer satisfaction, etc) These are important because they are a hedge against open source software and upgrade cycles that extend as hardware matures.

3) Lack of vertical integration/insularity

4) Organizational awareness of issues.

Sun scored relatively low on these, Oracle depended on how heavily you rated customer satisfaction and customer perceptions, and Microsoft scored high on everything but healthy services businesses, but there they were growing and trying lots of things.

Realize that my info is ~10 years old. At the time I was leaving Microsoft, they were working on adding more transparency to the process since, as you'd guess, people wanted to know more. Part of that was explicit titles tied to levels; part was just informing people of the process.

And at least there _are_ guidelines. Have you ever worked at a small company? There are certainly exceptions (I'd gamble that Fog Creek is one), but most of the ones I've worked at or for have had salary and promotion schemes that basically came down to some mix of hiring manager's whim, highest priority for the company today, your public visibility before joining, and whether you have some family connection to the owners.

To be fair (and like others have said re: Amazon), this sounds pretty particular to a specific team. In other teams, it's pretty clear what you have to do in order to get promoted. I overheard from some employees that at the last meeting they had on the subject, management was very straightforward, saying that they had X spots available and Y people to consider. If you did the right things, they would consider you, and promote the best X people. I think this approach is about as good as it can be in a large org.

I haven't heard of any organization with ~100k+ people without rules like these.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.