|

Rule of Law & Property Rights in Organizations

June 18, 2012 - 1:06pm

At first glance, the outputs of Holacracy’s governance process – role definitions – may look like little more than an improved job description. But once you understand what they truly mean, they become so much more – they form the keys to Holacracy’s distributed power system and the DNA of the organization’s design. Fortunately, there are a few simple rules you can use to remember their deeper meaning and unlock the staggering level of clarity encoded within.

Let’s dissect the meaning of role definitions in a Holacracy-powered company, and I invite you to look at HolacracyOne’s governance records as we go to see how this works in a real organization. You’ll note there are three basic components of a role definition:  Purpose, Scope, and Accountabilities. Purpose defines what potential this role exists to manifest; Accountabilities define what expectations others can hold of this role; and Scope defines the “property” of this role, which it can control and regulate as it sees fit, given its Purpose. Using these basic concepts, the simple rule to remember is this:

When you fill a role, you gain the authority to take any action you deem reasonably useful to express the role’s Purpose or energize one of its Accountabilities, as long as you don’t violate the Scope of another role.

Here’s a tangible example of how this plays out:  As of this writing, HolacracyOne’s Content & Outreach Circle holds a role affectionately named Social Media Butterfly, with a Purpose to “Pollinate the web with Holacracy”, and an accountability for “Creating or sourcing quick-to-consume content of interest to our market, and posting it to social media channels and open-contribution websites”

Social Media Butterfly Governance Records

Whomever fills that role can thus use their reasonable judgment to define what actions would best serve that Purpose or express that Accountability, and has the full authority to execute those actions – with no approvals required from anyone – unless they “exert control” within the Scope of another role.

So, for example, our Social Media Butterfly may freely decide to post comments on someone’s blog relevant to Holacracy, but they wouldn’t be able to, say, add our Facebook link onto the materials given out at our trainings. Those materials fall within the Scope of our Holacracy Education role, and thus the authority of Social Media Butterfly is constrained – they can only take that action if they first get the approval of Holacracy Education. And, on the flipside, others can take any actions they deem useful to express their own role’s Purpose and Accountabilities, but if they want to add something to our Facebook page, they would need approval of Social Media Butterfly, as that role holds a Scope of “HolacracyOne social media pages and accounts”.

In this way, you can think of a Scope as a “property right”, and that leads to another simple rule-of-thumb for practicing Holacracy:  You are free to do whatever you wish with your own property (your role’s Scope), but don’t exert control on your neighbor’s property without their permission. We can extend this one step further to include circles as well:  If a circle has been granted a Scope to control, and hasn’t further delegated that Scope to one of its roles, then it’s considered “communal property” of all roles within that circle – any one of them can exert control within that Scope. But, if you fill a role which is not in that circle, you’ll need permission first.

Putting this all together, the Holacracy Constitution brings two foundational elements of our broader human societies into our organizations: there’s rule of law through its defined governance process, and property rights through its distributed authority system. This enables an interconnected autonomy that should be familiar from our day-to-day societal life, yet there’s a key distinction here as well:  While a Scope grants your role a property right, it does not grant you a property right. Your responsibility, should you choose to accept a role in a Holacracy-powered organization, is one of steward – you are controlling the role not for your own sake, but for its sake. Your job is to control its property and use its authority for the sake of its Purpose – which, in turn, serves its circle’s Purpose, which ultimately serves the whole organization’s Purpose. Like a parent raising a child, your charge as role-filler becomes a sacred duty, a stewarding of another’s path in the world – an act of love and of service, not for your own sake, but nonetheless of your own free will.


If you liked this post, share it:

|

Comments

Submitted by Thomas Drakengren (not verified) on June 20, 2012 - 3:39pm. #

Interesting; so the role's scope only tells other roles what *not* to do, and not within what scope the role itself should act, is it so? Is that in order to keep the freedom to actually extend the scope if possible, or is there another reason?

Submitted by Brian Robertson on June 20, 2012 - 4:01pm. #

Hi Thomas,

That's correct (though for another reason), and this is a common misunderstanding in early practice of Holacracy.  Giving a Scope to a role does not set any expectations that the Role will necessarily do anything - it's a role's Purpose and Accountabilities which serve that function and create the "pull" for a role to act, not its Scope.  And giving a role a Scope doesn't limit the role to only acting within that Scope or anything like that - rather, it is granting authority to the role to control the Scope, if it so chooses, for the sake of its Purpose or Accountabilities.  It does that by limiting the authority of other roles, which now need permission to impact the Scope.  A role holding a Scope may also grant this permission by publishing policies which define when/how other roles may impact that Scope, and within what constraints.

Hope that clarifies!

- Brian

Submitted by Thomas Drakengren (not verified) on June 20, 2012 - 5:16pm. #

OK, got it, thanks! So the general process for checking Scope violations would be to check the Scopes of "sibling" circles or roles all the way up along the ancestor chain; in that way the process should be fairly scalable, right?

Submitted by Brian Robertson on June 20, 2012 - 7:02pm. #

Yep, that's right.

Add comment

The content of this field is kept private and will not be shown publicly.
Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.