1 Comment A presenation of Colony, a platform for Decentralized Autonomous Organisation

  1. Tiberius Brastaviceanu

    Like and other first adopters of the OVN model, Colony and are developing block chain tools for decentralized organizations. We are inviting everyone in this space to collaborate on these tools, because the infrastructure for distributed organizations is very complex, especially in the case of material production and distribution.

    Like SENSORICA’s (network resource planning and contribution/value accounting system), Colony is about managing a distributed workforce, it is mainly a project management tool, a platform that enables people to easily contribute to projects. Colony tries to remove managers, to make the organizations more horizontal. People suggest ideas, give other people feedback and contribute to projects, all that is peer evaluated.

    There are 2 tokens:

    * nectar (represents equity or ownership, rewards value creation or contributions),
    * pollen (rewards feedback, decision making, evaluations…)

    Pollen and nectar are related by recognizing that well-applied evaluations, feedback and decision making are valuable for the organization and are rewarded in nectar.

    [min 13:56] They hit to allocation of nectar based on a deliverable. But there is not much else on how contributions are evaluated. They are aware of SENSORICA’s work on the .

    Nectar is the equivalent of in the OVN model. The OVN model uses a , which affects equity if it is used as a factor in the .

    I think that the pollen token is a good idea, because it can capture some of what the OVN model considers calls “non-production activities”, which are contributions with no clear deliverables like office work, coordination and facilitation, feedback, evaluations, decision making… For example, feedback (comments), evaluations (vote +1, up or down, or assign a score), and decision making (if done on a platform like Loomio) can be tracked by software. Other activities can’t be easily tracked because they happen outside of the platform or in the physical world, for example communication and coordination (emails, social media activity), facilitation and orientation in physical spaces, face-to-face training of a person, … In these cases pollen cannot be automatically applied, and we need other ways to capture the contribution, and to evaluate it.

    The notion of “teams” [minute 8:19 in the video] within colonies limits the openness and the fluidity of the colony, creates silos. Anyone part of a colony is part of a team, to which he/she has been invited, based on trust. An agent can only invite 6 people. This model cannot support swarms, which is what SENSORICA advocates under the tagname of “long tail commons-based peer production”, and something that Primavera is also hammering with Backfeed. Swarm-like ventures will exist alongside closed ones, I am not making a judgement between the two. I suggest to the group behind Colony to get inspired from and . But I they are making a mistake by imposing such structures and limitations at the design level, early on in the development phase of their platform. made the same error of over-engineering the network/community from the start, and they collapsed. I suggest to provide a more generic platform and let people implement their structures based on their experience. No one knows how peer production functions, really. Not even those who have practiced it for the past 4, 5 years. This field is still emerging (methodologies, governance, management tools, organizational structure, …), and I think Colony places too many bets on specifics.

    There is no mention about physical assets management, supply chain management, customer relations and distribution management. This looks very early stage, and it is far from being able to support material production. But it can be applied to simple projects, especially ones that deal with digital production.

Leave A Comment

Your email address will not be published. Required fields are marked *