This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)(Learn how and when to remove this template message)
Open allocation refers to a management style in which employees are given a high degree of freedom in choosing what projects to work on, and how to allocate their time. They do not necessarily answer to a single manager, but to the company and their peers. They can transfer between projects regardless of headcount allowances, performance reviews, or tenure at the company, as long as they are providing value to projects that are useful to the business goals of the company. Open allocation has been described as a process of self-organization. Rather than teams and leadership arrangements existing permanently in a company, such relationships form as they are needed (around important projects) and disband when they are no longer necessary. Additionally, open allocation implies that projects are not unilaterally created and staffed by executive mandate. Rather, the person forming the project (who might not be an official manager) is responsible for convincing others to invest their time, energy, and careers into the effort.
Google introduced and publicised an unusual perk known as 20% time, in which - in theory - employees have freedom over one-fifth of their working time, which may be put into a personal project or a high-priority internal effort outside of management's direction. However, the other 80% of the time employees would be still working under closed allocation, and also may not in practice be able to use their 20% time all of the time, for example due to deadline pressures.
While startups vary wildly in work environment quality and employee autonomy, one of the main selling points of technology startups in the early 21st century has been a claim - demonstrably true of the best startups, but not of all of them - that employees enjoy a high level of autonomy, at a level traditionally only seen in basic research labs.
GitHub and Valve, in the early 2010s, became well known for having such environments. In 2013, Tom Preston-Werner gave a talk at Oscon in which he spoke about the importance of open allocation to GitHub's success.
Leadership under open allocation
Organizations using open allocation do not give middle managers unilateral control over their reports' work. People management, product direction, and project-specific leadership are, in this way, decoupled. One argument in favor of this is that when the people defining projects no longer have the unilateral ability to terminate employees or deprive them of opportunity, better projects and leaders (those that can convince, rather than coerce) will emerge. Middle management may play roles, however, in mentoring, handling of conflict (as an absolute last line of dispute resolution), and (especially) ensuring that new hires are appropriately "onboarded" into the open allocation system.
Leadership in an open-allocation organization is typically organic; the person to propose the project will lead it, if he or she can convince others to follow. When projects end, the leaders may rotate back into being "followers", and there is no stigma attached to this. Leading and following are temporary distinctions and largely by choice; one may choose to follow in order to learn more about a different part of the business, for example. Ideally, the leader for each project will be the most committed, capable or passionate person involved, and companywide rank (which may not exist at all) has little to no bearing on the selection.
Performance reviews in open allocation companies are handled in a variety of ways. Valve uses stack ranking driven by peer review to determine raises and bonuses, but unlike the hated stack-ranking regimes of some other technology companies, these do not initiate termination or interfere with internal mobility, but are strictly used to determine compensation.
Benefits of open allocation
- Information: In a closed-allocation company, the people doing the work and those deciding what is to be worked on are typically disjoint sets. This means that impractical projects are often proposed because the people responsible for the firm's executive function are deprived of important knowledge—in particular, whether the people doing the work consider the project worth investing their time, energy, and reputation. (If the answer is negative, they typically cannot communicate it, especially in at-will employment situations.)
- Peer review can be used and encouraged not only for source code, but also design, business strategy, and publicity. More people are allowed input into the issues they consider important.
- Motivation: Employees who have chosen their projects are more likely to be productive and highly motivated. There is more personal pride at stake when the person selected or defined where to put his or her efforts.
- Personal responsibility: People can no longer blame bad project assignments or inept immediate managers for underperformance, since those are results of their own choices. A person who worked on a bad project, in an open-allocation environment, is at fault.
- Efficiency: Hierarchies of people (which frequently duplicate efforts) are replaced with conceptual hierarchies, but extra-hierarchical collaboration (the norm, in an open-allocation company) allows cross-domain knowledge to be formed and deployed. An employee who wants to start a new project that may add value to the business can do so immediately, but those that require investment of others' resources and time require convincing them that the idea is valuable. In essence, workers are trusted with their own time, but disallowed from attempting to control others' time.
- Communication: In the ideal open-allocation environment, anyone can communicate with anyone else in the company, without having to pass a message up and down a management relay.
- Less waste: One theory on the causes of corporate efficiency is that much unused or low-quality work is the "promotion-oriented" kind, directed by a manager for his or her career goals while generating little or no value for the company. Under open allocation, it is difficult to staff such projects. However, unpleasant but important work will get done, because performing it well will lead to more esteem among peers, and make it easier to lead others in the future.
- Low turnover: Open-allocation companies typically have low turnover. People rarely leave, because the work environment is considered superior to the norm; they are rarely fired, because there are so many avenues toward success that most people can find a project where they can perform well.
Because open allocation is an unusual organizational style, it can be at odds with external demands on an organization. For example, consulting companies that promise a certain number of staff will work on a project must assign work to people in order to meet those commitments. Additionally, regulatory pressures such as Sarbanes-Oxley may require that people are assigned to certain duties.
Additionally, open allocation's strongest successes are in businesses in the areas of science, technology, and in particular, software - the most successful of which are typically staffed by highly competent and educated people. Whether the successes of open allocation apply more generally to other types of organizations is an open question.
Finally, terminating employees in an open-allocation environment can be challenging, because establishing a performance-based case in such a flexible environment is difficult. While open allocation generally creates fewer of the "unlucky" low-performers who landed on the poorly-fitting projects or with incompatible managers, and therefore tends to reduce turnover (voluntary and involuntary) dramatically, it doesn't provide a mechanism for getting rid of severe under- or non-performers who "hide" in the organization. This has not been an issue to this point, if only because the companies using open allocation have been highly selective ones that can hire people with strong track records. Furthermore, the increase in performance among high performers under open allocation is typically so dramatic as to counteract any risk of decline among the lower performers.
Organizations using open allocation
|Organization||Industry||Type||Number of employees||Used open allocation|
|Valve||Video games||Private company||400||1996 (founding year) - date|
|GitHub||Technology||Private company||175||2008 (founding year) - 2014|
|Treehouse||Technology||Private company||60||June 20, 2013 - date|
|W. L. Gore and Associates||Manufacturing||Private company||9,840||1958 (founding year) - date|
|Monk Development||Software as a Service||Private company||25-30||2013 - date|
|Targetprocess||Software as a Service||Private company||110||2016 - date|
At Valve, employees' desks have wheels under them, allowing them to move to another team with ease - a symbolic as well as practical marker of Valve's open allocation approach - and physically reorganize as their projects demand.
Treehouse allows any team member to switch teams at any time, but says that it is "not cool" to leave a team at a critical time or when you are needed by your team-mates, and such an action would be reflected in poor performance reviews.
- Dannen, Chris (18 October 2013). "Inside GitHub's Super-Lean Management Strategy--And How It Drives Innovation". Fastcolabs. Retrieved 28 October 2013. CS1 maint: discouraged parameter (link)
- Roach, Michael (24 September 2014). "Founder or Joiner? The Role of Preferences and Context in Shaping Different Entrepreneurial Interests". Management Science. doi:10.1287/mnsc.2014.2100. SSRN 2170954 – via Social Science Research Network.
- Caulkin, Simon (2 November 2008). "Gore-Tex gets made without managers". The Observer.
- "Why There Are No Bosses at Valve". Bloomberg BusinessWeek. 27 April 2012. Retrieved 1 September 2013. CS1 maint: discouraged parameter (link)
- Kelion, Leo (23 September 2013). "Valve: How going boss-free empowered the games-maker". BBC News. Retrieved 1 October 2013. CS1 maint: discouraged parameter (link)
- Rusli, Evelyn (17 July 2014). "Harassment claims make startup GitHub grow up". Wall Street Journal. Retrieved 18 July 2014. CS1 maint: discouraged parameter (link)
- Carson, Ryan (18 September 2013). "How to set priorities, create budgets and do project management in a #NoManager company". Retrieved 2 November 2013. CS1 maint: discouraged parameter (link)
- Carson, Ryan (17 September 2013). "No Managers: Why We Removed Bosses at Treehouse". Archived from the original on 21 September 2013. Retrieved 2 November 2013. CS1 maint: discouraged parameter (link)
- "W. L. Gore & Associates - Best Companies to Work For 2013". Fortune. February 4, 2013. Retrieved October 31, 2013. CS1 maint: discouraged parameter (link)
- "Our Culture". W. L. Gore & Associates. Retrieved 2 November 2013. CS1 maint: discouraged parameter (link)
- Cutting Edge Agile, Part II: Open Allocation Agile SD. 5 January 2015.
- "How we (un)plan the future". Targetprocess. October 2016.