The Do-ocracy Guide
How to actually get things done at HeatSync Labs. If you want something done: Just do it!
The Golden Rule
If you want something done: Just do it!
Doing a task is in itself justification for you being the person who does that job. Authority is earned through action, not election.
What is Do-ocracy?
In a do-ocracy, individuals choose to take on tasks and roles independently. The authority to make decisions and take action lies with those who do the work.
This is different from democracy (where everyone votes) and different from meritocracy (where the “best” person does it). In a do-ocracy, whoever shows up and does the work has the authority to make decisions about that work.
Core Principles
- Initiative: Don’t wait for permission or assignment
- Action: Doing beats planning
- Communication: Tell others what you’re doing
- Openness: Be receptive to feedback and help
- Responsibility: Own your actions and their outcomes
How It Works in Practice
See a Need
Notice something that needs doing: broken equipment, messy area, missing documentation, cool project idea.
Communicate Intent
For significant actions, post your plan on the wiki, Slack, or physical board. This allows for feedback.
Seek Input
Actively ask for feedback, especially from those who might be affected. Address constructive objections.
Take Action
If no unresolvable objections arise within 9-14 days (or immediately for small tasks), proceed responsibly.
Document Results
Record what you did, how much it cost, and any relevant details for future reference.
When to Just Act vs When to Discuss
Just Do It
- Cleaning and organizing
- Fixing broken things
- Routine maintenance
- Documentation improvements
- Small improvements (under $50)
- Reversible changes
- Safety fixes
Seek Feedback First
- Changes affecting others’ work
- Spending $50-$200
- Moving/reorganizing shared spaces
- New policies or procedures
- Tool modifications
- Events using significant space
Needs Formal Approval
- Spending over $200
- Permanent infrastructure changes
- Legal commitments
- Bylaw changes
- Safety policy changes
- Membership decisions
Practical Examples
Example: Organizing a Workshop
Sarah wants to run a soldering workshop:
- She posts on Slack: “Planning a soldering workshop for next Saturday 2-5pm”
- Gets feedback about material costs and space availability
- Orders supplies using the workshop budget
- Runs the workshop
- Documents attendance and expenses on the wiki
Sarah didn’t need permission - she took initiative, communicated, and made it happen.
Example: Tool Area Reorganization
Mike notices the electronics bench is chaotic:
- Takes photos of current state
- Posts proposal with mockup on wiki: “Reorganizing electronics bench for better workflow”
- Waits 10 days for feedback, incorporates suggestions
- Spends a Saturday reorganizing with help from volunteers
- Updates tool documentation with new layout
Mike communicated first because this affected others’ workspaces, but still led the change himself.
Do-ocracy Budget Guidelines
| Amount | Process | Documentation |
|---|---|---|
| Under $50 | Just do it | Save receipt, note in expense log |
| $50 - $200 | Post intent, wait 72 hours for feedback | Receipt + brief wiki entry |
| Over $200 | Formal proposal at meeting | Full proposal + receipts + report |
Reimbursement: Submit receipts with documentation to the treasurer. Approved do-ocracy expenses are reimbursed within 30 days.
Boundaries and Limitations
Do-ocracy Does NOT Apply To:
- Safety violations: Never compromise safety for expediency
- Others’ property: Don’t modify someone else’s project without permission
- Irreversible changes: Major alterations need group consensus
- Legal matters: Contracts, liability issues need board approval
- Access control: Membership and access decisions follow formal process
Conflict Resolution
When do-ocracy actions conflict:
- Direct dialogue: Talk to each other first
- Seek mediation: Ask a neutral member to help
- Community input: Bring to next meeting if needed
- Board intervention: Only for unresolvable disputes
Tips for Successful Do-ocracy
Start Small
Build trust by successfully completing small projects before taking on major initiatives.
Document Everything
Future members benefit from knowing what was done and why. Over-documentation beats under-documentation.
Ask for Help
Do-ocracy doesn’t mean working alone. Recruit others who share your vision.
Accept Feedback Gracefully
Not all ideas work out. Be ready to adjust or even abandon plans based on community input.
Celebrate Successes
Share what you accomplished! It inspires others and builds community momentum.
Learn from Failures
Things will go wrong. Document what didn’t work so others can learn.
Remember
Perfect is the enemy of done. It’s better to do something imperfectly than to do nothing perfectly. The community will help iterate and improve over time.
Resources
- Wiki: Document your projects and read about others
- Slack #do-ocracy: Coordinate with other doers
- Physical board: Post plans and gather feedback
- Treasurer: Submit reimbursement requests
- Meeting notes: Review past do-ocracy discussions