Quick systemic consensus


Seeking review

2016-06-25 - Tilmann (Reformatting and small rewrites)

Quick systemic consensus (Quick SysCon) is a powerful moderation tool for fast consent oriented decision making for groups during collaborative work and planning processes.

  • The process should be known by the group.
  • A moderator can help but is not necessary in a trained group.
  • An untrained group should definitely have a trained moderator.
  • The decisions are decisive (A quick syscon could be changed to a non decisive process by a process proposal. The  default is that it is decisive).

Also check out the glossary and the FAQ for further explanations.

Page contents

 

 

 

Process

Quick SysCon starts with a certain topic and normally with a direct proposal (or a question followed by a proposal). As soon as the proposal is properly identified and recognized as valid for the framework it is immediately checked for resistance "Is there any resistance to this proposal?". This is done by raising one hand.

  • If there is no resistance and the proposal fits in the framework the proposal is accepted as a decision. The decision should be noted in a protocol.
  • If there is resistance expressed by at least one person, the process is taken to the board.
    1. The first proposal is written down
    2. The question/topic is written down
    3. The two control options "passive solution"(aka zero solution) and"deepen process" (formerly known as further solution) are added
    4. Proposals that are brought forward are written down
      (Proposals can always be withdrawn by the proposal makers)

Voting

Everyone votes at the same time on one proposal after the other with the following options:

  • no resistance towards proposal: hands folded together
  • low resistance towards proposal:  one hand up
  • high resistance towards proposal: both hands up

The votes are counted by the moderator or protocol maker.

Framework

The framework defines which proposals are legal and which are illegal according to the framework (framework violation). Legal proposal can go into vote, while framework violations have to be withdrawn.

Literally legal

Proposal has to be legal by law.

Example

On the question what to do at a party someone in the group proposes to have the a woman in the group make a table dance. This proposal is illegal if the woman does not want to. She can not be forced to do it even if the group would vote in favor of the proposal. The proposal should not enter the voting in the first place. The only way to get the proposal into the voting would be to make sure beforehand the woman would want to make a table dance or she is under a legal contract with a job description that contains table dance as her work.

Reality

Proposal has to be feasible, according to the knowledge of participants.

Example

The proposal "Let us have a meeting at 9:00 am today" is not fitting into the framework if it is already 10:00 am. The proposal does not be taken on the chart for the proposals.

It can happen that a proposal turns out to violate the framework after it has been voted on as the preferred solution. If that can be foreseen it can be agreed one (via Quick SysCon) to take the next best solution.

If it was not anticipated it is a normal learning experience (mistakes happen) and the decision needs to be reevaluated.

Process proposal

A process proposal is initiated when a proposal needs to be resolved before the current Quick SysCon can continue. A process Quick SysCon is treated like every other proposal.

  • If no resistance is expressed the process proposal is immediately accepted
  • If there is one resistance the process is taken to the board. For that it needs to be clearly separated from the interrupted Quick SysCon.

When the process Quick SysCon is resolved the process continues with the interrupted Quick SysCon (de-escalation), if not made explicitly irrelevant by the process.

 

Process break

The process break is a powerful moderating tool. It can be requested by every participant during an escalation of a Quick SysCon.

The process break, if accepted, stops the escalation of a topic for a certain time frame. During this time no further process Quick SysCons can be started. Only after the stack of escalations is resolved in their current order new Quick SysCons can be started while the process break is active.

Implementation

The process break is requested by a participant with a certain time frame. The request of a process break can not be stopped by a process proposal!

Checked if there is any resistance.

  • If there is no resistance accepted and activated for the requested time.
  • If there is resistance the request is written down (topic is process break) and the passive solution (no process break) is added.

Further proposals of a process break with a different time frame can be added. Vote on break proposals.

Waiting period

After a failed request, the process break can be requested again after 5 minutes or later.

 

Moderation

Input of participants can normally be divided into three big groups. Be aware that the meaning of an input can vary regardless of the phrasing and wording from person to person. If it is not clear it is a task of the moderator to find out.

It is in all cases also the task of the moderator to moderate, meaning keeping input concise, understandable and proportional to the weight of the current question.

Wishes towards proposals

Wishes towards a proposal are not specific enough to make a proposal on their own but can be valuable input to form a proposal with low resistance/high acceptance.

Moderator task: Repeat wish and make clear it got heard. Ask if clear and understood.

Framework information

These information help setting the framework to check on proposals if they are valid.

Moderator task: Repeat and clarify framework information (eventually write down)

Explanations/Knowledge

Normally follow on a question of understanding or knowledge request.

Moderator Task: Check if explanation was understood.

Statement

A statement gives information about the state of the person bringing the input.

Moderator task: Repeat main point.

Questions

Questions normally are requests of knowledge or explanations(understanding).

Moderator task: Answer the question, especially if directed towards the current process, or redirect question towards the group.

Proposals

Proposals can either be a proposal for the currently running Quick SysCon or are recognized as process proposal. Keywords: first, before 

Moderator task: Check on framework. If legal, take up proposal on board. If process proposal, interrupt current Quick SysCon and make process Quick SysCon.



To the extent possible under law, the yunity wiki contributors have waived all copyright and related or neighboring rights to the content of the yunity wiki. More information...


You have an account but can't edit or create pages? Write us in the open chatroom or in our yunity Slack!