Maybe trivial:
During triaging tensions in the Tactical a Project is requested for a role who is not represented by a partner in the meeting due to other commitments of the individual.
4.2.4 states:
If a Defined Role of the Circle is entirely or partially unrepresented at a Tactical Meeting due to someone’s absence, the Circle’s Lead Link may act within that Role to cover the gap.
So should the Project be assigned to the LL or to the absent partner who energizes the role that holds the corresponding accountability?
As the partner is not present in the meeting, he cannot actually "accept" the Project as stipulated under 4.2.3 e) that states:
"If any Next-Actions or Projects are accepted during this discussion, the Secretary ...."
So the actual question is: How is the "acceptance" of a NA or Project best received by an absent holder of a role?
Thank you for your insights.
Hansjürg
"assigning" Next Actions and Projects to absent role holders in the tactical meeting
12/08/2016
We assign the project to the specific Role, not to the LeadLink, as the Lead Link is acting in the Role of the absent person, and not as the Lead Link.
(Generally, Projects are assigned to Roles not "partners".)
Acceptance is implied, or given by the LeadLink.
If the proper Role holder, looking at the Tactical Outputs, has a tension with the project that was assigned to them, well, that's a tension.
Does this help?
12/08/2016
Hello Martina!
:-)
Thank you. You are going straight to the point: "Implied acceptance".
Navigating through a power shift phase, I observe many such implied acceptance situations that somehow support the continuation of the shadow power structure.
With the LL acting as "the boss" who commands.
Any thoughts on how do address this?
12/09/2016
4.1.2 Duty of Processing
You have a duty to promptly process messages and requests from your fellow Circle Members, as follows:
(a) Requests for Processing: Other Circle Members may ask you to process any Accountability or Project on a Role you fill in the Circle. If you have no Next-Actions tracked for it, you must identify and capture a Next-Action if there are any reasonable ones you could take. If there are not, you must instead share what you’re waiting on. That must be either a Next-Action or Project tracked by another Role, or a specific event or condition that must happen before you can take further Next-Actions.
1.2.5 Directing Attention & Resources
12/09/2016
Great comments - thank you all.
12/11/2016
Hi Hansjuerg,
Adding to the comments above: if you think that this specific constitutional rule of Lead Link accepting projects for absent circle members is reproducing shadow power structures, worst case you might also think of changing this "default" setting via a policy. But I guess that a joint reflection among circle members to reflect on dynamics experienced fostering/hindering a transition to Holacracy would be a smarter first move.
We did similar exercises with clients and made good experiences with tracking outputs in a public "Implementation Impediment Backlog" (with three columns: identified, work in progress, solved). Surfacing them raises a different level of collective awareness and helps to break often implicit/unconscious patterns.
- Gerald