Netflix: Non-'A' Players Unworthy of Jobs
theodp writes "Describing How Netflix Reinvented HR for the Harvard Business Review, ex-Chief Talent Officer Patty McCord describes 'the most basic element of Netflix's talent philosophy: The best thing you can do for employees — a perk better than foosball or free sushi — is hire only "A" players to work alongside them.' Continuing her Scrooge-worthy tale, McCord adds that firing a once-valuable employee instead of finding another way for her to contribute yielded another aha! moment for Netflix: 'If we wanted only "A" players on our team, we had to be willing to let go of people whose skills no longer fit, no matter how valuable their contributions had once been. Out of fairness to such people — and, frankly, to help us overcome our discomfort with discharging them — we learned to offer rich severance packages.' It's a sometimes-praised, sometimes-criticized strategy that's straight out of Steve Jobs' early '80s playbook. But, even if you assume your execs are capable of identifying 'A' players, how do you find enough employees if 90% of the country's population is deemed unworthy of jobs? Well, Netflix CEO Reed Hastings' support of Mark Zuckerberg's FWD.us PAC suggests one possible answer — you get lobbyists to convince Congress you need to hire as many people as you want from outside the country. An article commenter points out that Netflix's 'Culture of Fear' has earned it a 3.2/5.0 rating on Glassdoor."
This has been my experience as well. The best teams and companies are those who have a good mix of people, and who know how to utilize talent. For example, I've worked with an old geezer who was rather over the hill as a designer / analyst. A "D" player at best in his assigned role. However he had a ton of knowledge about the company, projects and people, and in some ways he was the department's "memory". He also had good ideas about how to organise teams and company processes, and he was a brilliant coach. He wasn't good at actual management jobs, so... they left him where he was, and where he was perfectly happy. Adding a ton of value to the company on a daily basis. Freely organizing around problems is exactly what he did.
That's not to say you don't need the right mix of people and skill levels to be successful. A-teams are probably as likely to contain the right mix, and in my experience about as likely to recognize it. Unless of course you stack the deck by saying that your A-team also has an A team lead who knows everything about this, but I've never seen this in practise.
If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
Here's the problem. Grade A people expect to do grade A work. In almost every organization there is a ton of work that doesn't fit into this category but still needs attention. Code gets old and has to be updated, and there's a ton of work that doesn't require the brightest and best but still has to be done.
Now the grade A people don't want to know that. They want to work on the sexy new stuff that makes them look like the superstars they are. They might put up with maintenance coding for a while, but they won't stay there. They will want to move to better things, and if they can't they will move to another company - and because they are grade A, they can do that with relative ease.
Google used to have the same issue with a grade A requirement, and they found that products stayed in beta for years as a result of engineers moving on when the interesting parts of the code was done. They even had to cancel some products because they couldn't get engineering resources that wanted to work on them. So they lowered their standards a little and things improved somewhat.
By the way, I'm not knocking maintenance programming - that's often difficult work. Maintenance guys have to come up to speed quickly on systems they never wrote and then make the code do things it was never designed to do, and finish it in an impossible short deadline, because it's "only" maintenance. But it's not sexy enough for most grade A folks.
I think the choice of VC-1 came because it was supported by Silverlight while H.264 was limited if present at all. VC-1 is also the protocol of choice for Blu-Ray, and the time saved simply copying the files instead of moving them to H.264 may be significant.
They're the largest in their field and have little real competition, so they must be doing something right. They're also in the process of moving away from Silverlight, provide a primary source of more bandwidth across the Internet than perhaps any other single company (not counting CDNs like Akamai), and maintain a customer satisfaction rate that is the envy of most of the entertainment industry. The executives may need to be smacked around a little, but it's hard to argue that the company as a whole has many serious problems.
You can never go home again... but I guess you can shop there.
Sort of: they use torrenting stats to work out what's popular and acquire licences to stream it.
Yeah, I had a sig once; I got bored of it.