Marcus Andrey Study
Ler em português Library

Framework · Facilitation techniques · 3 min read

Consent decision

"Is this good enough for now and safe enough to try? Any objections?" A way to decide on standards and process changes without endless consensus.

  1. 1Proposal

    The proposer presents one concrete proposal and its review date.

    "I propose we use this table pattern."
  2. 2Clarify

    Questions to understand the proposal only. No opinions yet.

    "Does it cover inline editing?"
  3. 3Reactions

    One short round: each person gives a quick reaction.

    "I like it, a bit worried about mobile."
  4. 4Objections

    Ask each person: is it safe enough to try? Objections need a reason.

    "Any objections?"
  5. 5Integrate

    Change the proposal to resolve each objection, then ask again.

    "Can you live with this version?"

Repeat steps 4–5 until there are no objections, then record the decision and review date.

Use it when

  • A design-system standard keeps getting discussed because one or two people want a perfect solution.
  • You introduce a new process, for example a critique format or a handoff checklist, and full agreement is not realistic.
  • A group has converged on one option after a Dot voting round and needs a clear decision before it leaves the room.

How to use it

  1. Present one concrete proposal. The proposer explains the proposal, the reason for it and a review date. Write it where everyone can see it. Output: one written proposal with a review date.
  2. Clarifying questions only. People ask questions to understand the proposal. No opinions or counter-proposals yet. Output: a proposal everyone understands. About 5 minutes.
  3. One round of quick reactions. Each person gives a short reaction in one or two sentences, without discussion. Output: a sense of the room. About 3 minutes.
  4. Ask for objections. Go round and ask each person: "Is this good enough for now and safe enough to try? Any objections?" Every objection must include a reason: what harm could it cause? Output: a list of reasoned objections, or none.
  5. Integrate the objection, then re-check. Work with the person who objects to change the proposal so the objection is resolved. Then ask for objections again. When there are none, record the decision and the review date. Output: a decision, the reasons and a review date. 10–20 minutes in total.

Worked example

In a design-system standard workshop, 6 designers and 2 frontend developers have chosen one data table filtering pattern with a dot vote. The UX lead runs a consent round.

Step What happens
Proposal "All products use the filter bar pattern from next quarter. We review it in 3 months."
Clarifying A developer asks if it supports saved filters. Answer: not in version 1.
Reactions Most like it. One designer would prefer a side panel, but says it is a preference.
Objection A designer objects: "Our users filter on 12 fields. A bar won't fit, so they lose work."
Integrate The group adds: "Products with more than 8 filters may use the side panel variant."
Re-check No objections. Decision recorded, with the review date.

The preference for a side panel did not block the decision. The reasoned objection improved it.

Watch out for

  • Preferences treated as objections. Ask: "What harm would this cause to our goal?" If there is none, it is a preference, and the decision can go ahead.
  • Silence taken as consent. Ask each person by name in the objection round, especially remote participants.
  • No review date. "Safe enough to try" only works if the group knows it will look again. Always set a date.
  • Using consent when one person must decide. If an Approver owns the decision, use DACI instead, and say so before the session starts.

Template

Read the questions out loud in this order.

CONSENT DECISION                                  10–20 min

Proposal (written, visible):
______________________________________________
Review date: __________

1. Clarifying questions?   (questions only, no opinions)
2. Quick reactions?        (one round, 1–2 sentences each)
3. "Is this good enough for now and safe enough to try?
    Any objections?"       (ask each person by name)
   Objection must say: what harm could this cause?
4. Integrate: how could we change the proposal so the objection
   is resolved?  → back to step 3

Decision recorded:                Review date:
Source
Sociocracy

Books to go deeper

  • Facilitator's Guide to Participatory Decision-MakingSam Kaner et al.Book · 1996 (3rd ed. 2014)
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close