
Men of an RAF Repair and Salvage Unit working on a damaged Supermarine Spitfire Mk IX of No 403 Squadron, Royal Canadian Air Force, at a forward airstrip in Normandy, 19 June 1944. | Imperial War Museums | Public Domain
“Platform Cooperativism” is a fairly recent concept coined by Trebor Scholz and Nathan Schneider to disrupt the collaborative economy scenario, which is currently dominated by a few “unicorn” corporations and by what many people consider a neo-capitalist perspective. The concept is particularly timely because it coincides with the emergence of new proposals linked to the Social and Solidarity Economy that review the links between the economy, society and democracy, both inside and outside organizations. The concept of platform cooperativism can connect the tradition of free software (from a digital Commons perspective) with the current demands of “crowd-workers” affected by extractive versions of the Sharing Economy.
In light of the recently published guidebook Ours to Hack and to Own, edited by Trebor Scholz and Nathan Schneider, and the Platform Cooperativism 2016: Building the Cooperative Internet conference held recently in New York, this article aims to summarise a few approaches related to the design, user experience and co-creation of digital cooperative platforms. It focuses on an explorative research session that we facilitated during the accompanying “unconference”, which gave rise to a series of potential lines of action related to online reputation systems for platform coops.
From crowd-workers & followers, to cooperativists & owners
As Scholz and Schneider point out in Ours to Hack and to Own, platform cooperativism emerges at the intersection of shared governance and shared ownership. Technology should be an opportunity to broaden the scope of organizations based on the Rochdale Principles (which were first set out in 1844 to boost the social and economic impact of these organisations). Similarly, Scholz argues, modern digital platforms should be inspired by the cooperative movement and based on the principles of democracy and self-management. These new technological structures should embed their values and support local economies. Thus, platform cooperativism should be a response to the “new industrial renaissance” —to quote Douglas Ruskoff—, which is currently controlled and centralised by small number of companies, generating a new digital capitalism in which workers and users are merely followers.

Platform Cooperativism 2016: Building the Cooperative Internet. New York, 2016 | Trebor Scholz | CC BY-NC-SA
In Ours to Hack and to Own, Mckenzie Wark discusses the vectoral political economy, in which most information is private property, and which is in many respects worse than the capitalist political economy. It is what Steven Hill calls a “freelance society” made up of “crowd-workers” threatened by an “un-sharing economy”. According to labour organiser Kati Sipp, labour assessment of people who work in the cooperative platform and reputation-based economy should incorporate the best practices of the collaborative economy. Digital technology based on cooperativism should contribute to eliminating inequities for the people involved. In the book, after analysing three types of cases (time banks, food swaps and makerspaces) close to platform cooperativism, Juliet B. Schor stresses the key issue of inequalities related to race, class, education and gender. To prevent this, she suggests that there should ideally be a diverse group of founders and early participants.
Another important perspective – which is discussed in the collection of essays in the book and was also highlighted at the conference – can be found in the current political and economic context of Barcelona. The papers by speakers like Mayo Fuster and Francesca Bria brought up critical issues such as technological sovereignty, gender balance, transparent governance and other challenges in the co-creation of public policies, at this crossroad between the social economy and the sharing economy.
Community-centred design, lean platform co-development and open source
Along similar lines, during the “How to Build Platform Coops” panel organised by Sasha Constanza-Chok (Civic Media MIT & rad.cat), Una Lee spoke about community-centred design processes and the concept of “design justice”: how to design with and within communities in such a way as to advance social justice. This tactical approach to developing platforms and interfaces connects design practitioners with people who have been historically marginalized by design, in order to radically collaborate with them in building relationships leading to the creation of platforms, processes, and systems that will ultimately have an impact on their lives. An example: the action research and facilitation work carried out by the team behind contratados.org to uncover the actors and processes in low-wage labour recruitment along the Mexico-U.S. migrant stream.
Another key element discussed in the same panel focused on the need to adopt and incorporate strategies from the lean startup approach (on which the majority of big, extractive “sharing economy” platforms such as Uber and AirBnB are based). An important aspect of the ”lean” methodology is the fact that it also represents a learning process, as Evan Henshaw-Plath explains. Similarly, new platform cooperatives should also incorporate early feedback in their learning and development loops and base their growth on “minimum viable platforms” modularly built around user experience. This approach is similar to the analysis set out in the foreword of this review of methodologies carried out by Dimmons for the design and incubation of collaborative platforms, which also points out the need to identify and scale up new ways of funding platform coops (other than aggressive “business angels” and other highly speculative formulas).
Another key element discussed by this panel was the importance of the open source philosophy: when platforms based on cooperativism appropriate the strategic “lean development” used by their “extractive” competitors, open source and the ethos of the Free Software movement seems to be the right approach and the way forward. At the conference, Drutopia activist Micky Metts remembered how Richard Stallman harnessed the hacker culture tradition of the 1970s to launch the GNU Project. As Paola Villareal pointed out, open standards (such as oHail, an API standard for ride-hailing services) are a basic element for engaging more people in building truly open cooperative technology platforms.
What if the “cooperativist UX” adopts open badges for a fair reputation system?
Following this panel at the conference, both of the authors (Enric Senabre and Ricard Espelt) were interested in further exploring the critical issue of co-design, the user experience (UX) approach and requirements of platform coops, which we had discussed with other people from the “cooperativist UX” point of view. So we organized a short explorative session on the third day of the PlatformCoop unconference at Civic Hall, with participants from the fields of digital media and software development, social justice, community organizations and unions, all interested in the approach.
We organized a dynamic session based on a process of modularly building new user stories for platform coops in general, following a process that is often used by agile developers to identify new requirements for software. In our case, this interaction allowed us to document the discussions around different issues from the perspective of the needs and expectations of cooperativism (related to user stories and platform interfaces in general) following the research through design approach.
The results were interesting, although the session did not work exactly as we expected, given that we had intended to brainstorm and generate as many user stories as possible on different types of requirements. Instead, we began with a reflection on which specific functionalities and features (other than those available on existing online platforms and social web interfaces in general), if any, could be explored. It blocked up the session for a while, but after coming up with some missing elements that could help to generate trust in online communities related to cooperatives and unions, we finally arrived at the key element of online reputation systems for every social web application.
As we started to specify some basic definitions of a user story for cooperativist-led reputation and feedback systems, some of the examples that had been shared over the previous days at the PlatformCoop conference resonated in the discussion. Examples include the case of crowd-workers not wanting to have their photo on their online profiles, or the other side of online trust systems: when sharing economy platforms are rated by users “outside the platforms”, as on FairCrowdWork Watch; or when users can blacklist unfair requesters on microtask platforms like MTurk via the CrowdWorkers browser extension; or the example of Contratados’ employer and recruiter reviews.
But what about the positive side: building trust among platform cooperativists by transparently connecting to each other online and mutually recognising value? And what about adding openness and transparency? At this point, trying to move further, we discussed open source examples like the Wikipedia barnstars awarded to contributors for hard work and due diligence, or the digital self-assessment of an organization’s social impact used in the social and solidarity economy in Catalonia, as well as the interesting and relevant example of Mozilla’s open badges, which usually operate under the umbrella of digital learning but could also be adapted and adopted….
After drawing inspiration from imagining possible new positive rating icons (beyond the classic, limited and even pernicious standard of star rating features), we went on to discuss variations of a user story, which can be summarized in the following formula: “user + action + component + goal” (as expressed in co-design workshops by the Platoniq facilitation model):
What if as a platform cooperativist + I could mutually and independently rate and be rated + with a distributed and generative badges-like system + so I can contribute to build networked solidarity and trust.
That lead to interesting variations around user stories of this kind, which can be seen as a pattern that grows with the addition of other actions or goals related to equitable models, and can be modular and allow user control of the levels and types of personal information displayed. Although we didn’t have time to move to different potential requirements, the story allowed the group to address other key elements like:
- The importance of avoiding long and tedious forms (if the reputation system is to embrace meaningful indicators beyond stars or “likes” and “dislikes”).
- The adoption of effective peer-to-peer mechanisms at the technical level, to ensure that mutual feedback is solid and coherent.
- The need for UX design to pay attention to ensuring attractive icons and symbols to reinforce motivation.
- The fact that aggregation (and, of course. critical mass) means that individual open rating in given platforms could also be a way to dynamically rate the platforms themselves.
- The interesting issue of mutual mentoring and skills for adopting and generating these kinds of badges, as a channel for deeper understanding of the internal logic of digital platforms and how to build or improve them.
Questions for future research, and development
As a follow-up to the session, apart from this written report, we consider it important to highlight the fact that the output resonates with the research work of the Stanford Crowd Research Collective, especially in relation to the centralisation and decentralisation of reputation systems in “crowd guild” platforms, and the importance of considering the social dimension of sustainability when building technological systems, as set out in the KarlsKrona Manifesto.
The next steps in addressing “platform cooperativism UX” should continue along these lines: new user stories that generate both potential platform coop requirements and design-driven research outputs. In the short term, there is the upcoming Platform Coop event in London, where we believe that co-design discussions can keep contributing to advancing this new digital economic paradigm. We also hope to bring this methodology and the same questions to our local context in Barcelona, especially in relation to existing and new coops that are developing digital platforms and strategies in the emerging field of cooperative agricultural food products and possibly others.
Adam Hyde | 29 November 2016
hi Enric and Ricard.
A great experiment and review of the outcomes. I wrote a response to it here:
https://www.adamhyde.net/response-user-experience-platform-cooperativism/
Adam
john gieryn | 30 November 2016
Thanks for the great efforts Enric and Ricard; I look forward to reading much of the linked content. Wish I had not been facilitating a session while yours was happening! Seems you did a great job in creating value with the group.
I think this article, and Adam Hyde’s comment, highlight the challenge of balancing action and discourse, production and planning, in the much needed (and in many senses already successful) efforts such as that of the nascent Platform Co-op community and the Consortium being built. Trebor Scholz, Nathan Schneider, et.al. have done an amazing job of describing the banner, and convening some top minds from technologists to designers, to social justice advocates and community organizers. Now is the challenge, as co-designers, of how to build trust based in shared norms and values, shared language, and active collaboration.
Reflexively related to these, is “social capital”, which isn’t to speak of authority or domination as in “capital”, but is the frequently used denotation for the value in our interpersonal existence and interaction. Social capital is said to contain three dimensions; those assembled at the Platform Co-op Conference seem to rank highly on the Cognitive one, and the efforts of many have been building capacity in the Structural one, but that which may need the most attention is the Relational dimension, which in turn’s composed of confidence, interdependence, mutual responsibility, and (as Adam Hyde mentions) group identity with which participants identify. You can read a bit more about these ideas in an article I’m about to publish (relates a strategy for growing the Relational capacity → collective action) https://medium.com/@CoOpChange/get-intercultural-to-open-access-ad7c6b07bdc0.
I look forward to continuing to learn from you both as to best practices for collaborative, participatory methods for making wicked problems understood, and giving regular folk the tools to solve them.
In Reciprocity,
–john
john gieryn | 30 November 2016
hopefully my last comment is just pending, and not lost to the ephemeral blogosphere…
anyways, here’s the link to the article I mentioned in that comment, in case the link broke when I published it: https://medium.com/enspiral-tales/get-intercultural-to-open-access-ad7c6b07bdc0#.9mp5lr7iy
Enric Senabre | 02 December 2016
Hi Adam,
Thank you very much for your detailed response to the experiment we started! I completely agree with you in terms of how complex or even unrealistic could be to ask “design questions” for open ended problems, but as you also mention we finally focused on a specific need (trust among peers, and reputation mechanisms for generating it). This was a first result of constructive and discursive iteration generated by sharing some possible new icons, modularly composed user stories and (very basic) drafted requirements.
Our aim was to keep refining a methodological tactic that follows this logic, connected to the tradition of participatory design, but also the implicit-explicit loops behind agile and lean: designerly ways of generating solutions to community-oriented problems (usually with some digital tool/context involved, like in this case), while at the same time generating data and insights that can be incorporated to research / knowledge outputs.
In times when software has taken command (quoting Lev Manovich book, or in other words when “software is eating the world”, as I read somewhere else), user stories as a structure for agreeing on who, how and why solving all kind of problems makes a lot of sense to me, even moving behind the main focus of software development. With Platoniq there’s a line of work doing this with other partners in the incubation of civic-oriented projects via “idea camps”, for example
I mean user stories as “a generative game” not only for identifying software requirements (in my opinion a requirement is a more refined, detailed and developer-oriented user story, that emancipates from such a common language). User stories can help to bring in some stages of a research different perspectives and integrate diversity. If you add then some participant observation in parallel, and try to extract from the discussions what’s behind assumptions, limits, context, views etc, while a group advances in making the user story a more concrete design afterwards, then both ways combined are in my opinion not much different from the practices of action research.
I think that connects also to what you consider at the end was the real value of our little experiment (which was concentrated in less than one hour, so not optimal conditions at all, when the ideal context for these things as you know are dedicated retreats and “slow sprints” 🙂
In my opinion, it represents some validation that this dual ambition is viable: research through design (my main source here is still the book “Universal methods of design” https://searchworks.stanford.edu/view/9706083 full of nice documented tricks) for generating useful or practical results (in this area, documented user requirements) while also contributing to areas of knowledge or discussion in a given domain. Like we are doing here, at some meta level!
Enric
Ricard Espelt | 06 December 2016
John and Adam, thank you very much for your comments as well as your articles and other references.
My current research, around small agrofood consumption groups in the city of Barcelona, self-manageds with the cooperativism principals, give me an approach to platformcoop closer to the social capital around the members’ organization than the possibilities of technology.
Chequing the contents and the cases presented in the last Platformcoop Conference, we could think that platforms are useful to scale the cooperative organizations to impact better in the market, employment, etc. In that sense, currently, the movement has developed a wide cognitive capital and it’s exploring how to structural capital is impacting in the efficiency of the organizations but, as John argues, the relational capital is maybe the less explored. Obviously, this statement is formulated according to my experience analysing these type of groups (close to political and social activism) and where the relation among members are a key point to the way the group operates.
In my point of view, this is something relevant in the definition of the platform coops. How to grew up and maintain, at the same time, the cohesion and the confidence among the members? How to keep the social and the political compromise of the organization? And also, as John states, how to be aware about intercultural competence in the agenda of the platformcoops evolution?
Adam Hyde | 08 December 2016
hey Enric,
I think here is some useful outcomes of the experiment. I would categorize them as two distinct parts:
1. the ‘findings’ from the participant
2. an exploration of a process
Number one is what it is, and you can see it as more or less useful. It seems it was useful for helping the community start to understand the utility implications of a political critique of platforms. Thats a useful thing in itself.
However I think the results of (1) are a direct outcome of the process, and I believe the process was a good start but I would recommend you take the opportunity to rethink things a little. This will help you with (1), ie. get better results.
Its for this reason that I challenge the tools you chose to use. I don’t think the intent or even framing of user stories is very useful. It will get you something but you could get a lot better if you threw user stories away and came up with something new, even if it is just to change the language. ‘Users’, for example is also a politically loaded term when it comes to platforms. It suggests a form of subservience (in my opinion) to both the developers of the platform, and the technology itself.
Platform Cooperativism, as far as I can understand, is trying to escape exactly this paradigm. So I would challenge at the very base level the use of language of ‘user stories’. But actually, I think there is a greater problem – the problem of using a process for designing user interfaces in a process that is never going t give you a design for user interfaces. Your explorations are at a far more important higher level and you deserve a process that maximises the outcomes of that exploration. Why use a software design paradigm when that is not what you appear to be doing. Don’t force this process into a software design process yet. It is too early. Design another, more appropriate process wiht more appropriate language, and use that. Then when you are actually designing UX, throw away that tool and use user stories (or something similar).
Clayton Dewey | 06 June 2017
Great article! As a User Experience Architect and co-founder of Drutopia (drutopia.org) much of this resonated with me. In fact, you put into words much of what we’ve been trying to do – start with the practical problems communities are facing and building solutions collaboratively. We’ve found this to be working well so far.
So far though, our user research has been done very directly- video conferences with participants and then the sharing of wireframes and gathering feedback by email.
Once our product is live we will want to have a platform for Drutopia members where they can ask questions, make and coordinate feature requests together, etc.
So far we haven’t settled on a platform for this. Our code is housed on GitLab because of its open source, decentralized structure (as opposed to GitHub, which is more centralized). However, GitLab (and GitHub) lack the kind of intuitive interface and social web features (eg: badges, ratings) that would empower our members (especially the less technical ones) to engage with the project.
There are two platforms though (both open source), that we are looking at.
Discourse (discourse.org)
Helpy (helpy.io)
I’m leaning towards Helpy at the moment. They don’t have badges, but I talked with one of their developers and it is something they are building for a client and so they hope to contribute it back to the open source version. We’ll see!
Leave a comment