The Decline of '20% Time' at Google
One of the things Google is known for is giving their employees so-called '20% time' — that is, the freedom to use a fifth of their working hours to pursue their own projects. Many of these projects have directly improved Google's existing products, and some have spawned new products entirely. An article at Quartz on Friday made that claim that 20% time was all but dead at Google, largely due to interference from upper management. Some Google engineers responded, and said that it has essentially turned into 120% time — they're still free to undertake their own projects, but they typically need their whole normal work week to meet productivity goals. "What 20% time really means is that you- as a Google eng- have access to, and can use, Google’s compute infrastructure to experiment and build new systems. The infrastructure, and the associated software tools, can be leveraged in 20% time to make an eng far more productive than they normally would be." An article at Ars makes the case that this is not necessarily a bad thing, because Google has enough good products that simply need iteration now, making the more innovative 20% time less useful. "Google wasn’t hurting for successful products when it started to tout its 20 percent time: off the backs of its pre-IPO services, it earned a market cap of over $23 billion. But if it was a company that wanted to grow and diversify beyond products that were either related to search or derivative of what already existed, it needed more ideas, better ideas, as quickly as possible. Hence, liberal use of 20 percent time made a lot of sense. Now, Google is not only an enormous company of nearly 45,000 employees with a market cap twelve times that of its first IPO ($286 billion), it has a lot of big products that it wants to make work. More than it needs more ideas, it needs to make the ideas it has great."
The stock market kills companies.
A change from a work environment where you can spend 20% of your time experimenting with new ideas you have, and 80% working on the "regular" mainline products, to one where you're expected to spend at least 100% of a regular workweek iterating on the "regular" products, seems like a bad thing from the perspective of the engineer at least. Ars seems to be arguing that it's not necessarily a bad thing for Google's stockholders, which is a pretty different question.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
What that often translates into is: do stuff we aren't paying you for. Why can't the staff handle their own secretarial needs? Why can't they clean up their own workspace, get their own supplies from storage, install their own software etc etc. We take what was before someone elses full time job and just tack it on to everyone else's day but don't reduce the productivity expectations to compensate.
What is productivity? How do you define productivity?
My point is you can work for gmail and do your metrics to hit your spam filtering code. But, what if the next big idea is there that can generate more revenue. Would it then be wise to work on better spam filtering for your gmail users or would it make more sense to fund something that no one has done yet and that Microsoft or Apple will invent and then patent the shit out of instead?
That was my point. I have worked at companies where they are were sooo process oriented that we just put out fires and no one could ever call out sick or go on vacation or the whole operation would shutdown.
The good employees left and they had to bring in H1B1 because they were cheaper and would have no quram working 65 hours a week just to remain employed. Work 40 hours a week you were fired for being lazy. No improvements and no say were allowed outside of the directors as we had no time to do anything else. We just put out fires and worked 120% to keep our jobs. That might have worked for the previous CEO to gain his bonus but the company is losing over a 1 billion a year now!
http://saveie6.com/
The more MBAs in your organization the less innovation you will have.
They don't think in terms of success through better (or more diverse) products, only in squeezing maximum efficiency from everything - Marx would applaud them.
Motorola in 1981 they used to say "work smarter, not harder", we got comp time off for overtime worked, etc. After a while it became "work harder", and the comp time off went away, and overtime was expected with no compensation. A little while later it became "work!", followed by "work, goddamit!" where you were viewed unfavorably if you used company time to take a leak.
The bean counters always win...
I work for Google. 20% time is unpopular, undertaken by single-digit percentages of engineers. Despite that, the message coming down from management is generally positive.
My sense of the issue is that a lot of engineers are spooking at shadows, worried about their performance reviews if they spend 80% of their time on their teams' main business rather than 100%. The solution to this, as far as I am concerned, is to make sure there is someone who is willing to stand up and say positive things about your project at review time. Since Google has an intricate system of peer review, that should be enough.
And if you can't find _one_ person who thinks your project is a good idea, take some time to figure out what you are hoping to accomplish before continuing.
But there is something else going on here.
Google was, a long time ago, a young idealistic company full of people that had drunk the Kool-Aid and were willing to pour out their energy into neat little side projects that one day might make Google greater.
Times have changed.
The smart folks at Google percolate their ideas on their own time in secret, and then bail out and start a "start-up" (and then possible sell the idea back to Google).
The whole "creativity" dynamic has changed at Google. It is still a pool of VERY smart people, but they know better than to give their ideas away for free.
If you want news from today, you have to come back tomorrow.