Difference between revisions of "Do-ocracy"

From Noisebridge
Jump to: navigation, search
(Don't be afraid to step on people's toes: fixed grammar)
 
(38 intermediate revisions by 30 users not shown)
Line 1: Line 1:
Typically when someone wants to do or change something big at Noisebridge, they bring it up at a meeting and it goes through our [[Consensus Process]]. Most of the time many of us just don't want to be troubled with spending a week figuring out if everyone is ok with a small or mundane thing, and so there's Do-ocracy. Do-ocracy tends to work just as long as our only rule is followed, to be excellent to each other.
+
[[File:Do-ocracy Poster - DO IT - 2018-08-11 revision (small).png|thumb|right]]
 +
[[File:Do-ocracy Poster - DO-ERs DECIDE - 2018-08-11 revision (small).png|thumb|right]]
  
'''Do-ocracy: If you want something done, do it, but remember to be excellent to each other when doing so.'''
+
Do-ocracy is a decentralized, anarchist way of deciding and managing how things get changed, and is the main way that things get done at Noisebridge. It can be summed up as follows:
  
An important part of being excellent is documenting your change. Write a note on Noisebridge's [[ChangeLog]], or leave a note on what you do-ocratically did. Contact numbers are especially important if you want people to contact you about the change. The biggest challenge in a do-acracy is not reversal, but ascertaining (and taking) responsibility.
+
<blockquote>Do-ocracy: If you want something done, do it, but remember to be excellent to each other when doing so.</blockquote>
 +
 
 +
This applies to almost everything at Noisebridge, with only a few exceptions (often described as very big deep changes to Noisebridge as an organization). If you think it'd be cool to build something out of some parts in the Parts Repository, the tables should be re-arranged, or a new workshop should be built, '''you should do it'''! But remember to be excellent.
 +
 
 +
== How to do Do-ocracy ==
 +
 
 +
There are no formal rules to Do-ocracy, but here are some tips for smooth functioning Do-ocracy. Don't feel obliged to do any of them.
 +
 
 +
 
 +
=== Be accountable ===
 +
 
 +
If you make a change that isn't terribly easy to undo, such as moving a projector, or which has impacts that can't be undone, such as putting a video on the projector that's potentially triggering of epilepsy, it's good to be accountable to those impacted by the change. Make sure that people know who made the change, so that they can clarify what's going on and how they're impacted. Write notes, post in Slack or on the mailing list, make announcements in person. Let people know you're responsible for your change.
 +
 
 +
=== Don't be afraid to step on people's toes ===
 +
 
 +
Sometimes you'll make a change Do-ocratically and someone will be unhappy with it. That's ok. Stepping on toes is fine. But what's usually not fine is not being willing to talk to the person about the change, so it's best to be willing to resolve the problems that it may have caused.
 +
 
 +
=== Use little-c consensus ===
 +
 
 +
If you're concerned that a change may be a little too impactful to just do, and you want to make sure it's ok to do, speak to the people who are likely to be impacted. Be willing to find outcomes that everyone can live with.
 +
 
 +
=== Don't use an either/or approach ===
 +
 
 +
If the particular thing you want to do isn't ok, either before or after the fact, explore other options. Try to achieve everyone's end goals, while being flexible with how you get there. It's often not the case that your only options are ''Do What You Want To Do'' vs. ''Do What They Want To Do''. Usually you can find some other, third path to things which everyone can live with.
 +
 
 +
=== Be compassionate ===
 +
 
 +
Because it really sucks to have one's project trashed, or a workshop turned inside out by a project, or the like, you may find that you've Do-ocratically done something that makes someone irritated. While it's not Excellent for them to be aggressive or hostile, you should expect that they may be upset. Be patient and compassionate.
 +
 
 +
=== Don't be a dick ===
 +
 
 +
Even tho it really sucks to have one's project trashed, or a workshop turned inside out by a project, or the like, don't be a dick to the person who did it. Aggression and hostility are widely considered Unexcellent and you may find yourself asked to leave if you can't keep that under control. Instead of immediately talking to person who made the change, take some time to think about the situation. Drink some herbal tea, smoke some weed, go for a jog. Give your limbic system time to relax.
 +
 
 +
=== Do-er's Decide, Non-Do-er's Stand Aside ===
 +
 
 +
If you're not willing or able to put in the time or effort to hack, don't stand in the way of the people who are are. If you have opinions, be willing to hack. Offering advice is fine, but it's usually good to ask if it's wanted, and if not, don't give it.
 +
 
 +
== Fictionalized Examples ==
  
==Use Cases==
 
 
====The Short Version====
 
====The Short Version====
 
# Dick asks around if anyone would feel negative about the bike shed being pink. No one does.
 
# Dick asks around if anyone would feel negative about the bike shed being pink. No one does.
Line 16: Line 53:
 
# Jane and Dick decide to repaint the bike shed blue.
 
# Jane and Dick decide to repaint the bike shed blue.
  
====The What Normally Happens Version====
 
# Dick paints the bike shed pink.
 
# Noisebridge is now so large someone is bound to have an opinion about something (typically this ends up being someone who is either more or less living out of the space or who is almost never at the space), so Jane gets fucking pissed off at Dick and threatens his life. She's not a fan of pink and since she doesn't have a job and has been spending most of her time at Noisebridge, it's like a second home to her and she wants it run her way.
 
# They yell at each other for a while over the discussion mailing list, annoying hundreds of people.
 
# Dick makes Noisebridge a very unwelcoming place for the next week since all he wants to talk about at the space is how much of a bitch Jane is and how you should state so on the mailing list so as to tarnish her name.
 
# Jane gives #bantown Dick's home address and phone number.
 
# Dick ends up stating several times throughout the next month that he's leaving or has left Noisebridge, or any combination of the two.
 
# Jane, in retaliation to Dick constantly reverting changes she's made to the wiki, shits on top of the electronics bench. A statement to those (everyone) that haven't stopped talking to Dick. This is called an Austin Solder Puddle.
 
# Dick has dinner with Jane and after a bit of small talk ends up back at her place. The next morning he wakes up in Jane's bed, feeling a large pang of regret hit him. No shower will make him feel clean.
 
# At this point one of two things happen.
 
## Dick and Jane's friends overlap, they inadvertently end up at a bar drunk and make up. Crying in each other's arms about how much of a waste Noisebridge is.
 
## The drama continues until someone just gives up and moves on. At this point pretty much everyone's forgotten why this epic battle got started in the first place.
 
  
==Notes==
+
{{ManualPage}}
* Do-ocracy works most of the time. When it doesn't it sort of sucks.
 
* Write a note (with your name or nym) saying what you did.
 
* If someone nicely asks you to change something back, be nice back and just change it back.
 
* If someone's being a dick to you about something you've changed, be nice and just change it back. If you must cry about it only do so after you've restored things.
 

Latest revision as of 18:02, 23 September 2018

Do-ocracy Poster - DO IT - 2018-08-11 revision (small).png
Do-ocracy Poster - DO-ERs DECIDE - 2018-08-11 revision (small).png

Do-ocracy is a decentralized, anarchist way of deciding and managing how things get changed, and is the main way that things get done at Noisebridge. It can be summed up as follows:

Do-ocracy: If you want something done, do it, but remember to be excellent to each other when doing so.

This applies to almost everything at Noisebridge, with only a few exceptions (often described as very big deep changes to Noisebridge as an organization). If you think it'd be cool to build something out of some parts in the Parts Repository, the tables should be re-arranged, or a new workshop should be built, you should do it! But remember to be excellent.

How to do Do-ocracy[edit]

There are no formal rules to Do-ocracy, but here are some tips for smooth functioning Do-ocracy. Don't feel obliged to do any of them.


Be accountable[edit]

If you make a change that isn't terribly easy to undo, such as moving a projector, or which has impacts that can't be undone, such as putting a video on the projector that's potentially triggering of epilepsy, it's good to be accountable to those impacted by the change. Make sure that people know who made the change, so that they can clarify what's going on and how they're impacted. Write notes, post in Slack or on the mailing list, make announcements in person. Let people know you're responsible for your change.

Don't be afraid to step on people's toes[edit]

Sometimes you'll make a change Do-ocratically and someone will be unhappy with it. That's ok. Stepping on toes is fine. But what's usually not fine is not being willing to talk to the person about the change, so it's best to be willing to resolve the problems that it may have caused.

Use little-c consensus[edit]

If you're concerned that a change may be a little too impactful to just do, and you want to make sure it's ok to do, speak to the people who are likely to be impacted. Be willing to find outcomes that everyone can live with.

Don't use an either/or approach[edit]

If the particular thing you want to do isn't ok, either before or after the fact, explore other options. Try to achieve everyone's end goals, while being flexible with how you get there. It's often not the case that your only options are Do What You Want To Do vs. Do What They Want To Do. Usually you can find some other, third path to things which everyone can live with.

Be compassionate[edit]

Because it really sucks to have one's project trashed, or a workshop turned inside out by a project, or the like, you may find that you've Do-ocratically done something that makes someone irritated. While it's not Excellent for them to be aggressive or hostile, you should expect that they may be upset. Be patient and compassionate.

Don't be a dick[edit]

Even tho it really sucks to have one's project trashed, or a workshop turned inside out by a project, or the like, don't be a dick to the person who did it. Aggression and hostility are widely considered Unexcellent and you may find yourself asked to leave if you can't keep that under control. Instead of immediately talking to person who made the change, take some time to think about the situation. Drink some herbal tea, smoke some weed, go for a jog. Give your limbic system time to relax.

Do-er's Decide, Non-Do-er's Stand Aside[edit]

If you're not willing or able to put in the time or effort to hack, don't stand in the way of the people who are are. If you have opinions, be willing to hack. Offering advice is fine, but it's usually good to ask if it's wanted, and if not, don't give it.

Fictionalized Examples[edit]

The Short Version[edit]

  1. Dick asks around if anyone would feel negative about the bike shed being pink. No one does.
  2. Dick paints the bike shed pink.

The Being Excellent To Each Other Version[edit]

  1. Dick paints the bike shed pink.
  2. Jane becomes unhappy about the fact that the bike shed she helped build is now pink.
  3. Jane politely engages Dick in discussion about why he thought this was ok. Dick realized that other people he shares the space with have feelings too.
  4. Jane and Dick decide to repaint the bike shed blue.


Noisebridge Manual - The Prologue - Visitors and Guests - Getting along - Staying in touch - Day to Day operations - Infrastructure - Inner Mechanizations - Things we do - Lore - Ask to leave |Edit |Edit Sections