Do-ocracy - Revision history

JasonCarswell at 11:07, 27 September 2024

2024-09-27T11:07:42Z

JasonCarswell at 10:53, 27 September 2024

2024-09-27T10:53:05Z

JasonCarswell at 21:30, 2 August 2024

2024-08-02T21:30:32Z

JasonCarswell at 00:04, 18 August 2023

2023-08-18T00:04:53Z

JasonCarswell at 18:15, 27 July 2023

2023-07-27T18:15:09Z

JasonCarswell at 15:09, 27 July 2023

2023-07-27T15:09:43Z

JasonCarswell at 10:24, 27 July 2023

2023-07-27T10:24:04Z

JasonCarswell at 10:22, 27 July 2023

2023-07-27T10:22:40Z

JasonCarswell at 10:17, 27 July 2023

2023-07-27T10:17:38Z

JasonCarswell at 10:13, 27 July 2023

2023-07-27T10:13:39Z

← Older revision		Revision as of 11:07, 27 September 2024
Line 97:		Line 97:

	== See also ==		== See also ==
		+
		+	* [[Community organizing]]
		+	* [[Terminology]]
		+	* [[Windsor ACTION Group]]
		+
		+	=== On Community Wiki ===

	* '''[https://communitywiki.org/wiki?action=rc;rcfilteronly=tag:volunteer volunteer]'''		* '''[https://communitywiki.org/wiki?action=rc;rcfilteronly=tag:volunteer volunteer]'''

@@ Line 3: / Line 3: @@
 [[File:CommunityWiki logo 150x122.png|thumb|right|150px|[https://CommunityWiki.org CommunityWiki] logo.]]
 [[File:You aren't doing it wrong, if no one knows what you are doing.jpg|thumb|right|150px|"''You aren't doing it wrong, if no one knows what you are doing.''"]]
 == Do-ocracy ==

← Older revision		Revision as of 21:30, 2 August 2024
Line 2:		Line 2:

	[[File:CommunityWiki logo 150x122.png\|thumb\|right\|150px\|[https://CommunityWiki.org CommunityWiki] logo.]]		[[File:CommunityWiki logo 150x122.png\|thumb\|right\|150px\|[https://CommunityWiki.org CommunityWiki] logo.]]
		+	[[File:You aren't doing it wrong, if no one knows what you are doing.jpg\|thumb\|right\|150px\|"''You aren't doing it wrong, if no one knows what you are doing.''"]]

	== Do-ocracy ==		== Do-ocracy ==

@@ Line 1: / Line 1: @@
 : ''This [https://CommunityWiki.org/wiki/DoOcracy article] originated on [https://CommunityWiki.org CommunityWiki.org] and was copied here to be forked, expanded upon, and evolve.''
-[[File:CommunityWiki logo 150x122.png|thumb|right|150px|CommunityWiki logo.]]
+[[File:CommunityWiki logo 150x122.png|thumb|right|150px|[https://CommunityWiki.org CommunityWiki] logo.]]
 == Do-ocracy ==

@@ Line 1: / Line 1: @@
-: ''This [https://CommunityWiki.org/wiki/DoOcracy article] originated on [https://CommunityWiki.org CommunityWiki.org] and was copied here to potentially fork and evolve.''
+: ''This [https://CommunityWiki.org/wiki/DoOcracy article] originated on [https://CommunityWiki.org CommunityWiki.org] and was copied here to be forked, expanded upon, and evolve.''
 [[File:CommunityWiki logo 150x122.png|thumb|right|150px|CommunityWiki logo.]]
-== DoOcracy ==
+== Do-ocracy ==
 A '''do-ocracy''' (also sometimes '''do-opoly''', which is a more obvious pun on “'''[http://www.m-w.com/dictionary/duopoly duopoly]'''”) is an organizational structure in which individuals choose roles and tasks for themselves and execute them. Responsibilities attach to people who '''do''' the work, rather than elected or selected officials.
@@ Line 27: / Line 27: @@
 ''From [[User:JasonCarswell|an experienced Burner]]:''
-If unsatisfied with someone's project you are just as free to do your own version as you are to criticize it, shut up, or help make theirs better.
+If unsatisfied with someone's project, you are just as free to do your own version as you are to criticize it, shut up, or help make their project better.
 Just because you do something doesn't mean the community owes you anything for taking the initiative.
-If it's important and/or the do-er is competently considerate, a do-er will consult, include, and invite the community to participate as much as practically possible (while being aware of [https://en.wikipedia.org/wiki/Too_Many_Cooks_(short) too many cooks]) - because it's better for the community (folks may want to help but not everyone can take initiative), more hands make less work, and there's less room for complaints if folks had ample opportunities.  Ultimately, balance is ideal, as in most things.
+If it's important and/or the do-er is competently considerate, a do-er will consult, include, and invite the community to participate as much as practically possible (while being aware of [https://en.wikipedia.org/wiki/Too_Many_Cooks_(short) too many cooks]) - because it's better for the community - working on projects increases familiarity, capable folks will rise to the occasion, many folks may want to help but not everyone can take initiative, more hands make less work (freeing up the capable for other projects), and there's less room for complaints if folks had ample opportunities to improve things.  Ultimately, balance is ideal, as in most things.
 == Necessary conditions ==

@@ Line 25: / Line 25: @@
 === More concepts ===
-[''Paragraph of from [[User:JasonCarswell|an experienced Burner]]:'']  If you are not satisfied with someone's project you are just as free to do your own version as you are to criticize it, shut up, or help make it better.  Also, just because you do something doesn't mean the community owes you anything for taking the initiative.  Lastly, if it's important and/or the do-er is competently considerate, a do-er will consult, include, and invite the community to participate as much as practically possible (while being aware of [https://en.wikipedia.org/wiki/Too_Many_Cooks_(short) too many cooks]) - because it's better for the community (folks may want to help but not everyone can take initiative), more hands make less work, and there's less room for complaints if folks had ample opportunities.  Ultimately, balance is ideal, as in most things.
+''From [[User:JasonCarswell|an experienced Burner]]:''
 == Necessary conditions ==
@@ Line 64: / Line 70: @@
 *: Essential tasks for the organization that no-one is interested in doing, will be hard to bootstrap and accomplish.
 * '''Log Jam'''.
-*: [''New addition.''] Drastic diminishment or death of a community and/or the group momentum may result when controlling management (a single leader or core clique) are afflicted by burnout, sickness, tragedy, or other issues.  Consciously or not - isolation occurs when leadership neglects to openly invite and include participation, and inform of management developments and processes to ensure others may take over if necessary.
+*: [''New addition.''] Drastic diminishment or death of a community and/or the group momentum may result when controlling management (a single leader or core clique) are afflicted by burnout, sickness, tragedy, or other issues.  Consciously or not - isolation will occur when leadership neglects to openly invite and include participation, and inform everyone of management developments and processes to ensure others may take over if necessary.
 * '''Possessiveness'''.
-*: [''New addition.''] A person who’s do-ocrat’d themselves into control of a very necessary system (event organizing team, group email list, etc.) can get heady with power and gate-keep information, entrench core management cliques, claim they know what's best rather than consult and include the community, and ignore or cut out many who wish to help or have input in how things are run or communicated.
+*: [''New addition.''] A person who’s do-ocrat’d themselves into control of a very necessary system (event organizing team, group email list, web site administration, etc.) can get heady with power and gate-keep information, entrench core management cliques, claim they know what's best rather than consult and include the community, and ignore or cut out many who wish to help or have input in how things are run or communicated.
 * '''Resentment'''.
 *: If only a minority of participants in the community do-ocratize themselves into the hard jobs, they can resent others who don’t take on responsibility.

@@ Line 23: / Line 23: @@
 Things come to a head when one of IT’s star 36-month projects is cancelled because “the app those guys in Marketing did for us is good enough.” IT issues an edict on company email that “pirate” software “will not be supported” by IT helpdesk staff and is an improper use of company property (the network). In an executive meeting, the management decides to split off “the guys in marketing” as a new “Experimental Apps Taskforce”, relegating IT to network maintenance and desktop support.
-=== More ideas ===
+=== More concepts ===
 [''Paragraph of from [[User:JasonCarswell|an experienced Burner]]:'']  If you are not satisfied with someone's project you are just as free to do your own version as you are to criticize it, shut up, or help make it better.  Also, just because you do something doesn't mean the community owes you anything for taking the initiative.  Lastly, if it's important and/or the do-er is competently considerate, a do-er will consult, include, and invite the community to participate as much as practically possible (while being aware of [https://en.wikipedia.org/wiki/Too_Many_Cooks_(short) too many cooks]) - because it's better for the community (folks may want to help but not everyone can take initiative), more hands make less work, and there's less room for complaints if folks had ample chance.  Ultimately, balance is ideal, as in most things.

@@ Line 31: / Line 31: @@
 Do-ocracy typically evolves spontaneously in groups where:
-* '''Authority is non-coercive.'''
+* '''Authority is non-coercive'''.
-* '''Culture of participation.''' Each member of the community feels a right and a duty to take on responsibilities.
+* '''Culture of participation'''.
-* '''Effort is rewarded with recognition.'''
+*: Each member of the community feels a right and a duty to take on responsibilities.
-* '''Stakes are low.''' Typically, if job X or task Y didn’t get done, or got done poorly, it’s not a life-or-death situation.
+* '''Effort is rewarded with recognition'''.
-* '''Work is plentiful.''' There are lots of jobs to do, and lots of people to do them.
+* '''Stakes are low'''.
 == Contrast ==
@@ Line 48: / Line 51: @@
 == Dangers ==
-* '''Burnout'''. People can get too attached to the do-ocratic system and volunteer for too many jobs, or too much work, and tend to have a low '''[http://wiki.c2.com/?TruckFactor TruckFactor]''' [If someone was hit by a truck could their work be continued?].
+* '''Burnout'''.
-* '''Complacency'''. If a minority of people take on jobs, the others can become complacent and ignore new tasks, since “someone else will do it.”
+*: People can get too attached to the do-ocratic system and volunteer for too many jobs, or too much work, and tend to have a low '''[http://wiki.c2.com/?TruckFactor TruckFactor]''' [If someone was hit by a truck could their work be continued?].
-* '''Despotism'''. A person who’s do-ocrat’d themselves into control of a very necessary system (network, food pool, etc.) can get heady with power and demand rewards or tribute for their work.
+* '''Complacency'''.
-* '''Fair Process'''. Do-ocracy is not always explicitly defined, so there are diverging perception dangers about “fairness”.
+*: If a minority of people take on jobs, the others can become complacent and ignore new tasks, since “someone else will do it.”
-* '''Frustration'''. Some people don’t have the time or means to do something, but they do have (real or imagined) expertise. In a do-ocracy, they will feel overrun and perceive the situation as slipping out of their hands. This can cause frustration. And remember: “''Fear is the path to the dark side…''”
+* '''Despotism'''.
-* '''Incompleteness'''. Essential tasks for the organization that no-one is interested in doing, will be hard to bootstrap and accomplish.
+*: A person who’s do-ocrat’d themselves into control of a very necessary system (network, food pool, etc.) can get heady with power and demand rewards or tribute for their work.
-* '''Log Jam'''. [''New addition.''] Drastic diminishment or death of a community and/or the group momentum may result when controlling management (a single leader or core clique) are afflicted by burnout, sickness, tragedy, or other issues.  Consciously or not - isolation occurs when leadership neglects to openly invite and include participation, and inform of management developments and processes to ensure others may take over if necessary.
+* '''Fair Process'''.
-* '''Possessiveness'''. [''New addition.''] A person who’s do-ocrat’d themselves into control of a very necessary system (event organizing team, group email list, etc.) can get heady with power and gate-keep information, entrench core management cliques, claim they know what's best rather than consult and include the community, and ignore or cut out many who wish to help or have input in how things are run or communicated.
+*: Do-ocracy is not always explicitly defined, so there are diverging perception dangers about “fairness”.
-* '''Resentment'''. If only a minority of participants in the community do-ocratize themselves into the hard jobs, they can resent others who don’t take on responsibility.
+* '''Frustration'''.
-* '''Social Exclusion'''. People who can’t do things, or choose not do things, are often marginalized in decision-making, which compounds social divides.
+*: Some people don’t have the time or means to do something, but they do have (real or imagined) expertise. In a do-ocracy, they will feel overrun and perceive the situation as slipping out of their hands. This can cause frustration. And remember: “''Fear is the path to the dark side…''”
-* '''The Martyrdom Complex'''. Some people have a psychological need to work strenuously most of the time, perhaps because they are seeking persecution and suffering, motivated by a desire for penance. In do-ocracy, people with these psychological needs tend to take more responsibility and sometimes make strict rules to impose on others.
+* '''Incompleteness'''.
 * The '''Tyranny Of Structurelessness'''.
 == Examples ==
-* '''Open Source Software'''. Typically, Open Source development groups care less about qualifications, age, and location than how much and what quality of work people submit.
+* '''Open Source Software'''.
-* '''IETF'''. Internet standards are written by… the people who submit standards. Per David Clark, one of the most famous quotes about the Internet: “We reject kings, presidents and voting. We believe in rough consensus and running code”.
+*: Typically, Open Source development groups care less about qualifications, age, and location than how much and what quality of work people submit.
-* The '''BitchunSociety''' from Cory Doctorow?’s '''[https://communitywiki.org/wiki/DownAndOutInTheMagicKingdom DownAndOutInTheMagicKingdom]'''. Probably an extreme form of do-ocracy.
+* '''IETF'''.
 * '''Wiki'''.
-* '''Hackerspaces'''. Many Hackerspaces around the world employ some form of do-ocracy, '''[https://hackerspace.gent/ Hackerspace Gent]''' wrote '''[https://github.com/0x20/hackerspace-blueprint/releases/latest/download/hackerspace-blueprint.pdf The Hackerspace Blueprint]''', a document describing how to run a hackerspace using do-ocracy and how to mitigate some of the issues of it.
+* '''Hackerspaces'''.
 == See also ==