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

Advice process vs accountability

When a software engineer role already have a particular accountability to develop software based on requirement. Does it mean she doesnt need to do advice process when delivering it?

 

A technical team leader role might raise tension on governance meeting to add accountability on software engineer role to get her technical design document reviewed by technical leader role. But does it mean its not okay to ask people to use advice process ? And instead only use governance tension?

 

The reason i am asking is because i feel advice process is such a basic tool in teal organization, and i fear of the impossibility of doing it on holacracy system.

3 Replies
Tom Mulder
12/12/2018

[@mention:456308404149183518] The question is what is the tension that require the role filler to ask for advice. If the role filler thinks it is wise (I often do that) to ask for advise from an expert role then no rule is holding them back. But the role filler is still free to make his own call and decision.

If you want to make it an obligation then there needs to be rule that restricts the authority of the role filler (you may take every action or decision to enact the purpose or accountabilities of your role unless there is a rule against it (e.g. domain or policy)). So then a proposal needs to be drafted for a Policy to create this restriction. A policy like: "If you create a technical requirement document then you need to ask for advice from role XYZ"

On your first question. What is defined in the requirements? You can also make an Accountability ….. on requirement and as defined in process X. In this process you can then add something on advice. But as it stated now there is no obligation for this. 

So Holacracy is not restricting anything but is just asking you to make it explicit. 

Hope this helps.

Paul Walker
12/13/2018

I absolutely second what [@mention:523162737680436711] said. If you find yourself questioning these things, it means expectations aren't clear enough.

If there is no rule requiring someone to use the advice process, then they don't have to. If you want them to have to use the advice process, then you need to make it an explicit requirement.

Juliane Martina Röll
12/14/2018
Fajar Firdaus posted:

 

A technical team leader role might raise tension on governance meeting to add accountability on software engineer role to get her technical design document reviewed by technical leader role.

Adding this Accountability to the software engineer Role would merely set an expectation that they will get their document reviewed (and it would not create an expectation for the technical leader role to actually do the reviewing...). It would not create a rule or an obligation that they do it.

If you want to create a formal obligation to have the document reviewed (or to use advice process when creating design documents), you could use a domain (possibly controlled by the technical leader role).