Holacracy Community of Practice Archive, 2015-2019 Community Holacracy Web Site

Hi,

like this profound conversation about nuances of holarchic principles - thanks for all your perspectives and summaries, very helpful!

Here's my additional thoughts:

Where a domain HAS been delegated to a circle/role, from super-circles all the way from the anchor circle, the domain (and any accompanying policies) applies to ALL roles in all circles of the organization.

To my understanding domains and policies are holarchic (and affect all the circles down). Referring to Andrea's point about "the default domain not being considered a full fledged domain" and Nick's example of the Auto-accept time limit I would still interpret a GCC policy relevant for all sub-circles, even without an explicit domain, since it applies to "all activities and functions within the circle". 

I still have a few practical questions: how can a spread of domain show up in Governance? The domain of circle B is visible at the "super-circle boundary" (ie the LL role representing the circle B in the super-circle A). Since the domain must stay visible at the circle boundary you can only grant authority to impact that domain for subcircles via a policy. And: a policy in Circle B that allows impacting a domain of Circle B for Circle D is delegated further downwards to a Sub-Circle of D via processing a change of the policy in Circle B e.g. via Rep Links. I wonder how transparent and easy to capture that is for circle members of D, since the policy is not part of the subcircle's governance but a few circles up. And how do circle members hold themselves well-informed about changes without screening Glassfrog records every morning. For larger org that can become really tricky.

Any thoughts / experiences on that?

- Gerald