Basic Idea: In small groups management can be automated. If it can be automated well enough, a hierarchy is not necessary. Small groups need to be able to switch quickly beteween adhocracy and democracy while preserving fairness. The following principles are a first attempt to provide a framework for this.

Principle: An operating ageement should be written with a specific purpose, in very simple language or ideally in pseudocode or actual code.

   Corollary: This document should contain a way to programmatically deal with issues such as "there is no person to do job X", by random selection or by rotation or by whatever other method is agreed upon.
   Corollary: This document should contain a way to programmatically allocate revenue and split profits.

Principle: Job titles are optional. Hats worn are necessary. Everybody should list the jobs they are happy to do in order of expertise.

   Corollary: Hats needed should be specified as soon as the scope of the project is determined.
   Corollary: Any hats left unworn by unwillingness should be traded around with some frequency.

Principle: Everybody contributes to a common diary or blog, at least once a day, with at least one sentence, explaining what they did during that day.

   Corollary: Everybody should be able to identify at least one useful thing they did each day they are working.
   Corollary: Anybody wanting to not work for a time should let everybody know in advance.

Principle: Everybody gets one vote. Tie breaks are decided by whoever is wearing the largest hat in that area or as specified by the operating agreement.

   Corollary: Votes are called when there is a disagreement and resolved as close to immediately as possible.
   Corollary: Valid vote outputs are yes, no, don't care, don't know enough.

Principle: Every rule agreed upon after the starting document is generated should carry an explanation as to in response to what event it was made.

   Corollary: The reason for the starting document itself is assumed to be "To accomplish our primary goal", which should be specified.
   Corollary: The more a rule can be automated, the more it should be, but this machine must never override anybody.

Principle: Any procedure that gets in the way of the stated goal must be moved out of the way.

   Corollary: When in doubt between toss and keep, default to keep. 
   Corollary: When in doubt between open and closed, default to open.

Principle: Nobody should create emergencies. Everybody should react to emergencies.

   Corollary: Emergencies should be definied strictly.
   Corollary: Emergency response is coordinated by anybody who is there and knows what they are doing.
Page last modified on February 03, 2015, at 04:08 PM
Powered by PmWiki