"They were happy to see employees spontaneously self-organizing to put their 20% time to good use."
Reminded me that I heard that Google's 20% time had generally like 10% participation and has had a number of conditions including manager approval for the last 4 years. Is this article breathing new life into the myth of 20% time or does this reflect the revival of the process?
Either way, incredible accomplishment on the patch army!
20% time has always meant different things depending on who you talk to. It's likely that you're just talking to different people.
I took copious amounts of 20% time in my time at Google (2009-2014). Usually I'd start a 20% project with neither my manager's knowledge nor his approval; if it looked like it had legs, I'd let him know about it and ask what he thought. I never had a manager outright forbid me from working on a 20% project; responses ranged from "You should consider this your main project now; it's critically important that we understand this area" (along with a spot bonus for delivering on it) to "Well, you can work on it, but you are unlikely to get credit for it come promo time." In general, as long as I got my work done, my managers didn't care what else I was working on.
Was your workload such that you could put in a reasonable number of hours on your 'work' and still have 20% of your time for other projects? Or was 20% time just putting in an extra 20% on top of what other developers (who didn't do 20% projects) would do?
Over my career there, yes, I could put a reasonable number of hours on my work and still do 20% projects. There were short periods of time when I was asked to "bank" the time and focus entirely on my main project, eg. I might work straight for 5 weeks on my main project and then take a week straight of 20% time once it launched.
This suited me fine - usually the way I took 20% time was to fit it into time periods when I didn't really have much else to do or I was bored with my main project. And splitting it up like this let me focus more intently on both of them, which helped in delivering.
Cool, sounds like it worked out for you about the way I would expect. I suppose it may depend some on your team, I have heard some people say it is just 20% extra work.
Googler here. I recently had a 20% project that sometimes had bursts of 100% busyness (but still ~20% on average). It also was not relevant to my team and was in the benefit of "everyone". No explicit manager approval was required.
It certainly depends on the particular manager or even org, but in general 20% projects are still a thing for those who want them (not many).
It's not uncommon for people to put additional effort (that you can spend on a 20%) to fix stuff in the primary project. Like, voluntarily adding themselves to a build cop rotation or doing code / readability reviews as a service, and so on. And sometimes, the primary project is tight on deadlines and people want to stay focused.
And even when a person is enjoying the 20% opportunity, most of the time there is no good project to take on. During my stays at Google, I've done many 20% projects (>10), but only had a 20% project may be a third of the time.
People enjoy their work in different ways. Some like being 100% on their main project, some like involving themselves in many smaller efforts (both across their main project and across 20%). Also, the default state is to not have a 20% project, the only people that will work 20% on something else are those that made a specific effort to do so.
Googler here, 20% projects are very real. It's a flexible tool between employee and manager that gets used in a lot of ways. The only recent guidance was that 20% projects should benefit the company. And, mileage will vary depending on the relationship between employee and manager. Some employees and managers use the program well, others don't do as good of a job, but it's still very alive and well.
20% time never went away. There's especially a lot of code health 20% projects, and like the article says, this is applying that spirit to open source.
As other Googlers have said (and yes, I'm also one) 20% time is a bit misunderstood and always has been. Suffice it to say that it never died, and different groups have different levels of participation - some times, some teams are focused on a launch so the percentage of time spent goes up or down. But generally speaking, yes, this is exactly the sort of healthy thing that we encourage.
Reminded me that I heard that Google's 20% time had generally like 10% participation and has had a number of conditions including manager approval for the last 4 years. Is this article breathing new life into the myth of 20% time or does this reflect the revival of the process?
Either way, incredible accomplishment on the patch army!