Do-ocracy
How things get done at Pawprint Prototyping.
Do-ocracy
Do-ocracy is a decentralized way of deciding and managing how things get changed, and is the main way that things get done at Pawprint Prototyping.
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.
Do-ocracy applies to almost everything at Pawprint. If you think it'd be cool to build something out of spare parts, rearrange the furniture, set up a new workstation, or start a workshop series: you should do it, but remember to be excellent.
As a general rule of thumb, if you want to do something that takes less than an hour to undo, you should do it.
The only exceptions are things that require big-C Consensus: a formal motion and vote at a general body meeting (typically described as big, expensive, or difficult-to-reverse changes to the organization itself).
How to Do Do-ocracy
There aren't many formal rules to do-ocracy, but here are some tips for smooth functioning.
Be Accountable
If you make a change that isn't easy to undo:
- moving equipment
- reorganizing a shared area
- modifying infrastructure
Make sure people know who did it and why. Post in the Telegram group, document it in the wiki, leave a note, or mention it at the next meeting. Let people know you're responsible for your change so they can ask questions or raise concerns.
Don't Be Afraid to Act
Sometimes you have to crack eggs to make an omelet. Most of the time it's easier to ask for forgiveness than permission. If something clearly needs doing and you have the ability to do it, don't let uncertainty stop you.
Use Little-c Consensus
If you're concerned that a change might be too impactful to just do unilaterally, talk to the people who are likely to be affected. Be willing to find outcomes that everyone can live with. If someone disagrees with something you've done, start a conversation. Stonewalling without engaging isn't excellent.
Look for the Third Option
If the people around you don't support what you want to do, don't frame it as "my way vs. your way." Explore other options. Try to achieve everyone's end goals while being flexible about how you get there. Usually there's a third path that everyone can live with.
Be Compassionate
It really sucks to have your project moved, your active workspace reorganized, or your setup disrupted by someone else's do-ocratic action. If you've done something that makes someone upset, be patient and compassionate — even if you think your change was reasonable.
Don't Be a Dick About It Either
On the flip side: even if it's extremely inconvenient to come back and find things aren't where you left them, don't be hostile to the person who moved them. Think first before you react.
Do-ers Decide, Non-Do-ers Stand Aside
If you're not willing or able to put in the time and effort to do the work, don't stand in the way of the people who are. If you have opinions, be willing to contribute. Offering advice is fine, but ask if it's wanted first — and if it's not, let it go.
Boundaries
Do-ocracy doesn't mean you can do literally anything without regard for others:
- Don't spend the organization's money without membership approval. If a project needs funding, bring it up at a general body meeting or send your formal proposal to secretary@.
- Don't throw away other people's stuff. If something looks like junk but might belong to someone, ask in the Telegram group first. Items with green parking tickets are spoken for until they expire. Items with unknown ownership may get a red parking ticket and either be absorbed into general space use, sold at the Electronics Flea Market, or discarded.
- Don't make irreversible changes to shared infrastructure (electrical, plumbing, network, walls) without discussing it first. Reversible improvements are generally fair game.
- Don't override someone else's active project. If someone is clearly in the middle of something, coordinate rather than steamroll.
When Do-ocracy Isn't Enough
Some decisions are too big, too expensive, or too contentious for one person to just do. That's what the formal governance process is for: motions proposed and voted on at general body meetings. If you're unsure whether something crosses that line, ask in the Telegram group.
Example
- Fizz asks around if anyone would feel negative about the bike shed being painted pink. No one objects.
- Fizz paints the bike shed pink.
Or, the more realistic version:
- Fizz paints the bike shed pink.
- Buzz is unhappy — she helped build that bike shed and wasn't consulted.
- Buzz politely talks to Fizz about it. Fizz realizes that other people sharing the space have feelings too.
- They agree to repaint it blue.
Credit
Do-ocracy as a hackerspace governance principle was popularized by Noisebridge in San Francisco and has since been adopted by hackerspaces worldwide. Much of this article was adapted from the Noisebridge article on Do-ocracy. The concept is also well-documented in the Hackerspace Blueprint and CommunityWiki. We've adapted it to fit Pawprint's culture and structure.