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

"Valid" accountabilities

Hello CoP,

I have two simple questions about accountabilities:

1) Can I add an accountability to a Role which is not related to its Purpose? I imagine it is possible, though not recommend. By possible I mean there are no "valid objections". 

2) Is it constitutionally allowed to have an accountability that needs to "access" the Domain of another role? Can I object that it may move the circle backwards if I say that it is going to take more time for the Role-filler to enact the acc?

Hope you can help me! Thanks

3 Replies
Brian Robertson
07/07/2016

Hey Davi,

1)  Yes, and it's not necessarily bad practice - it's a common and recommended thing to do in many cases.  Sometimes, because a role controls a domain or works in a general area, others need to count on it for something so that they can get their purpose met, and that's just fine.  On the other hand, it is often bad practice to stick extra accountabilities on a role that don't serve its purpose and that don't naturally fit that pattern.

2)  Yes, it's allowed, and often quite natural - just because another role controls the domain doesn't mean you can't just ask them for permission or propose some accountability on them to get your own accountability met.  Can you raise a valid objection to it on the grounds you've cited?  Maybe, or maybe not - depends on whether you can answer the objection test questions and validate the objection...

Hope that helps!

- Brian

Davi Gabriel da Silva
07/07/2016

Thanks, Brian! It's clear now

Bernard Marie Chiquet
07/07/2016
Brian Robertson posted:

1)  Yes, and it's not necessarily bad practice - it's a common and recommended thing to do in many cases.  Sometimes, because a role controls a domain or works in a general area, others need to count on it for something so that they can get their purpose met, and that's just fine.  On the other hand, it is often bad practice to stick extra accountabilities on a role that don't serve its purpose and that don't naturally fit that pattern.

 

- Brian

To add on Brian's comment, one use case I often see is when an ongoing activity is needed by/for the Org. and an accountability is then added to a role as it makes sense, even if the accountability is not related with the purpose of the role - we have the case within iGi, for instance, of adding an accountability to the Trainer Role for Marketing Role to get a short slot to present iGi's offers during a training - which is absolutely not needed for/by the purpose of the role, but this is one place that makes sense to hold this ongoing activity.