19 ms·
Ask HN: Was 20% time a good policy for Google's working culture?
I know the policy doesn't really exist anymore, but I still like the idea a lot in principle (for large and financially secure startups, say 1k developers and up). Just wondering what Xooglers and others think about it.
- asdfasgasdgasdg 6y agoI think it was a great outlet for the people who enjoyed using it. But most people were busy enough with their regular jobs that they did not engage with 20% time.
- chamberecho 6y agoI have no idea if it was good for their culture since I never worked there... but I reckon a lot of corporate software engineering jobs have the same luxury, informally. I work at a big US bank where you might not expect such freedom, but in reality there is great flexibility to do things outside of the normal day to day BAU, simply because it's not hard to deliver a sufficient amount of work in less time than you're expected to be in the office (or covid equivalent), and nobody keeps that close an eye on what you do anyway. Still, with all that freedom people don't always use it for good, they may actually just bunk off...
- ng12 6y ago> Still, with all that freedom people don't always use it for good, they may actually just bunk off... This is the right call. If you ever actually move the needle on anything important your fun 20% project will assuredly be taken over by middle management and you will get pushed out. If you have free time at a bank either slack off or work on low-effort projects that look good on your performance reviews.
- fractionalhare 6y agoAs a counterpoint, I've been promoted so that I could maintain leadership of a successful 20% project before. And I didn't go into it expecting it to get any visibility, it just happened. Not all workplaces are toxic. You generally have to take charge of your own career. But often the politics align such that it'd be strange to kick someone off their 20% project if it's successful.
- ng12 6y agoAgreed, it absolutely depends on where you work and sometimes your management chain. I'm mostly referring to the finance industry where I've seen this pattern repeated many times.
- agilob 6y ago> don't always use it for good, they may actually just bunk off... Which is good if you're tired, overworked, didn't sleep well or just want to spend some time with family. I usually use it to read books not closely related to my daily work, but related to what my coworkers do. Like about subscription models, devops, scrum master roles.
- silexia 6y agoI worked in a company that did not keep tabs unemployees at all. I was able to eventually reduce the amount of work it took to do my job to about 20 minutes per week. I use that time to learn how to program, then left and started an agency.
- blackrock 6y agoTell us about your agency. What have you worked on? How did you find your clients or customers or projects? Is it a consultancy? Or did you develop a marketable product? What technologies, programming languages, databases, and tech stack did you use? Keep the information anonymous, of course, if you want to maintain your privacy.
- one2know 6y agoBusiness siders including HR, marketing, sales, product, execs, managers etc ALL universally don't work Fridays. They (used to) come in for a couple hours then "bunk off" to the bar for lunch and happy hour (starts at 3). I find it ridiculous that engineers actually do work on Fridays, much less Friday after 3pm.
- zamadatix 6y agoDepends on the place for both counts.
- onion2k 6y agoStill, with all that freedom people don't always use it for good, they may actually just bunk off... I imagine no one at Google used their 20% time project to bunk off, simply because it was 20% of their working time, and not 20% of their contracted hours. If you're supposed to do 40 hours a week but you actually spend 80 hours working on work and 20 hours on your 20% project then you aren't bunking off.
- Privacy846 6y agoWhy would one do twice the hours that one is paid for? That makes no sense. :)
- stjohnswarts 6y agoAt some places that is the culture, and I'll do it for a couple weeks during a crunch, but I refuse to do more than that. After a week or two your efficiency goes down incredibly unless it is "your baby" or your passion and it's basically "fun" for you. I've never had real fun working on someone else's baby. Burn out is a real thing. We didn't evolve to sit on our asses in front of computers 16 hours a day, it's a simple matter of biology. We are adaptable, but we're not that adaptable.
- Privacy846 6y agoExactly. I can’t work 12 straight hours on an average day, my mind wouldn’t have allowed me to.
- bobthepanda 6y ago> Still, with all that freedom people don't always use it for good, they may actually just bunk off... Working smart and not hard and reaping the rewards is not "bad". The Protestant work ethic and living to work aren't healthy for everyone and I don't really see why we need to assign value judgements to people who do or don't subscribe to it.
- lanstin 6y agoI don’t trust software engineers without sufficient laziness.
- andrewljohnson 6y agoIn The Reponsible Company (by the Patagonia founder), he credits Googlers doing 20% time to do environmental work. The book is really pro-corporation though, heavily a PR piece IMO.
- fnbr 6y agoI found that to be the case with all of Chouinard’s books, especially “Let my people go surfing.” Tons of lightly veiled corporate propaganda.
- milofeynman 6y agoWe have a form of it called fix-it-friday and I find it helps a lot with minor UX improvements and tech debt that would otherwise fall in-between the cracks.
- aerovistae 6y agoYou're probably downvoted because it's semi-off-topic, but I think it's close enough to be relevant and worth discussing. Where I work, we dedicate 1 day per sprint to tech debt where everyone can just work on fixing whatever they want. It's made HUGE differences to the developer experience. So many of the things that slow us down and annoy us have gotten fixed this way. Sounds about the same as your fix-it-fridays.
- milofeynman 6y agoYeah, that sounds about right. It's those little things that really help the whole platform long term.
- TedDoesntTalk 6y agoDo you get to choose what to work on? Does it have to be in the backlog or can it be something not tracked?
- milofeynman 6y agoYup. Some people choose to just do regular feature work, others use it to great effect. Some of the best examples are slowdowns that sort of fall in-between feature teams, or debugging features that help other devs/QA, or tooling that helps debug customer issues. I imagine most of the things fixed come from annoyances that devs run into that they want to improve the product, QA, or tooling experience, customer experience.
- caymanjim 6y agoThis is not 20% time for personal projects. This is is scrambling after the fact to fix things that should be done as part of the normal development cycle. Formalizing it is basically saying "we know our process sucks, but instead of fixing it, we're going to sell it as a feature."
- gedy 6y agoI work at a company with 10% time, and TBH most people don't do much with it, if at all. A few do and really seem to appreciate it. We get more innovation and ideas from hack days.
- MattGaiser 6y agoThe problem is that it is very hard to get something big from little splotches of time, or at least I find it hard, so I focus on little wins. My company informally allows for spending time like this, but if it works out to an hour or two a day in between meetings and Slack requests, I can't really do much with that.
- Tempest1981 6y agoDoes the 20% need to be distributed evenly, time-wise? Or could you combine it into a 5-10 week clump between projects?
- gedy 6y agoMine is one day every other week
- aitchnyu 6y agoI write very little shippable code in first day of a 3 day task. Also my itch for unfinished work is very unhealthy. Does 20% favour guys who compartmentalize unfinished business to a fixed day every week and ramp up quickly?
- greesil 6y agoI have used something like 20% time to help manage technical debt, keeping it from consuming our team in web of pain and complexity. Usually we come up with a week or two of time every quarter to take care of these things, instead of a day a week.
- gotaran 6y agoShouldn't that be part of your core responsibilities and not "20% time"?
- bwest87 6y agoEh, maybe. Your core responsibility is to ship on time. Especially at a startup, it's not only "ok", it's usually the "right" call to ship faster, and accumulate technical debt. This is constant, and never really goes away. So you tend to have to intentionally bake in this time, or else it never happens. And I think this is OK! It's not always clear what is and isn't technical debt at the time it's being introduced. A lot of things seem "gross", but aren't actually much of a problem. Or you think, "oh god, this will never work when we add X feature", but then you just never add X feature, and so it's totally fine 2 years later. But to your point, of "well shouldn't that intentionality be part of normal duties?" Sure, but shouldn't coming up with Gmail? Or fixing bugs or UX improvements also be part of normal duties? Yes, they all should. The truth is it's hard to prioritize small things like that, and it's really hard to get a sense for their value as a centralized management team. They aren't close enough to the code or the product to always know. So I think 20% time is a great way to just decentralize that, and allow the engineers closest to the issues to pick what's important to work on.
- gotaran 6y agoYes, we're in agreement. A coworker of mine pointed me to the book Accelerate [1], which I admittedly still haven't read, which also mentions that organizations where management tries to make sure engineers are at 100% utilization end up being dysfunctional, partly for the reasons you pointed out. [1] https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339 https://www.amazon.com/Accelerate-Software-Performing-Techno...
- jasongrishkoff 6y agoI did a 20% project for Google Music back its early days, circa 2012. I was working on the Executive Compensation team at the time, but running a music blog called Indie Shuffle on the side. It's a long time ago, but I seem to recall naïvly hoping they'd embrace me with arms wide open and invite me to join their team + revamp their strategy. I met with a couple members of their team who were open to entertaining me given my background with a music blog. I remember being really excited about it - and I spent a lot of time preparing a deck about how exposure provided by the Google Music blog could be used as leverage to give the platform legitimacy in the eyes of independent artists (something that SoundCloud was doing really well at the time). A few senior leaders agreed to let me pitch my ideas, and after a fair bit of head-nodding, nothing actually happened. I ended up leaving Google about 3 months later to take my music blog full-time (still up and running at https://www.indieshuffle.com https://www.indieshuffle.com, and eventually started a much-more successful music venture called SubmitHub - https://www.submithub.com https://www.submithub.com). I count myself fortunate to say I have no regrets leaving Google. Reflecting on the idea of 20% projects, I do appreciate that my managers gave me the opportunity to explore alternate opportunities within the company, and that the Google Music team was receptive to me poking my head into their affairs. I think it holds a lot of potential when it comes to retaining top talent that's at risk of jumping ship for something different, and made me feel like I was part of the larger company rather than simply stuck in a silo.
- ultimoo 6y agoGreat story, thanks for sharing. What is it like being on google’s exec compensation team? I had no idea that was a thing and would love to listen to any more fun stories (only if you’re allowed to share).
- jasongrishkoff 6y agoExec comp is definitely a little-known function of most major companies. Normally folks would outsource that type of work to consultants, but Google was big enough that it needed 2 of us full-time. We helped the CEO and SVPs figure out how much to pay the company's top ~100. That meant we were hands on with performance bonuses, equity packages, hiring negotiations, promotions, and more. The coolest part about it was getting to frequently join Laszlo Bock (head of People Ops at the time) when he met face-to-face with the CEO (first Eric, then Larry) and the SVPs to discuss all of the above. It got to the point where they all began to recognize me, which was pretty darn cool as a 20-something-year-old. A byproduct of all that exposure was that I ended up being privy to a huge chunk of the "corporate drama" taking place in the upper ranks. It's been 7 years since I left, but as I'm sure you can understand, getting into details is probably a bit of a no-no :)
- corobo 6y agoIt was great marketing among developers if nothing else. Don't forget the pre-hires! Nobody just let you do passion projects! Get back to your work
- enneff 6y agoYeah it was great marketing. One of the reasons I so very much wanted to join the company. And here I am still, nearly 11 years later. I have done some fun stuff in 20% time. Some relatively serious projects that went somewhere; enough to keep me entertained. It’s true that if you have a demanding role it becomes more like 120% time. However it’s more the spirit of the thing that matters; the fact that you’re encouraged to pursue your interests on work time has led me to learn and experiment more than I would have otherwise.
- mondoshawan 6y agoIt was and still is part of our culture.
- thesausageking 6y agoGmail supposedly came from Paul Buchheit building it for his 20% time. Likewise, Google News was created by Krishna Bharat for his 20% project when he wanted a way to keep up with news after Sept 11th. Are there examples of successful results?
- trynewideas 6y agoGoogle Reader :(
- Cederfjard 6y ago>large and financially secure startups, say 1k developers and up Sorry for the tangent, but what’s the definition of ”startup” we’re working with here?
- jmtulloss 6y agoMy working definition is something like “pre-product-market-fit” or “hockey sticking” growth. Once you saturate your market and have to fight for every percentage of growth (or are so big that new things can’t make a big impact even if they are exploding in their niche) then you’re no longer a startup
- jmtulloss 6y agoThis also implies that linear growth companies aren’t startups, they’re SMBs. This is probably controversial and definitely valley/VC centric.
- dnautics 6y agopre-exit, I presume.
- deleted 6y ago[deleted]
- karaterobot 6y agoI've always wondered what the accountability for 20% time was. Did you check-in on your project with a manager? Did you present it at some demo meeting? If sufficient progress wasn't being made, did someone "encourage" you to change projects?
- bwest87 6y agoYou can do it a few ways. But in my experience, the simplest and best way is to force people to demo something at a pre-specified time. If you're doing it "hackathon" style, then it should be at the end of the hackathon. If you're doing it 20% style, then probably end of the quarter? You could do it with zero accountability, but having tried to run these programs (see my other top-level reply here), I think you'll mostly get a lot of people not doing much if you don't have any accountability.
- deleted 6y ago[deleted]
- mdoms 6y agoI'm not and never was a Googler but at Atlassian we the same policy of 20% time and I really do think it was super valuable. There are a certain number of developers who will muck around and waste their 20% time and there are certain (terrible) team leads and PMs who discourage the use of the time because they're anxious about their own projects. But for the most part it contributed massively to the happiness of the developers. And the outcomes, in my opinion, were invaluable. It's not always visible from the outside, but Atlassian now has swathes of valuable internal tooling, built with love by developers who were invested in solving their own productivity problems. The quintessential "20% project" is GMail but I think that misses the incrementalism that 20% projects really provide. Developers will absolutely take advantage of the time to improve their personal ergonomics, and everyone around them benefits from that. But this is obviously very difficult to measure.
- goalieca 6y ago> It's not always visible from the outside, but Atlassian now has swathes of valuable internal tooling, built with love by developers who were invested in solving their own productivity problems. Can we get some of that same love put into the actual business products?
- mdoms 6y agoI no longer work at Atlassian but I spent my last year working on a Jira frontend refresh that no customer ever asked for and few considered an improvement. So..... no? Haha sorry.
- jay_kyburz 6y agoOur beloved Trello now has some critical bugs. Makes me very sad.
- deviation 6y agoA missed opportunity... Seems my team spends more time complaining about Jira card load times & its interface than they do discussing the card..
- paxys 6y agoA broad, sweeping 20% time was never a thing even at Google. Some "rockstars" may have been left alone by their manager to pursue such projects, but the average engineer absolutely did not have this freedom. It was mostly all marketing.
- monktastic1 6y agoI don't know about that. I was no rock star, but my teams let me pursue it with no issues circa 2008-2015.
- more_corn 6y agoAt Google the joke was that 20% time was really 120% time since you still had to do your day job. I never personally saw a 20% time project turn into a product and I never felt comfortable taking 20% time. However, I did feel comfortable taking on what I saw as important work but which wasn't part of my job description --training myself up on it and becoming the go-to person for that work. That part of the culture WAS consciously cultivated and I found it very valuable. It drew me up and made me more than I was. It was bound up with a culture of open sharing of ideas and cross-training. A notion that you could find compelling work at the company and shift your focus to that work/team. There was also an effort to encourage new projects and ideas but they didn't go far enough. If I could give one piece of advice it's to create explicit approval and some serious financial incentives for people who start new products at your company. Treat projects like this in the way you'd treat an acquisition of the company making that product. E.G. if your company adopts a side project as a product, give the creators cash, respect, authority, and support to grow it into something great.
- dheera 6y agoI'm not a Googler but wasn't Gmail a 20% project? (And maybe other Google products that I don't know?) It seems to me that it would be entirely worth it to Google if 99.99% of 20% projects don't go anywhere, but every now and then, you get a big hit like Gmail whose newfound revenue completely eclipses the lost 20% experimental time from the 9999 other employees. And even for those 9999 other employees, even if their 20% projects don't go anywhere, they are likely still hugely educational in ways that would make them more productive in the other 80%.
- jayflux 6y ago> I'm not a Googler but wasn't Gmail a 20% project? (And maybe other Google products that I don't know?) I think the parent meant they didn’t see a 20% time project come to fruition while they were there, not in general
- tonfa 6y agoAlso I don't think gmail was a 20% project (at least according to wikipedia which links to http://blogoscoped.com/archive/2007-07-16-n55.html http://blogoscoped.com/archive/2007-07-16-n55.html): > [...] they asked me if I wanted to build some type of email or personalization product. It was a pretty non-specific project charter. They just said, “We think this is an interest area.” Of course, I was excited to work on that.
- sdenton4 6y agoOver the last few years, I've used 20% time to: a) Learn deep learning on audio with a friend, via online courses, reading research papers, and re-implementing things. Then, to put the knowledge to work, I... b) Joined a small bioacoustics project working with external researchers to level up their ML, c) Developed some models and deliver some results to the external researchers, and, finally, d) Got hired onto a new team doing ML on Audio full time, largely on the strength of recommendations from bioacoustics people. e) I've kept hacking a bit on bioacoustics, including launching the birdsong id kaggle competition earlier this year. https://www.kaggle.com/c/birdsong-recognition https://www.kaggle.com/c/birdsong-recognition IMO, 20% time is "just marketing" until you actually put in the personal effort to make something real out of it. Doing so is non-trivial, though. There's a real risk of falling into a 'half-ass two things' pattern. It's difficult to do exactly one day a week on some project, then cleanly drop it until the following week. Context loss is a real problem. This year, I find myself looking out for 'low stress' times during my day job to do some deeper dive on bioacoustics and create a bunch of new stuff in a kind of sprint, rather than consistently setting aside 8 hours a week. It's hard to do a research 'sprint' in two areas simultaneously; it's better to let a research question take over my brain for a while. (I also find that my personal limit for meaningfully tracking experiment outcomes is two model architectures. I tried three at some point this year and it was kind of a disaster.) It's tough to motivate myself to do important-but-boring things like write unit tests in 20% time, which (combined with the context shifting problem) has often lead to pain down the line. All told, it's a hard road, but very rewarding, IMO.
- rvna 6y agoAs someone who's interested in this space, could you point me to the resources you used to ramp yourself up? Also, what are you working on w/ Audio ML?
- sdenton4 6y agoHard to point at one thing! I started with a deep learning for artists course, and adapted the stuff I saw there to an audio mini project. And then started reading the big papers in neural networks independently. I found it helpful to read the source material (eg, ml text books and academic papers), paired with blog entries (which often have a good basic idea, but skip out get wrong some details), and actually building things for my own interests. On the work side, I'm doing low bit rate speech coding, which is good fun.
- throwaway60011 6y agoThe most visible impact was in the company's internal services. Many "scratch an itch" tools such as Google bus schedule lookup, employee tenure lookup, or massage-room booking originated in 20% projects. The "internal social media" of Google such as "moma badges" ("achievements" for e.g. writing 100 CLs or contributing to a particular fixit -- anyone could add new ones) and the internal joke image board "memegen" also originated as 20% projects. This kind of modest, privste service was much lower-commitment than trying to single-handedly kick off a new external-facing service. Having all these volunteer-built projects around created a good vibe of being part of a community of engineers, each building whatever we needed to make our days better and sharing it with our coworkers.
- swyx 6y agoi like that a lot. although arguable whether memegen is a net conributor or detractor to Google's productivity (debatable) and culture (even more debatable)
- ceras 6y agoAFAIK it still exists. In my several years there, most people didn't take full advantage of it, and that was as true in 2011 as it was in 2020. Most people just didn't come up with anything a technical project they'd rather work on than their core project. (I was one of those.) I think most who took advantage actually worked on improving and facilitating employee training & learning programs. Google has great internal training material -- mostly for internally-used technologies, but sometimes for external technologies people are curious about too, and also for soft skills, and even not-work-related skills (e.g. fitness classes). Overall I think the 20% resulted in more "community" work than most other companies have, and I think it was a positive for company culture. And for the few people that actually worked on technical projects, the existence of 20% time seemed highly motivating for them.
- deklerk 6y agoI've been at Google for 3 years and have 20%ed the entire time I've been there on: grpc-go, Drive, and Go tools (gopls, etc). I think it's fantastic. The whole 120% thing is up to the individual: there have been times I've made it a 120%, and there are times when it's been just "take a friday off to work on other stuff". You end up getting less of your "job" done but my managers have always been supportive. It's been great for sanity: some weeks/months feel just, like, meetings and chore work. It's great having that one day a week to work on a rockstar feature request in some fun project. It's also cool to work on your dream projects without the luck/physical move/whatever to get on the actual team. (you can effectively work on anything since no project is going to say no to free headcount) It's also nice because it spreads your professional network in the directions you choose to spread it, rather than the more organic spread that your normal job entails (assuming luck and available are big drivers of where and which projects you "end up" working, rather than 100% your choice). So, maybe I don't work on project X today, but I can 20% on it and build up those connections, and later in my career I have a much better shot getting on the project. That agency is a nice feeling. So, as far as the employee happiness goes, I think it's fantastic.
- serial_dev 6y agoWhat is the company size where you think a 20% policy like this matters? Does it only make sense for large companies like Google? Thank you for your take on these questions, your answer would be very much appreciated.
- seangrogg 6y agoHaving formerly worked on 20% projects at Google and now working at a small company, I'd say that 20% time can be valuable at any size. For smaller companies it's easy to essentially always have feature work which means never really having time for code health; anything that wasn't done right the first time will be hard pressed to justify getting done ever unless it's either breaking something or preventing features. 20% time can allow engineers to do something about issues they see and care about which could improve things for everyone else in a way "one more feature" may not.
- dub 6y agoIn the heyday of 20% time, Google had more money than they knew what to do with and the engineers were generally overqualified. Remember that in the early 2000s Google was famous for hiring people with PhDs and asking them build web servers. Within that climate, 20% time was a great policy. Nobody needed "permission" to take a day out of the week to write a better source code management workflow or a config file VIM code completion for the internal codebase or improve build times or fix an annoying bug in another team's codebase, or even just generate good will for the company by contributing to open source projects. It was good for the company, and good for morale.
- yodon 6y agoThe way I've heard it expressed is "if you want to hire racehorses, sometimes you've just got to let them run"
- Privacy846 6y agoI don’t understand. A PhD is a degree in research. If you have a PhD and are building web servers you sound misqualified.
- topkai22 6y agoThat’s exactly the point- Google in that time frame did a TON of prestige hiring, whether or not it made sense for the actual work they needed to fill.
- Privacy846 6y agoThat’s not what I got from the original comment.
- cambalache 6y agoHow so? That was entirely the point
- 6y ago
- whateveracct 6y agoAt my company (BigCo but not FAANG or SV), we have 20% time, but it's more for personal learning than side projects (and when it is projects, it's fine if those are just to learn, and not to help the company directly.) Execs call it out and focus on it too, so managers will even be happy to hear you're using it (and say "what can we do to get people to feel like they can use it?")
- bwest87 6y agoI never worked at Google, but I did work for a different, fairly well known consumer tech company doing a lot of work around "hack time". While there, they didn't have any such program, and I really wanted there to be one. So I helped implement a program for "hack time", which was pretty close to 20% time. I did surveys of over 100 engineers, put together a presentation for leadership, got directors of various eng departments on board, did a pilot program, then did post-surveys and presentations to gauge impact. We also spent time with managers to make sure they were on board, and made it clear to their direct reports that they were on board, and that it was OK to use hack time. The point is, we really tried to do this right, and get people to use the time, and assess if it was actually valuable. We did this for a quarter across a few different large eng teams. We eventually shut it down. My high level takeaways were the following... * Way more engineers *say* they're into doing hack projects than actually ended up doing them. We had huge initial survey response of people saying they wanted to do something, and only ended up having like 5-ish projects that were seen through. And there were probably 20ish projects that started at the beginning of the quarter. So large drop-off. * BUT! That can be totally fine! Many people who actually used hack time were some of the best engineers at the company. Other ones were some of the newest at the company. You're really helping job satisfaction for those top engineers, and really helping mentorship and learning for the new engineers. * I now believe it's better to have regular highly condensed hack weeks (or hack days if you're a small company), rather than a spread out "20% time". Even people who really liked hack time found it hard to actually take the time when deadlines were approaching. But when you just eliminate those things with a condensed period of hacking, then people can focus. You also tend to increase participation considerably through this method. (I know cause we did this method as well) * Stop trying to create Gmail in your hack time! A lot of the most valuable stuff to come out of hacking was internal tools, refactors, and little things that improved daily quality of life around the company. (ie. someone made a batch upload tool for the customer support team that they *loved*!). Or small UX improvements for customers. Some people did try to create certain new products, but it's super rare that those make it into the main product Not saying it can't, or won't, or even that you shouldn't do it. But as a general rule, the best you can hope for there is you've de-risked a new feature, or gotten your manager excited about the possibility, and they'll slot in time to "do it for real" in the next quarter. Realistically, people tend to have more fun just making stuff that they actually can see the value of the next day. Or when they get to hear thank you emails immediately from a whole other team. * You get a lot of other value from hack time besides break-through products. Specifically, you get people across teams mingling with each other. You get new and experienced engineers hanging out. You get a feeling of autonomy. People learn new tech or new parts of the company. For example, I made one of my most lasting relationships at that company by just randomly deciding to join his hack team for a hackathon project. I also got to use GraphQL and React for the first time on that project. Overall, I think hack time/ 20% time / whatever you want to call it is very very valuable, and companies of all sizes should do it. But you have to do it right, and you have to go in with the right mindset about why you're doing it. Do it because it's fun. Do it because you help your company meet one another. Do it because you'll probably improve the daily quality of life in small tangible ways for a lot of people for your customers, or for other employees. Do it to give your engineers some autonomy. Don't do it in order to get your next Gmail.
- vl 6y agoI worked there in 2010s and almost nobody was utilizing it anymore since general incentives were not aligned: it was hard to cut out time from your main project, and on top of the you had to pre-justify your 20% project as useful, which is for 20% project often more work than the project itself.
- musicale 6y agoI do like the idea of being able to spend 20% of your time on work that is worthwhile, meaningful, rewarding, and that you actually enjoy, but I wonder if the percentage could be increased somehow, maybe to 50% time or something?
- lanstin 6y agoThe way to do that is to find projects/changes to do that marry the business requirements with what you believe is excellent and right and should be done. Don’t just blindly implement requirements and don’t just build what you like, but have a compelling technical vision and then find other important things that justify (to others) building the vision.
- umaar 6y agoNot at Google, but rather Shazam. I've always been a big proponent of 20% time. Shazam is the first place I worked at which taught me about them and I've written about it here: https://umaar.com/blog/lessons-learned-from-working-at-shazam-part-1/#hackday https://umaar.com/blog/lessons-learned-from-working-at-shaza... It was the way in which I learnt what I'm passionate about.
- jboggan 6y agoI worked on a 120% project but was advised not to let my manager know about it unless it was successful. Not sure that is an indication of it working as intended.
- axegon_ 6y agoOK, never worked at Google, most likely never will for a million and one reasons but... Could someone eli5: What's a 20% time policy?
- detaro 6y agohttps://en.wikipedia.org/wiki/20%25_Project https://en.wikipedia.org/wiki/20%25_Project > The 20% Project is an initiative where company employees are allocated twenty-percent of their paid work time to pursue personal projects. The objective of the program is to inspire innovation in participating employees and ultimately increase company potential.
- tlogan 6y agoThe most important thing when building your company is that you encourage individual initiative: it might be via 20% or via some other ways. It is only reasonable to have 20% in certain situations. In short, focus on the reason why google had this: to encourage the initiative. In many corporations showing initiative (inventing things, doing more that required, etc.) is a career ending move.
- mensetmanusman 6y agoI work at 3M where we have had this policy for about 100 years. It’s the only reason we still exist; most of our sold products were side projects a generation ago.
- jedberg 6y agoI feel like at a place with expensive lab equipment, 20% time can go a lot further. Take smart people and give them a free day once a week to use all that expensive equipment they couldn't do on their own, and maybe magic happens.
- throwaway3699 6y agoI feel like access to Google's infrastructure + data definitely fits the profile here.
- rightbyte 6y agoI don't really think so. Most programming tasks can be done with a 2010 year-model computer. In machine engineering etc. you need expensive equipment.
- throwaway3699 6y agoAt Google it's commonplace for a single engineer to be able to run a MapReduce over the entire internet. Or do experiments with training huge deep learning models. The fact that approval is not required (aka 20% project) to use staggering levels of compute is the advantage I'm talking about.
- lucb1e 6y agoThat sounds a lot like a hacker space. While with paid time and less beer, it's not that dissimilar. I still think cities should create these spaces, not just support them... and unfortunately even support is almost never given.
- Ozzie_osman 6y agoI worked at Google 2006-2009. I joined a 20% project with an awesome staff engineer, then recruiting one of my team-mates to join 20% too. We ended up working on it full-time. It didn't end up launching but I think the core code ended up being used as part of other products. It was incredibly rewarding and a great outlet from my typical day-to-day improving Adwords.
- spicyramen 6y agoWe started a 20% project to get stuff done when we were not able to get head count. It was related to ML and people that joined were actually interested to learn the skill to move to a new team or our team. Unfortunately it took a long time before we actually got something that was useful. There was not really commitment not accountability.
- amf12 6y agoPersonally, I think it is a good policy for work culture. 20% does not just mean you have to work on your own idea but you can work on your other passions or to develop your skills. Say you are a backend dev and are passionate about ML, you could do a 20% with another team which is working on ML and develop your skills or just test waters. If that work has impact you can also include it in your perf.
- jariel 6y agoI wonder if '20% time' but on some kind of 'approved' project might make sense? None of us 'fully agree' with the product features set. We all have 'that thing' we feel different about. I wonder if instead of 'work on whatever' - you can just 'work on something else, that you really want to' - but that has practical value. Like XYZ feature, or creating online training, or that researchy thing with the local Uni. So 'in line with company objectives' but still fun. Because frankly, Google has been rolling in surplus since day 1, they have all the money in the world, that's fundamentally a different economic space than companies who are on the line.
- m0zg 6y agoThere never was any real 20% time. It was, as others are saying, 120% time, at least if you care about actually moving upward on the career ladder. Paradoxically, this makes it a good policy _for Google_: if you're an idiot, you'll put in 120% effort and Google gets more work per dollar from you (and gets to deny promo because you "spent too much time on your 20% project", as well), if you're not an idiot, you will work 8 hours a day, but then spending 20% of time on things unrelated to your next promo completely dooms your chances of getting it. Some people used to take advantage of this, truth be told you're paid pretty well even at the senior level, and Google expects most people stay at that level indefinitely. Although then there's the question of why one wouldn't just take it easy at work and spend their spare time on hobbies instead that Google won't own the output of. OTOH some people are taken in by the Google mythos, and they think spending 20% of their time on semi-random shit is _conducive_ to their career advancement. You get disabused of that notion after applying for a promo even once, which is when any experiments with 20% usually cease. Exceptions are few and far between. To establish this for yourself, try to find if people around you promoted to Staff and above have any real 20% projects that are actually 20% projects, that is, that take substantial time. They don't.
- ndesaulniers 6y ago> and gets to deny promo because you "spent too much time on your 20% project", as well or "while that's extremely important and beneficial to Google, it's not valuable to this PA. Thus you should unmark yourself for promo otherwise our director will tank you in committee." True story. :) Glad I'm out of that toxic group; I was able to turn my 120% project into my 100% day job and am much happier and well rewarded.
- joshuamorton 6y agoFwiw I know of more than one person promoted to senior based primarily on 20% work. I'd agree that it becomes rarer at staff+, just because your goal is to make cross Google impact and that's difficult in the context of most 20% work. But even there I know of people at that level who do 20% work. I'm not sure that they're any rarer than 20% at lower levels.
- dacracot 6y agoI'll caveat my remarks first by admitting that I nearly completely ignorant of Google's 20% policy, but since it was widely advertised, my workplace made a similar statement that one half of each Friday should be dedicated to learning something new to benefit the team and thereby our careers. All I could ever think of after this proclamation was that I was to do as I was told 85% of the time and innovate 15%. As a developer, I offended that my innovations are devalued to a time slot. I was under the impression that I was expected to innovate continuously within the confines of the deadlines given. My two cents.
- darkwizard42 6y agoDid you consider that maybe setting Friday up for everyone was to allow everyone who wanted to participate to work together without scheduling challenges or conflicts with their hired roles/team obligations? This is like saying a Hackathon is devaluing creativity because it occurs at a scheduled time...
- dacracot 6y agoI get your point, but without paragraphs of explanation, I doubt I could persuade you. I can say this... It was meant as a solitary exercise, not as a group.
- FalconSensei 6y agoBu then, if everyone stops to work alone at different times, you have a problem scheduling work things... I.e: if you want to take Tuesday afternoon to do your things, but then they need you for meetings/work on something else.
- swyx 6y agooh i love this! unintended consequences always arise - this is one of those reasons why I asked the question. thank you for sharing how this felt.
- tolbish 6y agoDon't you innovate during the other 85%? Likewise, couldn't you spend that remaining 15% doing rote, uninteresting work of your choosing? To me, the concept of 20% time is the freedom to choose what you're working on, not how you should be working.
- teen 6y agothe policy still exists tho
- iangudger 6y agoI used 20% time for things that were related to my work, but out of scope for my team. For example, I wrote a DNS library in Go for work and then I open sourced it [1] and used it to rewrite the standard library DNS client [2] as a 20% project. It actually worked out really well for me. The promo committee specifically called out my DNS project when they approved my promotion and ignored the stuff that I had been doing for my team. [1] https://golang.org/x/net/dns/dnsmessage https://golang.org/x/net/dns/dnsmessage [2] https://golang.org/cl/37879 https://golang.org/cl/37879
- forgotmypw17 6y agoAre there any companies out there that allow a 20/80 schedule, meaning 80% working on own projects?
- mcherm 6y agoYes - the vast majority of open source projects are run this way. The down side is that you don't get paid. And I think that's pretty consistent -- no one is going to pay market rates for you to spend 80% of your time on "whatever you like".
- jedberg 6y agoVC firms do. They call it Entrepreneur in Residence.
- justicezyx 6y ago20% when i left Google in 2019-04 is all but gone. It was not practiced widely. In my group, Borg, I don't know personally a single employee does that. During my tenure at Google from 2013-2019, I only know one person did that.
- mmcnl 6y agoI have trouble appreciating the 20% time. What's the fun in doing something by yourself? Isn't the exciting part about Google working at scale with resources you'd never have anyone else? Personally I feel like I would decline on 20% projects.
- grumple 6y agoYou can use the time to work on existing projects and/or with other people.
- khazhoux 6y agoFrom my time there, the most important thing about 20% time, from my POV, was the message to all engineers that innovation, personal growth, and expanding the boundaries of your work, is important to the company. It was less important whether you really engaged in a true 20% or not. The point was that the company very loudly endorsed the idea of it -- even if in practice, it was hard to get right.
- anonygler 6y agoI think it was great. The problem, in my experience, is that everything at Google is just too damn complicated these days. It's really hard to make an impact on a hard problem without an intense commitment. 20% context switching doesn't cut it. Linters, code checkers, automation tools, IDE plugins, etc, have all been plucked. There's not a lot of low hanging fruit anymore.
- mondoshawan 6y agoCurrent Googler -- AFAIK, 20% time is still a thing. You just have to clarify the project with your manager, just like you did before. I utilized it to write the Mendel development tool (mdt) for Coral boards here: https://pypi.org/project/mendel-development-tool/ https://pypi.org/project/mendel-development-tool/ On my current project, I have other Googlers spending 20% time to help the team I lead as well. 20% is very much still a thing here.
- osipov 6y agoNot at Google Cloud
- swyx 6y agothank you - i think i was misinformed by that one guy who claimed it was dead. damn.. my interest in Google rose significantly after posting this...
- mondoshawan 6y agoThere's been multiple calls that the policy is dead or 120%, neither are accurate, most spoken by folks with ulterior motives and biases.
- stjohnswarts 6y agoWould you say it's more like 120+% time or is that a misconception of the policy by HN people that have never worked at google?
- mondoshawan 6y ago120% is a misconception. 20% is volunteer. 80% is assigned. I built MDT that way, taking a few days cumulatively to work on it, and I maintain a strict 40 hour work week, with my manager's backing.
- WheelsAtLarge 6y agoCan someone give us a review how the 20% rule works/worked at Google? What I've read has always been second hand. Not directly from a Googler. I suspect that at the very least the 20% gives high employees a way to decompress for a bit by working on projects they love rather than ones that they have to do.
- ChuckMcM 6y agoMy experience while working there was that like most things the experience varied hugely depending on your manager and your current rating. For me, it was also kind of irrelevant since I'm one of those "weird" people that write code to relax in my "spare" time. Google didn't care what time of day you worked, I would find myself during the weekend trying out different things with map/reduce to see how different algorithms would need to be adapted and what not. Was that 20% time or just using the company's assets to indulge my curiosity? A bit of both I guess. As a manager I'm pretty cognizant of the risk of burnout, and one cause of burnout is being hammered by a problem day in and day out. To avoid that I always coached my team members to have "three" jobs, one was their main job, one was their time to work on things that were important but not urgent, and the third was to indulge their curiosity and learn something new or further their understanding of something. But I also respected people who wanted to just "do their job" and go home, so for them we'd keep it simple about what was expected and how it was measured.
- gravypod 6y ago(Opinions are my own) As someone who has worked for a long time at small startups (<30 people, <10eng) my "20%" projects (what other people are referring to "120%" here) that I've done on my own time have, in some cases, saved the companies I've worked for more than thousands of eng-hours and have taken less then a weekend. Attacking a core business problem from a new angle that no one else sees and designing a revolutionary approach to solving it that saves everyone time, money, and reduces stress is very common. Some examples of this from my previous job: 1. https://github.com/CaperAi/branchpoke https://github.com/CaperAi/branchpoke 2. https://github.com/CaperAi/bazel_compose https://github.com/CaperAi/bazel_compose 3. https://github.com/CaperAi/pronto https://github.com/CaperAi/pronto These were the ones that were easy to pluck from my job's monorepo and generally applicable. As someone who is leaving a small startup for Google I can also add that it's one of the biggest compensation-y things in the offer. My manager seems supportive of 20%ing, the project I'm on is an offshoot of a 20% project, and the skip level I spoke to supported the idea of building tools. So... From a management perspective the startups I've worked for have lost a senior engineer to another company more supportive of personal projects. This is very expensive as 1 senior engineer could represent 10%-40% of your eng team capacity at a small company. So, even just as an employee retention mechanism 20% of a salary spent on retaining your core engineering team and, possibly, obtaining huge benefits to overall company productivity is a worthy trade.
- swyx 6y ago> even just as an employee retention mechanism 20% of a salary spent on retaining your core engineering team and, possibly, obtaining huge benefits to overall company productivity is a worthy trade. thats a fantastic way to put it. as a businessman, 20% seems super high but who knows what the right number is. it's not 0%. i'd be careful about IP in terms of "plucking from my job's monorepo" - 20% time work is still work that they paid for. but im sure you've considered that. lastly - my qtn was not just about retention and saving money - it was also about culture - i do worry that politics and weird team dynamics arise when you basically play on a different team 20% of the time.
- gravypod 6y ago
- caturopath 6y agoIt's successful branding for a thing that happens at all companies - if people want to do things other than their core job, they can do it. They won't get too much credit for it unless it truly pays off. It isn't completely dead. Like everything in Google, it's a ton more formal than it used to be and it's super hard to get an external launch, but tons of people still participate in 20% time at every level from 'maintains important project' to 'messes around in their free time'.
- dkdk8283 6y agoI worked at a company very close to Google and we adopted the %80 rule. It was forced. You were not allowed to make changes to production on Fridays.
- swyx 6y agoif this is a joke it's not really funny
- dkdk8283 6y agoI’m serious. NCF = no change friday. It was culturally unacceptable to force people to work on weekend to fix.
- FalconSensei 6y agoWhere I work, many teams also don't push to prod on Fridays - although on our case we continue to work normally. For user-facing things, we also have code freeze at the end of the year, over the holidays.
- stjohnswarts 6y agoI do this at work on a personal level. I don't push any changes of any "large" variety as I appreciate my off time on the weekend. It would be a dead obvious pattern if management checked my commit history :)
- baccheion 6y agoWaste. At smaller companies, engineers eventually need some time to vent.. "energy". After the first ~2-3 years, most go to work in order to then go home. They have been given the education and realize there's nothing. Further, whatever they do is owned by the company. That is, only garbage would really get pushed.
- intellix 6y agoI was working at a fairly small company who tried to do the whole 20% thing. For me it was awesome as I got to work on some really valuable things without all of the bureaucracy around project management. For the more junior folk though it seemed like a waste of time as their stuff seemed more fun than valuable to the company. At Google/Atlassian is it entirely 20% on what you want or do you first need to propose and justify the value of the work you plan to do with an approval?
- stjohnswarts 6y agoemployee morale is worth a lot though and often overlooked at big corporations.
- shmoo 6y agoMy experience as a long-time Googler has been that people do 20% projects for two main reasons: 1) They want to change their role and view the 20% project as a means to an end. As an example, I worked with two 20%'ers that wanted to transfer from non-SWE to SWE roles. One of them has already succeeded, and another is hoping to be able to do so as soon as head count permits. 2) As a labor of love. As an example, we have an epitaphs page containing information about/farewells from people that have departed Google. It's not an officially supported project but is still quite popular. These kinds of projects don't necessarily lead to promotions (although the criteria for promotion have recently changed), but on balance they make people's lives better.
- mustafa52 6y agoI want a review on this website. Does this service work for providing temporary disposable numbers? http://receive-free-sms.com/ http://receive-free-sms.com/
- ffggvv 6y agofrom my experience at google. everyone is so obsessed with promo that no one does 20% projects because it distracts from their main project and hurts their performance review and delays their promo. its not even 120% time because if you have time to do 120% you should just do it on your main project to get faster promo instead of something your manager wont care about or know how to evaluate in a perf packet. the only time people did it was to try to switch teams. or if their main project was low impact/easy to do in 80% of your time so you wanted to pad perf.
- deleted 6y ago[deleted]
- martinx413 6y agoThe 20% policy definitely still exists. I am puzzled that there are so many comments saying it does not. I did a 20% project 2 years ago. My goal was to get into a new area of the company since my then current role was not going anywhere. I worked 20% on the new role and 80% on my existing role, so no extra hours required. I worked on a project that ultimately failed, but I got to know enough people in the new domain that I was able to find a project to join in that area. So as far as I'm concerned 20% is a great (and ongoing) thing about Google, even if it does not lead directly to new products.
- geekster777 6y agoXoogler here who left a few months ago. The policy totally still very much exists, although isn't "advertised" as much per say. Like, I think maybe 25% of googlers use 20% time and most are driving their own projects rather than working on some larger project they were pitched on. One of the biggest positives of 20% time was just blocking off every Wednesday - no meetings, minimal distractions, etc - for my 20% work. It was pretty refreshing and kept me at the company for probably 8 months longer than I would have without the 20% time. The other great thing is that I was able to push a project I believed in but that everyone was afraid to fund. I had ownership of something I cared about. It was something that helped out dozens of teams, helped me shape the direction of the team, and heavily pad out my perf packet. In general, folks are very protective of 20% time. My director didn't want to fund the additional maintenance cost of the project, but was respectful of the fact that it was 20% time. My manager and tech lead were in a similar boats.
- rfks 6y agoThe policy still exists (it is still encouraged, me & my coworkers used it in the last ~2 years). The "120%" issue is up to individual / manager (like many things at Google), I just took Fridays off of my main project, other people have different approaches. Whether doing 20% impacts performance / promotion - it again depends on the individual and their level, two data points: - I used 20% to start a team / role transfer, ended up on a very interesting project & team which helped my career growth - one of my coworkers used 20% to start & maintain an internal feature of a large product that directly helped his promotion case so I think 20% is great for Google and its employees (when applied wisely).
- JohnJamesRambo 6y agoWish they would spend that 20% time working on maintaining and keeping old Google projects that people use and depend on alive.
- agumonkey 6y agoNever went into a company that did this, but it would surely fit my brain, I often need personal outlet (unless the main tasks are already providing me this). It would probably drive my productivity up so I can finish the boring parts and enjoy a mind-free 20%
- simonebrunozzi 6y agoIf I remember correctly, Orkut [0] was the output of one of these 20% projects (the Wikipedia page doesn't say that; my memory might be wrong). Interesting to think that Google had an opportunity to build Facebook, but didn't pursue it. And yes, of course, years later there were Wave, etc. [0]: https://en.wikipedia.org/wiki/Orkut https://en.wikipedia.org/wiki/Orkut
- habosa 6y agoGoogler here: I did a true 20% project once. I was filing a ton of bugs about Android internally and the process was crappy, so I found another person and we started working on an app to report bugs directly from the phone. This went from nothing to a company-wide utility to a publicly launched app with full-time engineers (although I stopped my 20% contributions before that) [0]. So I think in this case we had a clear positive impact on the company that would not have happened without the 20% program. This app was launched by 2-3 20% engineers and 1 20% PM. This was way outside my core job role (Developer Relations) but it was a great experience and I believe I was rewarded for it when it came time to apply for promotion. People always seem to focus on the question of 20% time vs 120% time, but I don't think that question can be answered. Google does not have a time clock culture. I work about 45-50 hours a week. I have coworkers who work 30, I have others who work 70. When we had an office I got there at 7:45am, I sat near people who arrived at 11:00am. So basically time management is personal and so is how you choose to do a 20% project. In all cases the mandate is "get your work done". 0: https://9to5google.com/2019/03/12/android-q-beta-feedback-app/ https://9to5google.com/2019/03/12/android-q-beta-feedback-ap...
- bootsz 6y ago20% projects (and the policy supporting them) are very much still a thing at Google. Not sure how many people actually participate in one but my perception is that it is a relatively low percentage of employees.