I posted about Sociocracy 3.0: Drivers before. Reading on and sharing thoughts as I go through more of the system:
After good driver statements that we all agree on, we then need to make proposals and refine them. The process of even coming up with proposals can be individual or collaborative, whatever works.
Concerns and Objections
Once we have proposals to consider, we should always check with anyone relevant who might have suggestions, concerns, or objections. So, doing a round with participants checking for any feelings of tension from anyone is a good practice. https://patterns.sociocracy30.org/co-create-proposals.html (and other links around that part of the guide).
They suggest a distinction between “objections” which really have to be addressed vs “concerns” which should be heard but don’t block progress if we can’t resolve them easily. https://patterns.sociocracy30.org/objection.html
Those ideas are pretty straightforward.
S3 is a Work-In-Progress
Incidentally, there’s been some notable revisions and improvements to the S3 Guide this year. It’s more readable and moving even more toward comfortable language like use of “team”. I’m as confident as ever that S3 (that’s the shorthand I’ll use from now on) is the best primary foundation for us, although all of it is adaptable however we find useful.
As I read more, I see that while it’s clear the ideas are pretty-well thought out, this is rough in some ways still. The new introductory section of the S3 Guide starts out great but then has a lot of not-so-well-structured sentences and statements that are hard to parse and sometimes erroneously duplicated. I may help contribute to improving the guide once I can process it better myself.
I’d love others to look into this more too and discuss our thoughts as we go.