Decision Making/Problem Solving

Decision Making/Problem Solving, Network Design, Participation

Four pillars of the design of participatory architectures

street wisdomIn return to my recent reflection on the “participatory architectures” for innovation, the issue that really fascinates me; the essential question I’ve been asking is: What can explain that some participatory projects work better than others? Are there any patterns of the collective behavior that help us to improve the participatory initiatives´ design?

Learned by several recent experiences (some good and some bad ones), the invisible hand of participation is an effective filter for innovation only if it´s conceived within an intelligent architecture of interactions.

On a further consideration, I consider there are four pillars that have a decisive impact on the success or failure of that “architecture”: 1) Ability of call, 2) Ability of structure, 3) Filtering capacity, 4) Synthesis capacity. Read more ›

by × August 30, 2013 × 1 comment

Collaboration Culture, Complexity, Decision Making/Problem Solving, Emergence/Self-organization, Group Performance, Network Design

Networks, enterprises and transaction costs

1_Colaboracion grupos_Eric Constantineau FlickrIn this post I would like to share an idea that seems to me quite complex: Are networks better than companies? Is it true that the “transaction costs” have collapsed so much to make the “network” a superior alternative to the “enterprise”?

Well, once again, let me say “that depends”: The networks are not always more agile than firms. It is rather the opposite: usually it happens that they involve a great complexity of relationship management. Yes, a robust and well-oiled network can be more agile than a versatile firm; okay … but to achieve this is not easy at all.

It hurts me to recognize that networks that work well and are agile, are still an exception rather than a rule. They serve to share ideas and to promote the exchange of knowledge, but when it comes to make a joint effort and carry out the distributed work, a lot of inefficiencies jump out.

Read more ›

by × August 11, 2013 × 0 comments