Holacracy

Summary

Holacracy is a method of decentralized management and organizational governance, which claims to distribute authority and decision-making through a holarchy of self-organizing teams rather than being vested in a management hierarchy.[1][2] Holacracy has been adopted by for-profit and non-profit organizations in several countries.[3] This can be seen as a greater movement within organisational design to cope with increasing complex social environments, that promises a greater degree of transparency, effectiveness and agility.[4]

Origins

edit

The term is found in print for the first time in the adjectival form holocratic in a book from the Collège de 'Pataphysique in May 1957.[5]

The Holacracy system was developed at Ternary Software in Exton, Pennsylvania.[6] Ternary founder Brian Robertson distilled the company's best practices into an organizational system that became known as Holacracy in 2007. Robertson later developed the "Holacracy Constitution" which lays out the core principles and practices of the system. In 2011, he released a Manifesto 16 of Holacracy which was later developed in June 2015, as the book Holacracy: The New Management System for a Rapidly Changing World, that details and explains his practices.[2] He claims that it resembles Scaled Agile Framework, Sociocracy and Nexus.[7] Robertson claims that the term holacracy is derived from the term holarchy; the latter was coined by Arthur Koestler in his 1967 book The Ghost in the Machine.[8]

Koestler wrote that a holarchy is composed of holons (Greek: ὅλον, holon neuter form of ὅλος, holos "whole") or units that are autonomous and self-reliant, but also dependent on the greater whole of which they are part.[9] Thus a holarchy is a hierarchy of self-regulating holons that function both as autonomous wholes and as dependent parts.[9]

Influences and comparable systems

edit

Holacracy, which is an alternative to command-and-control,[10] is one of several systems of flat organization. It has been compared to sociocracy, a system of governance developed in the second half of the 20th century.[11][12]

Essential elements

edit
  • Roles instead of job descriptions: The building blocks of Holacracy's organizational structure are roles. Holacracy distinguishes between roles and the people who fill them, as one individual can hold multiple roles at any given time. A role is not a job description; its definition follows a clear format including a name, a purpose, optional "domains" to control, and accountabilities, which are ongoing activities to perform. Roles are defined by each circle—or team—via a collective governance process, and are updated regularly in order to adapt to the ever-evolving needs of the organization.[2]
  • Circle structure: Holacracy structures the various roles in an organization in a system of self-organizing (but not self-directed) circles. Circles are organized hierarchically, and each circle is assigned a clear purpose and accountabilities by its broader circle. However, each circle has the authority to self-organize internally to best achieve its goals. Circles conduct their own governance meetings, assign members to fill roles, and take responsibility for carrying out work within their domain of authority. Circles are connected by two roles known as "lead link" and "rep link", which sit in the meetings of both their circle and the broader circle to ensure alignment with the broader organization's mission and strategy.
  • Governance process: Each circle uses a defined governance process to create and regularly update its own roles and policies. Holacracy specifies a structured process known as "integrative decision making" for proposing changes in governance and amending or objecting to proposals. This is not a consensus-based system, not even a consent-based system, but one that integrates relevant input from all parties and ensures that the proposed changes and objections to those changes are anchored in the roles' needs (and through them, the organization's needs), rather than people's preferences or ego.
  • Operational process: Holacracy specifies processes for aligning teams according to operational needs, and requires that each member of a circle fulfill certain duties in order to work efficiently and effectively together.[13] There are also key roles to help organise the process and workflow of each circle including Facilitator, Secretary, Lead Link, and Rep Link.[2]

In contrast to the governance process, which is collective and integrative, each member filling a role has a lot of autonomy and authority to make decisions on how to best achieve his or her goals. Some have described the authority paradigm in Holacracy as completely opposite to the one of the traditional management hierarchy; instead of needing permission to act or innovate, Holacracy gives blanket authority to take any action needed to perform the work of the roles, unless it is restricted via policies in governance or it involves spending some assets of the organization (money, intellectual property, etc.)[14] Holacracy is highly biased toward action and innovation: it defaults to autonomy and freedom, then uses internal processes to limit that autonomy when its use in a specific way turns out to be detrimental.

Holacracy specifies a tactical meeting process that every circle goes through, usually on a weekly basis. A particular feature of this last phase, known as "triage", is to focus discussions on the concrete next steps needed by the individual who added the agenda item to address his or her issue.[15] The intention is to avoid large, unproductive discussions dominated by the louder voices.[16]

Its developer was described by The New York Times as "a computer programmer with no training in human resources, let alone occupational psychology" and The Wall Street Journal identified the requirement for "every decision must be unanimous" as detrimental.[17][6] They also reported that "Fifteen percent of an organization’s time is spent in" ($27 billion of them "unproductive") meetings and made mention of Robertson's book.[18][19]

Contemporary practice

edit

In the U.S., for-profit and not-for-profit organizations have adopted and practiced Holacracy. Examples include Zappos.[17][20] Medium used Holacracy for several years before abandoning it in 2016.[21] A small number of research projects have reported the use of this style of management within the area of software development who promote its benefits for the search for greater innovation but raise concerns such as lack of usual structures and cultural habits around organising work, but more research is needed.[2][7][4]

The New York Times wrote in 2015 that "The goal of Holacracy is to create a dynamic workplace where everyone has a voice and bureaucracy doesn’t stifle innovation."[17] The Wall Street Journal had already asked in 2007 "Can a Company Be Run as a Democracy?" (and conceded that it "sounds like a recipe for anarchy").[6] The answer reported came when 18 percent of the employees at an online seller which had adopted this "radical self-management system" quit.[22]

Claimed advantages

edit

Various claims have been made in respect of Holacracy. It is said to increase agility, efficiency, transparency, innovation and accountability within an organization,[23] and to encourage individual team members to take initiative and gives them a process in which their concerns or ideas can be addressed.[6] Further that the system of distributed authority reduces the burden on leaders to make every decision and can speed up communications and decision making processes (but this can introduce its own challenges).[4] According to Zappos's CEO Tony Hsieh, Holacracy makes individuals more responsible for their own thoughts and actions.[17]

Criticisms

edit

Steve Denning warned against viewing Holacracy as a panacea, claiming that instead of removing hierarchy, decisions are funneled down from circle to circle in a clear hierarchy, with each subsequent circle knowing less about the big picture than the one above.[24] He also claimed that the rules and procedures are very detailed and focused on "administrivia."[24] Lastly, Denning added that the voice of the customer was missing from the Holacracy model, concluding that for agile and customer-focused companies such as Zappos, Holacracy is a way to add administrative rigor, but that Holacracy would not necessarily work well in an organization that did not already have agility and passion for the customer.[24] HolacracyOne partner Olivier Compagne replied to those criticisms on the company's blog, claiming that Denning's criticisms misunderstand Holacracy.[25]

Problems occur when transitioning to this system, particularly if older systems of management are allowed to become a hidden structure and system of power, in addition to this, individuals' space can become lost within the constant connectedness.[4]

In moving away from Holacracy, Andy Doyle of Medium noted that "for larger initiatives, which require coordination across functions, it can be time-consuming and divisive to gain alignment" and that Medium believed that "the act of codifying responsibilities in explicit detail hindered a proactive attitude and sense of communal ownership". They also noted that the inaccurate media coverage of Holacracy created a challenge for recruitment.[21]

At Zappos, about 14% of the company left voluntarily in 2015 in a deliberate attempt by Zappos to only retain employees who believed in holacracy.[26]

Other criticisms include a "one-size-fits-all" approach,[27] layers of bureaucracy and more psychological weight.[28]

See also

edit

References

edit
  1. ^ Rudd, Olivia (April 24, 2009). Business Intelligence Success Factors: Tools for Aligning Your Business in the Global Economy. John Wiley & Sons.
  2. ^ a b c d e Liebert, Filip (2020). "Holacracy as a new approach to new product development in it industry – case study". Zeszyty Naukowe. Organizacja i Zarządzanie / Politechnika Śląska. z. 145 (145): 279–296. doi:10.29119/1641-3466.2020.145.21. ISSN 1641-3466.
  3. ^ Röll, Juliane (2015). "Organisations running on Holacracy". structureprocess.com. Retrieved July 8, 2020.
  4. ^ a b c d Schell, Sabrina; Bischof, Nicole (2021). "Change the way of working. Ways into self-organization with the use of Holacracy: An empirical investigation". European Management Review. 19: 123–137. doi:10.1111/emre.12457. ISSN 1740-4762. S2CID 235533720.
  5. ^ Vue cavalière sur la mignonette, by Jean Ferry. Publications Secrêtes du Collège de 'Pataphysique (L'Hexaèdre ed.). Paris. 2020. p. 148. ISBN 978-2-9192-7118-4.{{cite book}}: CS1 maint: location missing publisher (link)
  6. ^ a b c d Jaclyne Badal (April 23, 2007). "Can a Company Be Run as a Democracy?". The Wall Street Journal.
  7. ^ a b Bhandari, Rabin; Colomo-Palacios, Ricardo (July 2019). "Holacracy in Software Development Teams: A Multivocal Literature Review". 2019 19th International Conference on Computational Science and Its Applications (ICCSA). pp. 140–145. doi:10.1109/ICCSA.2019.00013. ISBN 978-1-7281-2847-4. S2CID 203655347.
  8. ^ Arthur Koestler (1967). The Ghost in the Machine. Pan Books. ISBN 978-0-3302-4446-6.
  9. ^ a b Koestler, Arthur (1967). "The Ghost in the Machine". Psychiatric Communications. 10 (2). Penguin Group: 45–8. PMID 5735264.
  10. ^ Nick Rockwell (July 16, 2018), "Talking Technology: Aaron Dignan and Spencer Pitman", The New York Times, retrieved December 8, 2022
  11. ^ Steele, Robert David (June 5, 2012). The Open-Source Everything Manifesto. North Atlantic Books. p. 47.
  12. ^ "Holacracy and Sociocracy". adeeperdemocracy.org. 2010. Retrieved January 9, 2014.
  13. ^ Röll, Juliane (2014). "Energizing Project Roles (Holacracy Basics, Part 1)". structureprocess.com. Retrieved July 8, 2020.
  14. ^ Work, Daniel (2015). "Part 2: Permission Cultures". Medium. Retrieved May 29, 2015.
  15. ^ Compagne, Olivier (2015). "One Thread at a Time". medium.com. Retrieved May 29, 2015.
  16. ^ Meade, Kristy (2015). "Holacracy: A Step Toward Equality". medium.com. Retrieved May 29, 2015.
  17. ^ a b c d David Gelles (July 17, 2015). "At Zappos, Pushing Shoes and a Vision". The New York Times. Retrieved December 7, 2022.
  18. ^ {{cite book title=Holacracy: The New Management System for a Rapidly Changing World |author=Brian Robertson |year=2015 |publisher= Henry Holt & Company |isbn= 978-1-6277-9429-9}}
  19. ^ Virginia Heffernan (February 25, 2016), "Meet Is Murder", The New York Times, retrieved December 8, 2022
  20. ^ Groth, Aimee (December 30, 2013). "Zappos is going holacratic: no job titles, no managers, no hierarchy". Quartz. Retrieved December 31, 2013.
  21. ^ a b Doyle, Andy (2016). "Management and Organization at Medium".
  22. ^ David Gelles (January 13, 2016). "The Zappos Exodus Continues After a Radical Management Experiment". The New York Times. Retrieved December 7, 2022.
  23. ^ James, Michelle (2012). Navigating the New Work Paradigm. Center for Creative Emergence.
  24. ^ a b c Denning, Steve (January 15, 2014). "Making sense of Zappos and Holacracy". Forbes. Retrieved February 21, 2014.
  25. ^ Compagne, Olivier (January 21, 2014). "Holacracy Is Not What You Think". HolacracyOne's Blog. Retrieved February 21, 2014.
  26. ^ Groth, Aimee (January 13, 2016). "Zappos has now lost 18% of its employees to its radical buyout offer". Quartz. Retrieved December 30, 2016.
  27. ^ Culen, Julia (April 3, 2016). "Holacracy: not safe enough to try". Retrieved December 30, 2016.
  28. ^ Groth, Aimee (December 21, 2016). "Zappos is struggling with Holacracy because humans aren't designed to operate like software". Quartz. Retrieved December 30, 2016.
edit
  • Holacracy website
  • (2006) Interview with Brian Robertson on Holacracy