efficiency within lateral structures
October 27th, 2008A persistent theme in discussions of alternative economic systems is a trade-off between democracy and efficiency, with lateral structures considered more democratic, vertical systems more efficient. There are, of course, some inefficiencies specific to vertical structures such as ineffective or corrupt leaders or a mismatch of priorities between the leaders and the led.
However, it’s certainly true that the more people involved in a decision, the more difficult making the decision becomes. When three people decide something, there are three pairs of people. When 50 people are involved, there are 1,225 pairs of people. Subcommittees are used to avoid wasting everybody’s time, but they can become double time-wasters if the committee of the whole has to rehash everything from the subcommittee. Parecon improves on this problem a little, by limiting input in decisions to those affected by them. The committee of the whole never needs to address a problem that only affects those whose offices are on the third floor. But there are still trivial decisions that nevertheless affect many people*.
Over the last couple decades, there have been real revolutions in addressing this problem. The revolutions come in the form of fluid creation and rearrangement of small groups. You can see this in “issue-tracking software” like bugzilla, software that creates tools for collaboratively addressing bugs in (other) software. Individuals can easily join and leave the group of people involved in the discussion of the problem; people can post as much as they need to about one problem without affecting anybody not addressing the problem (as anybody not addressing the problem can leave). Problems can merge (by marking one as duplicate of the other), or become related (by marking one as depending on another).
A more familiar example of this might be Wikipedia. Similarly to bugzilla, by partitioning the concept of an encyclopedia into an unlimited number of “pages”, Wikipedia allows for the rapid creation of small groups. Groups can be as small as 1, or they can rapidly scale to multiple people working on the same page. If the page becomes particularly popular, many more people might work on it, or it might split up into separate subpages with different (but overlapping) groups working on each. Without such software, it would be unthinkable for so many millions of people to collaborate on a project the size of Wikipedia. Could you really imagine a mailing list or coordinating committee simultaneously juggling over 1m different encyclopedia pages? Trying to filter the discussion for only those subjects you were interested in? Despite relying on more traditional vertical structures for some things (such as maintaining the physical servers or deciding punishments for rule-breaking), Wikipedia has created a massive, lateral structure, with collaboration happening mostly in small groups.
This phenomenon–small groups within a large lateral decision-making structure–gets the best out of people–small group collaboration, without the inefficiencies of imperfect leaders. Even as it has its own imperfections, Wikipedia has demonstrated that it is a far more useful and used project than any commercial encyclopedia could have hoped to be in the 7.5 short years it has existed.
In my next post, I’ll share my ideas for how to spread that revolution further, how to see it move out of the realm of spreading software and knowledge, and see it in other walks of life.
* OK, technically, this isn’t the same as a bike shed problem, but it’s pretty similar.