Plattformskooperativ utmanar internetjättarna

Idén till plattformskooperativ kommer ur insikten att det som vid första anblicken verkade vara ett praktiskt sätt att dela tjänster, så som AirBnb och Uber, spårat ur till vad som kallas plattformskapitalism.

Via sin digitala plattformar drar företagen in enorma pengar på folks vardagliga arbete, men ger väldigt lite tillbaka, både till lokalsamhällena och de som bidrar med sina tjänster. I ett plattformskooperativ är det istället de som hyr ut sin lägenhet eller skjutsar någon som gemensamt äger verksamheten, för att på så sätt skapa lösningar som är socialt hållbara och ekonomisk lönsamma för fler.

När vi tänker på konsumentkooperativ idag, alltså företag där konsumenterna gemensamt äger företaget, är det ofta stora etablerade företag som Coop och Folksam vi tänker på, där det kan vara svårt att se den ursprungliga tanken med den typen av organisation. Men när de traditionella kooperativen bildades var det ett sätt att bryta monopol, ta tillbaka kontrollen över en orättvis prissättning och se till att vinsten från verksamheten återinvesterades i bättre utbud och tjänster.

Med plattformskooperativen har vi möjlighet att bryta liknande monopolsituationer på nätet, och garantera att vinsterna av våra små arbetsinsatser med att köra taxi eller hyra ut en lägenhet inte automatiskt hamnar i Silicon Valley.

På internet betalar vi ofta inte i form av höga priser, som när Konsum utmanade lokala livsmedelsmonopol i början av 1900-talet, utan med vår arbetsinsats och vår personliga integritet. Dagens internetföretag kan göra mångdubbelt större vinster än traditionella företag, i förhållande till hur många anställda de har. Anledningen är det arbete vi som användare gör åt dem. Varje gång vi fyller i våra personuppgifter, gillar något eller kommunicerar med andra på deras plattformar, skapar vi värdefull data som kan säljas till annonsörer.

Genom att som kooperativ driva en egen molntjänst eller plattform kan vi utnyttja alla möjligheter och fördelar med decentraliserade plattformar utan att förlora kontrollen över vinsten eller vår personliga data.

En annan anledning till att organisera sig i kooperativ är att det ger konkreta praktiska fördelar att driva en verksamhet gemensamt. Det sparar kostnader och administration, och kan göra det möjligt att gemensamt anställa specialister för vissa arbetsuppgifter. Idag är bostadsföreningar och kooperativa förskolor småskaliga exempel på kooperativ organisering. Ett intressant historiskt exempel är de frysboxföreningar som var vanliga på 50-talet. Att ha en egen frys hemma var alldeles för dyrt, men genom att gå ihop med några familjer i en ekonomisk förening och dela på en frysbox blev det tillgängligt och prisvärt.

En modern variant på frysboxföreningen skulle kunna vara att gå samman för att driva en gemensamma server, för att få tillgång till krypterade och säkra alternativ till molntjänster som Google Drive, Dropbox och Messenger. Det kan göras i en relativt liten skala, men kräver att någon med teknisk kompetens finns tillgänglig för underhåll och är (precis som frysboxarna på 50-talet) dyrt att göra var och en för sig. Det finns redan många spännande exempel på det här, som kallas “Cloud Coops” och som är något jag tror att vi kommer att få se mycket mer av, ju mer vi ser konsekvenserna av att lämna vår personliga data i händerna på tvivelaktiga företag. I Sverige finns redan föreningen Fripost som driver en mail-server som en ideell förening och håller workshops i att lämna Googles tjänster.

På webbplatsen The Internet of Ownership finns en katalog över plattformskooperativ som tillämpar principen om gemensamt ägande av digitalt drivna verksamheter inom en mängd olika områden. Där finns till exempel Stocksy, ett slags Flickr som ägs av fotograferna; Fairmondo, ett Blocket ägt av säljarna och köparna och en lista på Cloud Coops för kooperativa molntjänster.

Hur ska föreningslivet förhålla sig till Facebook?

Efter den senaste tidens avslöjanden har det blivit uppenbart att Facebook inte är ett företag som värnar om demokrati, personlig integritet eller unga personers psykiska hälsa. Så hur kan föreningslivet förhålla sig till den här teknikjätten, som vi är så beroende av för att organisera oss och nå ut till medlemmar?

Foto av Shadowsun7

Vad vi vetat sedan tidigare är att Facebook samlar in all vår användardata för att sälja riktade annonser. Det kan låta harmlöst, men har till exempel använts för att sälja annonspaket som riktar sig specifikt till psykiskt instabila tonåringar.

Det nya som kommit fram de senaste veckorna är hur den sammantagna datan från miljontals användare använts för att påverka politiska val och folkomröstningar, utan användarnas godkännande och eventuellt i strid mot lagen.

För att ge en kort sammanfattning, så samlade tvivelaktiga forskare och företag 2014 in data från 50 miljoner ovetande användare. Baserat på den informationen skapade de ett system för “psykologisk profilering”, till exempel genom kartläggning av användarnas sexuella läggning, barndoms-trauman eller etnicitet. Det systemet användes sedan för att, ofta med skrämselpropaganda, skapa riktad annonsering för Trumps valkampanj och Brexit i Storbritannien. Facebook har känt till att användardatan missbrukats, men i princip inte gjort något alls för att stoppa det.

Hur kan demokratiska föreningar, speciellt föreningar för unga personer, förhålla sig till det här? Vi vet att många föreningar är beroende av Facebook för att nå ut till nya och gamla medlemmar, för att opinionsbilda, ordna event, diskutera och organisera sig internt.

Hur skyddar vi våra medlemmars personliga data från att missbrukas av skrupellösa företag eller xenofoba politiska kampanjer?

Är det överhuvudtaget förenligt med demokratiska värderingar att använda Facebook?

I Digidem Lab arbetar vi med att hitta och rekommendera säkra digitala verktyg för organisering för föreningslivet. Säkerhet är alltid relativt, och behöver ofta vägas mot användarvänlighet, effektivitet och förmåga att nå ut till många. Även om vi föredrar kryptering, öppen källkod och decentraliserade tjänster är det inte alltid praktiskt möjligt att använda den typen av tjänster.

Det finns ändå några saker som vi tycker att alla föreningar kan börja göra redan idag

  • Gör inte era medlemmar beroende av att skapa konton hos teknikjättar som Facebook och Google, som lever på att samla in och sälja personlig data. Det är en sak om medlemmar vill använda de tjänsterna privat, men som förening bör ni inte göra det valet åt dem. Se till att det finns fler ställen än Facebook för att hålla sig uppdaterad om vad som händer i föreningen.
  • Utforska alternativa tjänster för event-organisering, diskussioner, beslutsfattande och kommunikation i föreningen, för att successivt kunna byta till tjänster som respekterar demokrati och personlig integritet.
  • Flytta diskussioner och distansmöten mellan aktiva medlemmar till andra tjänster, även om ni fortsätter att använda Facebook för att nå ut till nya medlemmar.
  • Diskutera sociala medier med era medlemmar och vad det kan få för konsekvenser att dela personlig information och politiska åsikter.

I nästa blogginlägg kommer vi att rekommendera några säkrare digitala verktyg för föreningar.

Making Madrid´s citizen platform accessible to a wider audience

Upcoming project at Medialab Prado’s Collective Intelligence 2017.

The citizen platform Consul is used by Madrid and over thirty other cities in Spain, as well as several cities in Latin America. In the last few months it has also been used by the social housing company of Paris for participatory budgeting and the British People’s Momentum for their annual meeting. This makes it one of the most interesting and well used open source projects for deliberative democracy right now.

Many of the organisations and social movements that we in Digidem Lab are in contact with are impressed by the possibilities of Consul. But it is also hard to demo the tool for them, and show them what their next step for implementing it would be.

Although a very useful tool with a wide range of use cases, the installation and setup process requires a lot from its administrators, and is something we believe is holding it back from being more widely used.


Adapting to new needs

With the new target audiences for Consul (cities abroad, NGO:s, different kind of participatory budgets), we need to look at the user journeys for adapting the tool for the different users and see how to best meet their needs and expectations.

This project is about finding the best ways to lower the threshold for the installation and setup process for these new target audiences. With an interdisciplinary team of marketers, developers and designers, we would be able to tackle many of the obstacles to wider implementation of Consul and provide a clear step by step process for any organisation interested in implementing and adapting it.

Any self hosted platform will of course have the problem of needing people with technical expertise. But some open source platforms, like for example Nextcloud, has shown an ability to meet their users half way by providing a range of options for installations, demo versions and documentation.

Finding the pain points

We will work in two phases, by first identifying new target audiences, their needs and pain points; then work iteratively on the setup process and documentation.

In the first phase we will get to know the users by defining target audiences, researching user experiences, defining personas and drawing user journeys.

Defining new target audiences: Which are the new groups using Consul, and how do we pinpoint and define these new users?

Researching user experiences: Interviewing for example Open Source Politics from France and Peoples Momentum from the UK about their experiences from using Consul in new contexts.

Personas and user journeys: Defining detailed profiles for our new personas. Creating user journeys for how the personas ideally would come to adopt Consul. Identifying pain points and obstacles where improvements in the documentation and installation process can be made.

Working on improvements in iterations

In the next stage, we work on improvements in iterations looking at for example automated installation options; a clearly designed installation guide; pre-configured installation profiles or demo versions based on the known user cases like citizen platforms, annual meetings, participatory budgeting.

Automated installation: Help the Consul development team with automated installation scripts for Ansible or Heroku. There are some progress in making Docker images that we could develop further.

Installation guide: There is a new drafted text from the Consul team. We could design and set up a manual in for example Read the docs or Hexo and work on the texts. Another option to explore is to make instruction videos for the different user cases.

Installation profiles and demo versions: The Consul team is working on a preconfigured setup file that we could extend to cover more cases that would be useful for demo versions.

Going worldwide

We are collaborating with the Consul development team to contribute to their work and base this development on their future needs. They are already making progress in these three areas, that we could feed into and develop further during the lab.

The overall theme is to make the installation and setup process easier and more accessible, to make it go worldwide! While these are general ideas about how to do it, the exact ways will depend on the identification of personas and user journeys, our contact with the Consul team, and the input and different skills that the working team contribute with during the lab.

Work less, produce more

According to tradition, a programmer’s productivity was measured by “lines of code” in the old days. That is, the amount of code you wrote.

Anyone remotely interested in programming understands how crazy that is, because the less code you need to write to make something happen, the more talented programmer you are (if the code is documented, structured and can be understood by others).

The fact that this measurement was used isn’t that crazy though — that’s our economic system’s standard way of measuring work. We get rewarded for working hard, doing overtime, putting in the hours and so on. If I as an employee come up with a way to do my job in less hours, it’s not like I will be rewarded for it. Just imagine if I came up with a way of completely automating all of my assignments at work. I would probably lose my job.

So a lot of innovation when it comes to automation, which is what a lot of innovation is about, is hampered by how the economy is structured. There is simply no economic incentive for it.

As a result, a lot of amazing innovation comes from other incentives than economic ones. The autobiography of Linus Torvalds, the main guy behind Linux, is called “Just for fun”. That is also how he describes his motivation behind writing the operating system that powers most of the internet servers and supercomputers today. And that is how large sectors of the open source sector still works.

If we truly want an innovation driven economy though, we need to create more incentives for productivity and automation. For starters, collectively owned workplaces would help. That way you might actually benefit from automation and a rise in productivity. Sharing our results and ideas freely will also immensely benefit innovation. And last but not least, we need to get rid of the work ethos that are encouraging us to measure productivity in “lines of code”.

Designing a guiding app for digital democracy

This is a description my project for as a part of the Collective Intelligence for Democracy workshop in November 2016 for MediaLab Prado Madrid.

In Sweden, more young people use Facebook every day than who voted in the last general election. This is an international trend, and most certainly does not come down to lack of interest in politics from young people, but from outdated and excluding tools and processes for democratic participation.

Digital tools open up completely new possibilities for instantaneous participation, discussions and decision making, without relying on geographical proximity. If traditional political instances and organisations do not adapt to new ways of working and thinking, they will keep losing trust and members. If they take advantage of the new possibilities of participation they will have enormous potential.

In the rest of Europe, we look up to you in Spain. You have found ways of implementing some interesting digital services in your local municipalities, political parties and NGO:s, and the rest of Europe has a lot to learn from you.

So we know that there are a lot of interesting tools already available, that needs to be tested and evaluated in local contexts.

In my organisations, Digidem Lab and ABF Göteborg, we are planning a long term project starting next year together with Sweden’s Local Municipalities, the Green Party, The National Council of Swedish Youth Organisations, Young People with Disabilities and Young Media. The project will research new ways for young people to get involved with digital democratic processes.

What we have seen in the run up to this project is that there is a demand for new technology, both in municipalities, parties and NGO:s. But also an urgent need for concrete examples of implementation, cost efficient solutions and practical guidance. And we think that this also is true in an international context.

Digidem Guide, the project that we will develop during this workshop, is an app guiding organisations to the digital tools that meet their specific needs for direct democratic participation via the Internet. The app will help organisations to find the right tools for digital democracy based on criteria like field of application, scope, need for security, technical knowledge and licensing.

The target group is decision makers in NGO:s, political parties and local municipalities. By developing it in an international context with all the valuable experiences from other team members, we will widen the reach to an international audience.

The project’s aim is to make existing tools available to a wider audience without technical knowledge or previous experience in the field. By broadening the user base we will also be able to get better feedback on the tools to help proceed the development further.

As a web strategist who has worked for NGO:s for about fifteen years, I know that it takes time to introduce new technologies and new ways of working. Having said that, there is often a willingness in organisations to find ways to get people involved and widen the reach of the organisation.

My experience is that usability is the key to succeeding in introducing new digital services. We need to be sure that the new tools and workflows that we introduce are as intuitive and user friendly as possible. To be honest, that is not always the case with open source applications. Therefore, to make the tools work for everyone, we need to involve people from all sorts of backgrounds and levels of technical experience who are willing to do user tests and evaluations, and help developers and designers in finding the right tools for the right task.

The development and design of the app will be focused on early user testing with the whole team, and I would therefore very much welcome the participation of activists, politicians and NGO representatives in the process.

The development of the app will kick off with an the initial workshop where we share ideas and visions for the project, after which we will all start researching and collecting tools to document in the app.

As I said earlier, focus then will be on creating an early prototype, with open source app frameworks, that can be tested by the whole team. We will prioritise the three most important improvements, and work on them until the next iteration of user testing and development. The process will be repeated three times, while we will also integrate a shiny user interface and a user friendly back-end for adding content. After that, we will be ready to launch the app as a web interface and eventually an Android and iPhone app!

I am very much looking forward to this workshop, as an opportunity to combine experiences from Sweden and the Spanish and international community, and to find ways of networking and collaborating on an international scale.

Modular and responsive design for Doctors Without Borders

This is a recap of a talk by Petter Joelson at Rabash’s Design Salon on February 19, 2015.

My agency Rabash was hired in 2014 to start redesigning Doctors Without Borders (Médecins Sans Frontières, MSF) Sweden’s website. The mission was to make the navigation intuitive, especially on smaller screens; optimise the donation interactions and enable moderators to create flexible campaign pages.

After the initial concept phase, I chose to start working on an early responsive prototype in html. Step by step, the prototype evolved to be equivalent to a full website. It might seem like a complicated process to make such vast prototypes in html, but I have learnt some tricks to make it quite easy. I have also seen three major advantages in this way of working, that I will walk you through one by one.

1. Responsive

Show the client how the website will look and behave.

Since responsive design came around a few years ago, I have worked according to the Mobile First-principle, and started the design process with wireframes for mobile screens. It is often an illustrative way of showing the client which priorities they have to make for the website to be easy to navigate. But it started to feel more and more impractical to show mockups of a page that does not look like the end result at all and can not be tested in its ”natural environment” which is the browser on a phone, tablet or desktop. This makes it unnecessary hard for the client, and even me as a designer, to envision the functionality and look of the final product.

Having to write complicated code just to show a quick idea for a client would not work for me. My first criteria for prototyping was that it should involve as little coding as possible. And even as front end development has become more and more specialised and complicated over the years, there are now more and more easy to use frameworks for building websites and other digital products.

A couple of years ago I started to experiment with simple prototypes in html. In the beginning it was just static pages built with Bootstrap. When I got the hang of it, I realised that it was actually as quick as drawing page by page in a wireframe app. For example: if I changed the height of an element at the top of the page, I did not have to move every other element; if I wanted to change the size of all headlines, I only had to do it once.

Now I use a combination of Bootstrap and Jekyll, with a few minor plugins that I install with Bower.

2. Modular

Give clients a custom design system with which they can modify, extend, and grow with into the future.

Brad Frost

A few years back, it was a really big deal when you every three to five years launched a new website. After the launch the sites became more and more out of date, until you did a complete redesign again. Most people understand now that their website has to be a living thing that evolves over time, in small adjustments, to stay relevant to users.

So how do we adapt to this workflow in the design process? Brad Frost advocates a method that he calls Atomic Design. He breaks down the design into smaller components to be able to present the client with a comprehensive design system, not just mockups for specific pages. Frost uses five levels for his design system:

  • Atoms: A single button or headline
  • Molecules: A search field with button and textfield; A byline for an article
  • Organisms: A campaign area, menu or list of news
  • Templates: The page template for news articles
  • Pages: Complete pages like About or Blog

To showcase the design system, Frost has developed something he calls Pattern Lab, that provides a kind of responsive style guide, documenting all parts of the website.

Inspired by Frost’s Pattern Lab, I developed a documentation for the different components of the website for Doctors Without Borders. It made it easier to explain to our AD which components needed graphic design, and the structure of the website became clearer for our developers.

For a vast project like this, it also made the whole workflow run smoother, as I could get an approval from the client for specific components, before the whole page template was done.

3. Content first

Separate content and presentation

A challenge with the new design was making huge amounts of information accessible on small screens. To achieve that, I needed to start with the content, and not make the mistake of building a perfect website, that get gets ”ruined” when the actual content is added.

The advantage of working with a system like Jekyll is that you can make a complete separation of design and content. The content files, using Markdown, are super simple text files that only defines the content, fields and template to use, nothing more.

That enables me to be able to work separately with the content, let a copy writer or the client go through the texts during the prototyping phase, and avoid surprises in later stages.

The prototype for Doctors Without Borders is nearly a complete version of the website, as I define templates in Jekyll and then only need to add ”raw” content.

From the prototype, I was able to generate a documentation page, that lists entry pages, types of articles, components and menu items.

To be able to make this separation of content and design is extremely valuable for responsive design. When the next gadget with a browser arrives (glasses, watches and so on), you will have the content files ready and can focus only on designing the presentation.

Next step: Integrating design and development

During this process, the prototyping has evolved parallell with the graphic design and the development of the final website. My aim for future projects is to better be able to integrate these processes, and be able to create both design and functionality in an iterative way and in dialoge with the client. When the CMSes become easier to work with, and the software for graphic design are better suited for responsive web it will of course get easier. But until then we need to experiment with ways of making the transitions between design and functionality as seamless as possible.