Networks, Hierarchies, and Markets: Aggregating Collective Problem Solving in Social Systems
How do decentralized systems collectively solve problems? Here we explore the interplay among three canonical forms of collective organization--markets, networks, and hierarchies--in aggregating decentralized problem solving. We examine these constructs in the context of how the offices of members of Congress individually and collectively wrestle with the Internet, and, in particular, their use of official websites. Each office is simultaneously making decisions about how to utilize their website. These decisions are only partially independent, where offices are looking at each other for lessons, following the same directives from above about what to do with the websites, and confront the same array of potential vendors to produce their website. Here we present the initial results from interviews with 99 Congressional offices and related survey of 100 offices about their decisions regarding how to use official Member websites. Strikingly, we find that there are relatively few efforts by offices to evaluate what constituents want or like on their websites. Further, we find that diffusion occurs at the "tip of the iceberg": offices often look at each others' websites (which are publicly visible), but rarely talk to each other about their experiences or how they manage what is on their websites (which are not publicly visible). We also find that there are important market drivers of what is on websites, with the emergence of a small industry of companies seeking to serve the 440 Members. Hierarchical influences--through the House and through the party conferences--also constrain and subsidize certain practices.
|Date of creation:||Jun 2009|
|Contact details of provider:|| Postal: 79 JFK Street, Cambridge, MA 02138|
Web page: http://www.ksg.harvard.edu/research/working_papers/index.htm
More information through EDIRC
When requesting a correction, please mention this item's handle: RePEc:ecl:harjfk:rwp09-017. See general information about how to correct material in RePEc.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: ()
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
If references are entirely missing, you can add them using this form.
If the full references list an item that is present in RePEc, but the system did not link to it, you can help with this form.
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your profile, as there may be some citations waiting for confirmation.
Please note that corrections may take a couple of weeks to filter through the various RePEc services.