[hackerspaces] a study of governance

Shirley Hicks shirley at velochicdesign.com
Thu Aug 18 20:37:17 CEST 2016


Thanks for the recommends. Have ordered the book.

Shirley Hicks
Red Mountain Makers
Birmingham, AL

> On Aug 18, 2016, at 1:05 PM, Ben Beyeler <ben at transitiongoshen.org> wrote:
> 
> I'd echo the regards for "Reinventing Organizations".   We've been part of trainings for Sociocracy (Dynamic Governance in the US). I appreciate how it provides structure for delegating work and empowering all.
> 
> https://www.youtube.com/watch?v=l3zFWpntExg <https://www.youtube.com/watch?v=l3zFWpntExg>
> 
> On Mon, Aug 15, 2016 at 7:06 PM, Edward L Platt <ed at elplatt.com <mailto:ed at elplatt.com>> wrote:
> The book "Reinventing Organizations" has some excellent case studies of organizations that fit into a third, self-managed category: http://www.reinventingorganizations.com/ <http://www.reinventingorganizations.com/> -Ed
> 
> On Mon, Aug 15, 2016 at 6:44 PM, Xer0Dynamite <dreamingforward at gmail.com <mailto:dreamingforward at gmail.com>> wrote:
> In the cornucopia of hackerspaces, two organizational structures seem
> to stand the test of time:  '''do-ocracy''' and '''bureaucracy'''.
> 
> They represent two competing ideals.  Do-ocracy is a vertical axis of
> individualism and bureaucracy is a horizontal axis of collective
> action.  Economically, the comparison would be like capitalism vs.
> socialism.
> 
> The success of do-ocracy is that you can just get things done -- if
> you ''already have the will for it''.
> The success of bureaucracy is that everyone is empowered -- when there
> are resources to do them.
> 
> The weakness of do-ocracies is that since there is no pre-planning,
> things you need ''aren't there''.  It gets there ''after'' a failure
> occurs and ''if'' the individual acts on it.
> The weakness of bureaucracy is that things happen s-l-o-w-l-y because
> it's difficult to reach consensus and people burn out.
> 
> Most hackerspaces are not quite at these extremes as do-ocracies
> implement weekly meetings, for example, for collective discussion, and
> bureaucracies generally allow individual action when it doesn't
> adversely affect anyone else or affect safety.
> 
> Most adhocracies seem to die out through lack of leadership,
> participation, and entropy.
> 
> Here endeth the lesson.
> 
> \0x
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org <mailto:Discuss at lists.hackerspaces.org>
> http://lists.hackerspaces.org/mailman/listinfo/discuss <http://lists.hackerspaces.org/mailman/listinfo/discuss>
> 
> 
> 
> -- 
> Edward L. Platt
> PhD student, University of Michigan School of Information
> https://elplatt.com <https://elplatt.com/>
> @elplatt <http://twitter.com/elplatt>
> KC1DYK
> 
> Tips for stopping email overload: https://hbr.org/2012/02/stop-email-overload-1 <https://hbr.org/2012/02/stop-email-overload-1>
> 
> This digital electronic mail message was sent from my general-purpose desktop personal computing machine.  Please forgive any overly-verbose, long-winded, rambling prose.
> 
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org <mailto:Discuss at lists.hackerspaces.org>
> http://lists.hackerspaces.org/mailman/listinfo/discuss <http://lists.hackerspaces.org/mailman/listinfo/discuss>
> 
> 
> 
> 
> -- 
> -Ben
> 574-535-9199
> 
> transitiongoshen.org <http://transitiongoshen.org/?ref=bab>
> Local initiatives for community resilience
> 
> goshenfunded.com <http://www.goshenfunded.com/>
> Creative Investment in the Common Good
> 
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/discuss/attachments/20160818/302cf143/attachment.html>


More information about the Discuss mailing list