Can Holacracy Help Organizations be more Agile?
Agile requires a lot of discipline around practices. Holacracy requires a lot of discipline around governance and structure.

Holacracy and Agile have a considerable degree of synergy. And they are both comparatively easy in the small; increasingly difficult to scale. They have a degree of overlap. But Holacracy won't replace Agile; Agile won't replace Holacracy. Holacratic structure is a good one for an agile shop, but it's not the only structure that works, and it can only work in a company made up entirely of “grown ups.” Agile is all about relationships and collaboration at its core, so holacracy evolves from the culture that Agile creates. Agile is a catalyst towards moving organizations and people from more of an individual culture to a more relationship and team culture, which is all part of the evolutionary journey of holacracy.
Holacracy tries to define a new rule set, taking into account the human aspect of organizations. The success of agile is really down to being quite confined to the development and product team, whereas Holacracy wants to apply it to the entire organization. The bigger the organizations or enterprises, the more they have “change inertia,” resist Agile and want everything completely waterfall. Holacracy steps in the direction of solving the problem that many experience with attempting to scale agile to fit large organizations. Most seem to think that Agile is "situation specific," there are no universal best practices. Holacracy tries to flatten organizations hierarchically and enforces agile philosophy throughout the company by having the business leaders confirm a new set of rules, with the goals to improve organizational agility.
Agile requires a lot of discipline around practices. Holacracy requires a lot of discipline around governance and structure. A functional Agile organization as a (squat) pyramid, but it's a pyramid balanced on it's point. Some of the principles behind Holacracy align well with agile principles, probably because they were born in an agile software environment and that influenced its creation. Holacracy appears hard to grasp to start, but is actually "lighter" than "agile practices." Holacracy, while outlines the governance of work, doesn't tell you how to execute your actual work. It governs the roles, accountabilities and authority, but it’s up to the role holders to figure out the best way to execute. It speeds up decision making, allowing decisions to be made more effectively without too much rigid rules. Agile (done well) requires a lot of discipline around practices. Holacracy requires a lot of discipline around governance and structure. While you can certainly do a half baked agile, but it’s hard to do half baked Holacracy. Maybe this is in part because agile rollouts tend to start and stop with the software delivery team, are often ground up and without full organization buy-in.

Holacracy is good, but you can not expect every employee to be of a same level of maturity to adapt to it. You need to build the collaborative team, before you build the self-management initiative. There are three needs in an organizational setting which are embedded in Holacracy or other format of digital “style”: Self-determination, Self-organization and Interdependence. The purpose of holacracy is to breakdown silos, to improve organizational agility with the faster speed of responding the changes, and to increase employees engagement, with the ultimate goals to build people-centric organization.
Follow us at: @Pearl_Zhu
Published on July 08, 2015 23:52
No comments have been added yet.