Co-design refers to collaborations in which several stakeholders actively join forces to tackle a shared challenge. Participating stakeholders can belong to any sector of society, such as civil society, industry, government or academia. The engagement of these four major sectors is commonly referred to as the ‘quadruple helix model’.
The Cos4Cloud project uses co-design methodologies for prototyping the services from the bottom up, with the quadruple helix, to allow for customization at all required phases. Our main goal is to align mutual interests to tackle the technological challenges of citizen science by organizing face-to-face workshops, online interactions and testing the services among all end-users involved. As a result of the co-designing methodology, Cos4Cloud will improve the functional specification of the services.
The coordinator of the co-design Work Package is Science for Change. The co-designed phases will follow the scheme shown below:
Improve citizen science technologies by giving your opinion on the specific technological services that we are developing, and, of course, have a nice time chatting with a diverse group of people about citizen science.
Aimed to: environmental / biodiversity experts, developers, developers from citizen observatories, university professors, environmental students or professors.
Dates: Worshop for MOBIS service: March 10 / Workshop for Cos4Bio & Cos4Env: March 11
Identify the issues
Issues and needs identified in a specific Citizen Observatory (CO) for service co-design.
Technology Mapping
Exploration of existing platforms from a technological point of view, TRL status and gradient.
Stakeholders Mapping
Mapping the various stakeholders who will participate in co-designing specific services.
Frame (the need/ problem)
Set goals and analyse challenges to better frame the problem, involving key stakeholders.
Service development
In this phase, the service will be co-designed using the Agile Methodology.
Deployment and testing
At this stage, the new, co-designed service will be put in place to get further feedback from users.
Final service co-designed
At this stage, the service will be co-designed, already in place and at the desired TRL (target TRL 8/9).
