Quartz:
Another sign of how Google's attitudes have changed? I've always thought 20% time was an interesting concept, and the article claims that other companies that copied it still keep it alive.
Another follow up article with a bit more insight.
Does anyone here work at a company that utilizes any similar concepts? What are your experiences with it?
When Google went public in 2004, the founders letter from co-founders Larry Page and Sergey Brin cited 20% time as instrumental to the companys ability to innovate, leading to many of our most significant advances, including AdSense, which now accounts for about 25% of the companys $50+ billion in annual revenue. Google engineers also used 20% time to incubate Gmail, Google Transit, Google Talk, and Google News, among other projects.
Heres how Google has effectively shut down 20% time without actually ending the program, says our source: First, as has been reported previously, Google began to require that engineers get approval from management to take 20% time in order to work on independent projects, a marked departure from the companys previous policy of making 20% time a right of all Googlers.
Recently, however, Googles upper management has clamped down even further, by strongly discouraging managers from approving any 20% projects at all. Managers are judged on the productivity of their teamsGoogle has a highly developed internal analytics team that constantly measures all employees productivityand the level of productivity that teams are expected to deliver assumes that employees are working on their primary responsibilities 100% of the time.
Another sign of how Google's attitudes have changed? I've always thought 20% time was an interesting concept, and the article claims that other companies that copied it still keep it alive.
Another follow up article with a bit more insight.
Some Google engineers insist that the statements given to Quartz and issued elsewhere in public forums are flat-out wrong: I dont have to get approval to take 20% time, and I work with a number of people on their 20% projects, says one anonymous poster claiming to be an engineer at Google.
But other engineers, even those who say they use the free time at Google, painted a more nuanced picture.
"20% time isnt dead I have been using it at Google consistently for over 7 years, and it has immensely benefited me. You dont need any permission, at least in engineering.
However, I would agree that it is as good as dead. What killed 20% time? Stack ranking."
Stack ranking is a policypopularized by former GE CEO Jack Welchof ranking employees by various metrics and firing the bottom 20%. Google doesnt enact exactly this policy, and is more focused on helping its bottom 20% improve, but the point is that such policies of measurement dont exactly lead to intangibles like incubating new initiatives or products.
"Googles [performance] management is basically an elaborate game where using 20% time is a losing move. In my time there, this has become markedly more the case. I have done many engineering/coding 20% projects and other non-engineering projects, with probably 20-40% producing real results (which over 7 years I think has been more than worth it for the company). But these projects are generally not rewarded. Part of the problem is that you actually need 40% time now at Google 20% to do stuff, then 20% to tell everyone what you did (sell it)."
Apparently, 20% time is jokingly referred to within Google as 120% time to indicate that, while engineers have the opportunity to pursue their own projects, its only on top of their existing (often quite demanding) schedules.
Does anyone here work at a company that utilizes any similar concepts? What are your experiences with it?