Dear Curtis,<br><br>I appreciate your summary below and would like to reprint it on the p2p blog ... would you like to expand and improve on it before?<br><br>Michel<br><br>
<span style="font-weight: bold;">Curtis Faith <</span><a href="mailto:curtis@worldhouse.org">curtis@worldhouse.org</a><span style="font-weight: bold;">></span>
May 09 01:39PM -0400
<a href="?ui=2&view=bsp&ver=ohhl4rw8mbn4#12fd773beb3104bf_digest_top">^</a><br>
<br>
The question of how to organize is really the core problem for a
building a world where collaboration is the norm.<br>
<br>
Some thoughts and principles for one way of organizing from the bottom
up:<br>
<br>
<br>
Leadership is trust earned through vision, respect, and action; not
implied by position or granted from above. <br>
<br>
Leadership is not about making decisions or having authority it is about
ability to effectuate the collaboration of work on for a given domain.<br>
<br>
Leadership is service.<br>
<br>
Leadership is synthesis.<br>
<br>
Leadership is mediation and mitigation.<br>
<br>
Leadership is design.<br>
<br>
Responsibility is shared and delegated at the full discretion of each
individual.<br>
<br>
Anyone who has a given primary responsibility is the "leader" for that
domain. That individual can delegate to others and then the others are
the "leaders" for their sub-domains.<br>
<br>
The customer for the domain's services are the ones who choose the
leader. For an organization as a whole, the customer is the leadership
for each of the domains, e.g. the leaders of sensing and intelligence,
design, manufacturing, distribution, and finance as well as
representatives from the product's customers would choose the overall
organizational leader.<br>
<br>
Each person chooses who they work for as their "leader" for any tasks
for which they wish to obtain responsibility. Responsibility requires
mutual approval by the one granting and the one accepting responsibility
for a given domain. For example, if you want to work in engineering on a
particular subsystem or module of a new device, then you must find
someone within engineering responsible for that module who is willing to
share responsibility with you by delegating a portion to you.<br>
<br>
There should be a grievance process whereby it is possible to replace
leaders over a domain on initiation of either the customers for that
domain, or those who are responsible for sub-domains.<br>
<br>
For domains for which we do not care to pay such close attention, or do
not have time to acquire the relevant expertise, we can delegate
responsibility for our decisions to someone we trust who becomes our
representative for these domains. These representatives, in turn, can
choose to delegate decisions to someone they trust carrying our vote
with them.<br>
<br>
Decisions should be unanimous and put to vote by anyone who commits to
learning enough about the issues to give the vote a fair hearing. If
unanimity cannot be reached then a course which receives 95% approval
should be sought, if not 95% then 90%, then 80%, and finally 2/3
supermajority as the last resort. <br>
<br>
A lack of consensus means that someone's point of view is not being
heard. Vote representatives should work out any issues ahead of actual
voting and learn enough to arrive at the highest possible consensus
decisions by making sure everyone's real issues are addressed in any
plans or decisions.<br>
<br>
All leadership responsibility is subject to a quarterly vote of
customers and sub-domain leaders. <br>
<br>
Resource prioritization is handled through a point system. Each member
receives 1,000 points each month and allocates gross profits between 20%
to 50% each for three areas: operational improvement expenses; building
and expansion expenses; and member bonus or benefits.<br>
<br>
An entrepreneur's role in such an organization is to get the leaders of
the necessary groups to agree to allocate resources to the proposed
project.<br>
<br>
All records of decisions and expenditures are completely open for
inspection at any time by anyone.<br>
<br>
<br>
Peace<br>
<br>
Curtis<br clear="all"><br>-- <br>P2P Foundation: <a href="http://p2pfoundation.net" target="_blank">http://p2pfoundation.net</a> - <a href="http://blog.p2pfoundation.net" target="_blank">http://blog.p2pfoundation.net</a> <br>
<br>Connect: <a href="http://p2pfoundation.ning.com" target="_blank">http://p2pfoundation.ning.com</a>; Discuss: <a href="http://lists.ourproject.org/cgi-bin/mailman/listinfo/p2p-foundation" target="_blank">http://lists.ourproject.org/cgi-bin/mailman/listinfo/p2p-foundation</a><br>
<br>Updates: <a href="http://del.icio.us/mbauwens" target="_blank">http://del.icio.us/mbauwens</a>; <a href="http://friendfeed.com/mbauwens" target="_blank">http://friendfeed.com/mbauwens</a>; <a href="http://twitter.com/mbauwens" target="_blank">http://twitter.com/mbauwens</a>; <a href="http://www.facebook.com/mbauwens" target="_blank">http://www.facebook.com/mbauwens</a><br>
<br><br><br><br><br>