Everyone who is affected by a decision should be directly or indirectly involved in the decision making. This could mean all members of a Team, a Delegate Circle, everyone holding the same role, a list of affected people or all amazee.io employees.
As Consent Decision Making is about making good enough for now, safe enough to try decisions, we live a culture where people feel comfortable to raise potential objections at any time. Everyone has the possibility to voice Objections against proposals, decisions, existing agreements, processes or activities.
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
A full explanation about Consent Decision Making concept can be found here. We suggest everybody to familiarise themself with this content before continuing here.
This document is to explain how Consent Decision Making exactly is used at amazee.io, and not why Consent Decision Making is a better way to take decisions.
</aside>
Giving Consent to something or consenting means the absence of Objections. It’s not to be confused with Consensus, which would mean that everyone has to agree.
Implicit Contract of Consent:
In the absence of objections to an agreement, I intend to follow through on the agreement to the best of my ability. I agree to share objections as I become aware of them.
An Objection is an argument relating to a (proposed) agreement or activity that reveals unintended consequences we’d rather avoid, or that demonstrates worthwhile ways to improve right now.
In turn having no Objection means:
Present the created Proposal to the group. In meetings this can be the Facilitator or someone who was involved in writing the Proposal. In our asynchronous, written world, active presentation is a good thing nevertheless it usually makes sense that you send a ready Proposal before meetings so that they can study it and prepare questions.