Jump to content

Side project time

Add links
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Greenrd (talk | contribs) at 02:10, 26 February 2023 (→Benefits and detriments: clarifications). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Side project time is a type of employee benefit constituting a guarantee from employers that their employees may work on their personal projects during some part (usually a percentage) of their time at work.[1][2] Side project time is limited by two stipulations: what the employee works on is the intellectual property of their employer, and if requested, an explanation must be able to be given as to how the project benefits the company in some way, even tangentially.[3][4]

Technology company Google is credited for popularizing the 20% concept.[5] It led to the development of products such as Gmail and AdSense.[6][7] Though the program's continuity has been questioned[8] Google states it remains an active program.[9]

Other major companies that have at one time or another offered some or all of their employees the benefit include the BBC (10%),[10] Apple (a few contiguous weeks yearly),[2] and Atlassian (20%).[5] Some, such as LinkedIn, have trialed more restrictive versions of such initiatives in which employees must first pitch their project and have it approved by their manager to work on it during company time.[5]

Side project time has been criticized by some academics, such as Queens College sociology professor Abraham Walker, as "exploitative" due to how it grants employers the intellectual property rights over the personal business ideas of their employees that the employer would have never requested to be worked on otherwise.[11]

History

3M and 15% time

The 15% project was an initiative established by corporation 3M. At the time of this program's implementation, the United States' work force was composed of highly inflexible employment opportunities in rigid business structures.[12][13] After WWII ended, 3M developed an ethos: Innovate or die, which provided enterprise for the company and inspired the launch of this program. This original project has widely successful outcomes, resulting in scientists developing and manufacturing products that remain utilized internationally, even decades later.[citation needed]

Google implementation

Since before its IPO in 2004[14] the founders of Google have encouraged the 20% project system. Within Google, this initiative became known as the "20% Project."[5] Employees were encouraged to spend up to twenty-percent of their paid work time pursuing personal projects. The objective of the program was to inspire innovation in participating employees and ultimately increase company potential. Google's 20% Project was influenced by a comparable program, launched in 1948, by manufacturing multinational 3M which guaranteed employees "15% time"—to dedicate up to 15 percent of their paid hours to a personal interest;[15][13] it was during his side project time that Arthur Fry invented the Post-It Note.[12] For Google's part, Gmail and AdSense both arose out of side projects.[6][7]

As recognition of the clear benefits of retaining such a scheme grew, schools have replicated this system for their students in the classroom environment. The production of such creatively stimulated, ungraded work allows for peers to experiment with ideas without fear of assessment and increases their involvement in their general studies.[16] Further, other small businesses are now using this system in their day-to-day functions, including software company Atlassian, as a safeguard to counter damp growth rates and a general lack of innovation.[citation needed]

In 2013, Google discontinued 20 percent time.[8]

The 20% Project is responsible for the development of many Google services. Founders Sergey Brin and Larry Page advised that workers "spend 20% of their time working on what they think will most benefit Google".[17] Google's email service 'Gmail' was created by the developer Paul Buchheit on his 20% time. In his project "Caribou", Buchheit used his knowledge from university software experience to create the service. The freedom to use his time in such a way allowed him to ultimately develop a fundamental Google service. Buchheit's colleague, Susan Wojcicki, utilised her time to create their product AdSense.[citation needed] Finally, developer Krishna Bharat created Google News as an individual pursuit and hobby.

Other companies

Australian enterprise company Atlassian has been using the 20% project since 2008.[18] Co-founder Mike Cannon-Brookes stated that "innovation slows as the company grows".[19] And as such the scheme was introduced to re-inspire innovation. The induction of the system was a six-month trial, granting $1 million to engineers and allowing them to work on private projects based on personal interests.[20] Part of this 20% time is their annual "Ship It'"day, where employees are challenged with a task to create any product and then ship this item within 24 hours.[21] Workers created products which ranged from refined beer to 'Jira' software updates.

American project management software company TargetProcess adopted the 20% project for their small company. The company was composed of 110 members when the initiative was introduced. Company founder Michael Dubakov identified a lack of innovation from his employees, with their daily routines occupied with monotonous work. Dubakov was inspired by the output derived from 20% projects in Google and 3M but was unsure about the limit on employee involvement. Despite driving the project at Google, only certain employees were granted this time – meaning most workers could not use this opportunity for innovation. Dubakov decided to allow all employees to pursue individual projects, to reduce boredom and inspire innovation. Initially the company introduced "Orange Fridays" in 2013, an allocated 4 hours of each Friday afternoon to attend workshops, learn about and develop new technology. From this, the company saw a rise in investment opportunities and company growth.[19] The company developed a culture to innovate, with no pressure applied to employees moving from their regular schedule to innovate and learn.

In 2016, TargetProcess experimented with open allocation. This initiative was an extension of "Orange Fridays" and was applied to a majority of employees. The goal was to provide a more comprehensible user experience and amend issues with the TargetProcess product. Involved members were granted the opportunity to manage their schedule and individually pursue new product design. This experiment highlighted positive growth in the company, observed from a 10-month review.[22] Dubakov implemented deadlines, ensuring each individual met their personal goals. As a result, members reported to have felt an increase in personal motivation. The main company detriment that arose from this experiment was decreased company unity. With each employee pursuing individual projects, a lack of management led to the company embodying the different visions from all employees, affecting company alignment. This experiment was ceased after the founder believed the company was unprepared for this shift in work dynamic.[23] TargetProcess would focus on backlog creation, with training programs for product development operating in conjunction. Self-organisation was a key concern for their 20% project as not all employees could manage their projects whilst reaching regular work deadlines. Another issue identified during this experiment was the reward scheme, granted when an individual initiated a new product or scheme. This undermined the work of those employees not involved in the experiment, and led to an imbalance in motivation within the company.

Notable projects

Gmail

Main article: Gmail
See also: History of Gmail

From the 20% Project, Google produced forefront services that drive the company today. One outcome of this project was Gmail, Google's email service. Developer Paul Buchheit created this service under the project title 'Caribou'. This service was developed without the awareness of other employees and was publicised several years later. By 2006, this service was available on computers and mobile devices. After 8 years of activity, Gmail had 425 million users.[citation needed] In May 2014, Gmail set the record as the first Android application to reach one billion installations on the Google Play store.[citation needed]

AdSense

Main article: Google AdSense

The 20% Project aided in the development of AdSense, a program where publishers can produce media advertisements for a targeted audience. This service allows website publishers to generate revenue on a per-click basis. This service was publicly released on June 18, 2003. This service was envisioned by Gmail's founder Paul Buchheit, who wanted appropriate ads to run throughout the Gmail service, but the project was pursued by Susan Wojcicki, who curated a team of developers who created the platform in their dedicated 20% time.[citation needed] After two years of its inception, the service was generating 15 percent of the company's revenue.[citation needed] The service can now offer ads in the form of simple text, flash video or rich media.

Google News

Main article: Google News

The news aggregator Google News is another result of the 20% Project. This service was publicized in January 2006, though the beta was introduced in September 2002. The creator of this service was Krishna Bharat, who developed this software in his dedicated project time. The service sources from 20,000 different publishers, providing articles in 28 languages. Now, the service has many new features, including Google News Alerts, which emails "alerts" on chosen keyword topics.[citation needed]

Google Dremel

Main article: Dremel (software)

Dremel was conceived at Google in 2006 as a "20 percent" project by Andrey Gubarev.[24]

Atlassian

Main article: Atlassian

In 2008, Atlassian announced its "20% Time Experiment", a six-month trial that was later extended to a full year.[25][26] After six months of the project initiating, the company saw major improvements to Jira, Bamboo and Confluence. The Bamboo team introduced Stash 1.0 in May throughout the dedicated project time.[19] Throughout two designated 'Innovation Week' workshops, the company shipped 12 features. At the end of the experiment, surveyed developers expressed that the biggest problem they faced was scheduling time for 20% work on top of the pressure to deliver new features and fix bugs. As a result, based on the number of developers who actually participated, the time allocated was closer to "1.1% Time."[26]

A related initiative is Atlassian's quarterly 24-hour "ShipIt" hackathon, which allows employees to pursue any project. In the past, employees have used this time to refine Jira Service Desk[27] and improve the Jira software for loading screens.[citation needed]

TargetProcess

TargetProcess implemented 20% Project initiatives such as the Open Allocation Experiment and Orange Fridays to inspire innovation from employees. Since the implementation of the project, investment opportunities have risen.[28] The company grew over 10% between 2008 and 2016 during the project's operation. Founder Michael Dubakov observed increased enthusiasm from employees.

Benefits and detriments

The 20% Project is designed to let employees experiment without the pressure of company decline or the threat of unemployment. For companies that thrive from the conception of services and products, innovative and entrepreneurial thought is vital to success.[15]

However, for an operating business, productivity can be negatively affected by the 20% Project. The loss of time previously spent on major company-aligned projects can negatively affect a company's overall performance.[29]

The allocation of this project time is not consistent. Former Google employee and Yahoo! CEO Marissa Mayer once stated "I've got to tell you the dirty little secret of Google's 20% time. It's really 120% time."[17]

Chris Mims mentioned that the 20% Project was "as good as dead".[6] This is a concern as it suggests that this project is destructive over long-term periods. In Google executive Laszlo Bock's book, Work Rules!, he mentions that the concept has "waxed and waned." He states that workers in fact dedicate 10% of their time on personal projects, increasing focus time after the idea begins to "demonstrate impact." He mentions that "the idea of 20 per cent time is more important than the reality of it." Workers should always be driven towards individual innovation, yet it should operate "somewhat outside the lines of formal management."[citation needed]

Atlassian Co-Founder Mike Cannon-Brookes implemented the 20% Project as a test to see if it produced any notable improvements or detriments to the company's output. They funded a six-month trial with one million Australian dollars. During this process, workers tackled inherent structural difficulties within the scheme. An employee mentioned that it was difficult to balance this 20% time "amongst all the pressures to deliver new features and bug fixes.";[20] the program introduced more deadlines for their employees. As a result, the company found that this 20% Project in fact became 1.1% of their working time.[20] Another issue faced was the difficulty in the organisation and team-work involved in the projects. As employees would organise groups to create new software, they would struggle to work with employees who had other commitments and alternate time schedules.[22] The company blogs have included fewer references to the 20% Project over the last decade with references that this scheme loses effect in long-term practices.[17] The company's 'Ship It' day still highlights the prosperity of time dedicated to employee-based innovation.[21]

Dubakov reported that the 20% Project proved beneficial for Target Process. The benefit of this separated time is that each member feels less pressure to complete tasks, and is able to advance their skill set and to review previous work. This time was not only used for new projects but for job-related training.[28] This allocation of time allowed for individuals to complete single tasks, improving time to delivery but negatively affecting synergy. The company reflected an emergent vision as a result of collective individual projects.[citation needed]

See also

References

  1. ^ Robinson, Adam (12 March 2018). "Google Employees Dedicate 20 Percent of Their Time to Side Projects. Here's How It Works". Inc.com. Retrieved 8 November 2021.
  2. ^ a b Cheng, Jacqui (13 November 2012). "Apple's Tim Cook beefing up employee perks, personal project time". Ars Technica. Retrieved 8 November 2021.
  3. ^ Geitz, Samantha (6 December 2016). "Why You Should be Giving Your Developers 20% time". Tighten. Retrieved 8 November 2021.
  4. ^ Bick, Julie; Mediratta, Bharat (21 October 2007). "The Google Way: Give Engineers Room". The New York Times. ISSN 0362-4331. Retrieved 8 November 2021.
  5. ^ a b c d Xu, Tammy (6 October 2020). "How Side Project Programs Foster Creativity at Work". Built In. Retrieved 8 November 2021.
  6. ^ a b c Mims, Christopher (16 August 2013). "Google's "20% time," which brought you Gmail and AdSense, is now as good as dead". Quartz. Retrieved 8 November 2021.
  7. ^ a b D'Onfro, Jillian (18 April 2015). "The truth about Google's famous '20% time' policy". www.businessinsider.com. Retrieved 31 May 2019.
  8. ^ a b Nisen, Max (16 August 2013). "Google's Obsession With Efficiency Has Killed Its Most Famous Perk". Business Insider. Retrieved 24 September 2020.
  9. ^ Murphy, Bill Jr. (1 November 2020). "Google Says It Still Swears By the 20 Percent Rule to Find Big Ideas, and You Should Totally Copy It". Inc.com. Retrieved 17 August 2022.
  10. ^ Ferne, Tristan (8 January 2008). "BBC - Radio Labs: 10 percent time". www.bbc.co.uk. Retrieved 8 November 2021.
  11. ^ Walker, Abe (2011). "Creativity loves constraints": The paradox of Google's twenty percent time. Ephemera, 11: 369–386.
  12. ^ a b Goetz, Kaomi (1 February 2011). "How 3M Gave Everyone Days Off and Created an Innovation Dynamo". Fast Company. Retrieved 31 May 2019.
  13. ^ a b Kretkowski, Paul D. "The 15 Percent Solution". Wired.
  14. ^ ""An Owner's Manual" for Google's Shareholders". Alphabet Investors Relations. Retrieved 28 June 2021.
  15. ^ a b "The Tech Classroom - What is the 20% Project in Education?". sites.google.com. Retrieved 31 May 2019.
  16. ^ "The Tech Classroom - What is the 20% Project in Education?". sites.google.com. Retrieved 13 June 2019.
  17. ^ a b c D'Onfro, Jillian (18 April 2015). "The truth about Google's famous '20% time' policy". Business Insider Australia. Retrieved 13 June 2019.
  18. ^ "Atlassian's 20% Time Experiment". Work Life by Atlassian. 10 March 2008. Retrieved 31 May 2019.
  19. ^ a b c "Atlassian's 20% Time Experiment". Work Life by Atlassian. 10 March 2008. Retrieved 13 June 2019.
  20. ^ a b c "Atlassian's 20% Time: A Year in Review". Work Life by Atlassian. 19 February 2009. Retrieved 31 May 2019.
  21. ^ a b Atlassian. "ShipIt Days". Atlassian. Retrieved 31 May 2019.
  22. ^ a b "Innovation Week – 20% time in a box". Work Life by Atlassian. 10 September 2012. Retrieved 31 May 2019.
  23. ^ Taucraft (3 May 2017). "Open Allocation Experiment". Targetprocess - Visual management software. Retrieved 13 June 2019.
  24. ^ Andrey Gubarev; Dan Delorey; Geoffrey Michael Romer; Hossein Ahmadi; Jeff Shute; Jing Jing Long; Matt Tolton; Mosha Pasumansky; Narayanan Shivakumar; Sergey Melnik; Slava Min; Theo Vassilakis (2020). "Dremel: A Decade of Interactive SQL Analysis at Web Scale". PVLDB: 3461–3472. Retrieved 30 September 2022.
  25. ^ Cannon-Brookes, Mike (10 March 2008). "Atlassian's 20% Time Experiment". Atlassian. Retrieved 12 June 2022.
  26. ^ a b Rotenstein, John (19 February 2009). "Atlassian's 20% Time: A Year in Review". Atlassian. Retrieved 12 June 2022.
  27. ^ Price, Dominic; Braddock, Philip (14 October 2019). ""24 hours of opportunity": behind the scenes of ShipIt". Work Life by Atlassian.
  28. ^ a b "This Small Company Is Making '20% Time' Work". TLNT. 18 May 2017. Retrieved 13 June 2019.
  29. ^ Ross, Alastair (3 June 2015). "Why did Google abandon 20% time for innovation?". HRZone. Retrieved 13 June 2019.
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Side_project_time&oldid=1141641735"