1.6 KiB
2. Do-ocracy
In short
- If you want something done: Just do it!
- Have you done something? Great!, now tell others about it. Tell them what you did, and why you did it. The mailing-list is a great place to do so. Telling other people about your actions lets them know who to thank and will give you more support.
- If somebody complains: Either revert it, or work out a solution with the person who is complaining.
Vision behind it
A do-ocracy is an organizational structure in which individuals choose to pick up roles and execute tasks by themselves, rather than getting them appointed by others. Responsibilities are attached to people who do the work, rather than to the elected/selected officials. Doing a task is in itself justification for you being the person who does that job.
Source: http://www.communitywiki.org/en/DoOcracy
People need to feel safe knowing that they are allowed to try, and to fail. Thus, when people fail, we need to be kind and help them get better instead of berate them. The hackerspace gives everyone room to grow, and failure is part of that. For more information, read up on the idea of "blameless post-mortems" in the IT operations and DevOps communities.
Tight feedback loop: It's easy to do something, so it's very easy to try something, see what the result is, and then use that information to try something different.
Boundaries
Some things are too sensitive to be handled by do-ocracy alone, like throwing things away. The guidelines define what the boundaries are of the Do-ocracy. Any member can request that a decision is discussed in the group.