Signatories

What does it mean to sign the Karlskrona Manifesto?

The Karlskrona manifesto is a call for conversation. Signing it means that you agree that sustainability should be taken into consideration during system design and that there is a need for discussion on the topic. It does not necessarily means that you agree with every statement of the manifesto. If you wish to help us improve it, please leave your critiques, ideas and suggestions when signing it. Thank you!

I Support the Karlskrona Manifesto!

Manifesto Signatories v1.00

Karlskrona Manifesto v1.00

Introduction
As software practitioners and researchers, we are part of the group of people who design the software systems that run our world. Our work has made us increasingly aware of the impact of these systems and the responsibility that comes with our role, at a time when information and communication technologies are shaping the future. We struggle to reconcile our concern for planet Earth and its societies with the work that we do. Through this work we have come to understand that we need to redefine the narrative on sustainability and the role it plays in our profession.

What is sustainability, really? We often define it too narrowly. Sustainability is at its heart a systemic concept and has to be understood on a set of dimensions, including social, individual, environmental, economic, and technical.¹

Sustainability is fundamental to our society. The current state of our world is unsustainable in more ways that we often recognize. Technology is part of the dilemma and part of possible responses. We often talk about the immediate impact of technology, but rarely acknowledge its indirect and systemic effects. These effects play out across all dimensions of sustainability over the short, medium and long term.

Software in particular plays a central role in sustainability. It can push us towards growing consumption of resources, growing inequality in society, and lack of individual self- worth. But it can also create communities and enable thriving of individual freedom, democratic processes, and resource conservation. As designers of software technology, we are responsible for the long-term consequences of our designs. Design is the process of understanding the world and articulating an alternative conception on how it should be shaped, according to the designer’s intentions. Through design, we cause change and shape our environment. If we don’t take sustainability into account when designing, no matter in which domain and for what purpose, we miss the opportunity to cause positive change.

We recognize that there is a rapidly increasing awareness of the fundamental need and desire for a more sustainable world, and a lot of genuine desire and goodwill – but this alone can be ineffective unless we come to understand that:

There is a narrow perception of sustainability that frames it as protecting the environment or being able to maintain a business activity.

Whereas as a systemic property, sustainability does not apply simply to the system we are designing, but most importantly to the environmental, economic, individual, technical and social contexts of that system, and the relationships between them.

There is a perception that sustainability is a distinct discipline of research and practice with a few defined connections to software.

Whereas sustainability is a pervasive concern that translates into discipline- specific questions in each area it applies.

There is a perception that sustainability is a problem that can be solved, and that our aim is to find the ‘one thing‘ that will save the world.

Whereas it is a ‘wicked problem‘ – a dilemma to respond to intelligently and learn in the process of doing so; a challenge to be addressed, not a problem to be solved.

There is a perception that there is a tradeoff to be made between present needs and future needs, reinforced by a common definition of sustainable development, and hence that sustainability requires sacrifices in the present for the sake of future generations.

Whereas it is possible to prosper on this planet while simultaneously improving the prospects for prosperity of future generations.

There is a tendency to focus on the immediate impacts of any new technology, in terms of its functionality and how it is used.

Whereas the following orders of effects have to be distinguished: Direct, first order effects are the immediate opportunities and effects created by the physical existence of software technology and the processes involved in its design and production. Indirect, second order effects are the opportunities and effects arising from the application and usage of software. Systemic, third order effects, finally, are the effects and opportunities that are caused by wide-scale use of software systems over time.

There is a tendency to overly discount the future. The far future is discounted so much that it is considered for free (or worthless). Discount rates mean that long-term impacts matter far less than current costs and benefits.

Whereas the consequences of our actions play out over multiple timescales, and the cumulative impacts may be irreversible.

There is a tendency to think that taking small steps towards sustainability is sufficient, appropriate, and acceptable.

Whereas incremental approaches can end up reinforcing existing behaviours and lure us into a false sense of security. However, current society is so far from sustainability that deeper transformative changes are needed.

There is a tendency to treat sustainability as a desirable quality of the system that should be considered once other priorities have been established.

Whereas is not in competition with a specific set of quality attributes against which it has to be balanced – it is a fundamental precondition for the continued existence of the system and influences many of the goals to be considered in systems design.

There is a desire to identify a distinct completion point to a given project, so success can be measured at that point, with respect to pre-ordained criteria.

Whereas measuring success at one point in time fails to capture the effects that play out over multiple timescales, and so tells us nothing about long-term success. Criteria for success change over time as we experience those impacts.

There is a narrow conception of the roles of system designers, developers, users, owners, and regulators and their responsibilities, and there is a lack of agency of these actors in how they can fulfill these responsibilities.

Whereas sustainability imposes a distinct responsibility on each one of us, and that responsibility comes with a right to know the system design and its status, so that each participant is able to influence the outcome of the technology application in both design and use.

There is a tendency to interpret the codes of ethics for software professionals narrowly to refer to avoiding immediate harm to individuals and property.

Whereas it is our responsibility to address the potential harm from the 2nd and 3rd-order effects of the systems we design as part of our design process, even if these are not readily quantifiable.

As a result, even though the importance of sustainability is increasingly recognized, many software systems are unsustainable, and the broader impacts of most software systems on sustainability are unknown.

Thus, we propose the following initial set of principles and commitments:
Sustainability is systemic. Sustainability is never an isolated property. Systems thinking has to be the starting point for the transdisciplinary common ground of sustainability.

Sustainability has multiple dimensions. We have to include those dimensions into our analysis if we are to understand the nature of sustainability in any given situation.

Sustainability transcends multiple disciplines. Working in sustainability means working with people from across many disciplines, addressing the challenges from multiple perspectives.

Sustainability is a concern independent of the purpose of the system. Sustainability has to be considered even if the primary focus of the system under design is not sustainability.

Sustainability applies to both a system and its wider contexts. There are at least two spheres to consider in system design: the sustainability of the system itself and how it affects sustainability of the wider system of which it will be part.

Sustainability requires action on multiple levels. Some interventions have more leverage on a system than others. Whenever we take action towards sustainability, we should consider opportunity costs: action at other levels may offer more effective forms of intervention.

System visibility is a necessary precondition and enabler for sustainability design. The status of the system and its context should be visible at different levels of abstraction and perspectives to enable participation and informed responsible choice.

Sustainability requires long-term thinking. We should assess benefits and impacts on multiple timescales, and include longer-term indicators in assessment and decisions.

It is possible to meet the needs of future generations without sacrificing the prosperity of the current generation. Innovation in sustainability can play out as decoupling present and future needs. By moving away from the language of conflict and the trade-off mindset, we can identify and enact choices that benefit both present and future.

Sustainability design in the context of software systems is the process of designing systems with sustainability as a primary concern, based on a commitment to these principles.

So what now? How do we start?
Each of the following stakeholders can do something right now to get started.

Software practitioners: Try to identify effects of your project on technical, economic, environmental sustainability. Start asking questions about how to incorporate the principles into daily practice. Think about the social and individual dimensions. Talk about it with your colleagues.

Researchers: Identify one research question in your field that can help us to better understand sustainability design. Discuss it with your peers and think about how sustainability impacts your research area.

Professional associations: Revise code of ethics and practice to incorporate principles and explicitly acknowledge the need to consider sustainability as part of professional practice.

Educators: Integrate sustainability design in curricula for software engineering and other disciplines and articulate competencies required for successful sustainability design.

Customers: Put the concern on the table. Demand it in the next project.

Users: Demand that the products you use demonstrate that their designers have considered all dimensions of sustainability.

The undersigned,
Christoph Becker, University of Toronto & Vienna University of Technology
Ruzanna Chitchyan, University of Leicester
Leticia Duboc, State University of Rio de Janeiro
Steve Easterbrook, University of Toronto
Martin Mahaux, University of Namur
Birgit Penzenstadler, California State University Long Beach
Guillermo Rodriguez-Navas, Malardalen University
Camille Salinesi, Universite Paris 1
Norbert Seyff, University of Zurich
Colin C. Venters, University of Huddersfield
Coral Calero, University of Castilla-La Mancha
Sedef Akinli Kocak, Ryerson University
Stefanie Betz, Karlsruhe Institute of Technology

**your signature**

Share your support:

   


Manifesto Signatories
249 Gibrail Islam United Kingdom University of Glasgow Oct 05, 2022
248 Rahul Mohanani Finland University of Jyväskylä Oct 03, 2022
247 Konrad Plucinski Poland WIT Foundation Sep 29, 2022
246 Tapajit Dey Ireland Lero, University of Limerick Sep 23, 2022
245 Anh Nguyen Duc Norway University of South Eastern Norway Sep 21, 2022
244 Simen Sommerfeldt Norway Bouvet Aug 30, 2022
243 Ana Carolina Moises de Souza Norway NTNU: Norwegian University of Science and Technology Aug 10, 2022
242 Matheus Andrade Brazil Federal University of Bahia Aug 03, 2022
241 Mateja Blazek Slovenia University of Maribor, Faculty of Organizational Sciences Jun 08, 2022
240 Antonio Lucas Soares Portugal University of Porto - Faculty of Engineering and INESCTEC May 31, 2022
239 Kui Hao Singapore BrightV Consulting Pte Ltd May 28, 2022
238 Šemso Hrnjičić Slovenia Univerza v Mariboru May 04, 2022
237 Sher Badshah Canada Dalhousie University May 04, 2022
236 Alenka Baggia Slovenia University of Maribor, Faculty of Organizational Sciences Apr 20, 2022
235 Tom Moran Netherlands Aspire Institute Netherlands Apr 20, 2022
234 LINO CIPRIANO MENDONCA Portugal ipg Apr 12, 2022
233 Vagner Bom Jesus Sao Tome and Principe Investigator Apr 08, 2022
232 Ivan Machado Brazil Federal University of Bahia Mar 26, 2022
231 Janis Hernandez Canada DocuPoint Mar 20, 2022
230 Aiko Frank Deutschland IT Consultant Feb 20, 2022
229 Ehsan Ahmad Saudi Arabia Saudi Electronic University Feb 12, 2022
228 Rajnish Nigam India Service Lee Technology Pvt Ltd. Feb 08, 2022
227 Emre Cebeci Turkey Karadeniz Technical University Feb 06, 2022
226 JuanAntonio Nelson United States Jan 31, 2022
225 Mahei Manhai Li Deutschland University of Kassel Jan 20, 2022
224 Elvira Qvist Sweden Jan 19, 2022
223 Rekha Kodali India accenture Jan 18, 2022
222 Urooj Fatima Norway Norwegian University of Science and Technology (NTNU) Dec 22, 2021
221 Sami Kabir Bangladesh Lulea University of Technology (LTU), Skelleftea, Sweden Dec 20, 2021
220 Md Abu Ahammed Babu Bangladesh Lulea University of Technology Dec 13, 2021
219 Angelo Vasquez Spain Universidad la salle Nov 27, 2021
218 Gillian Cartar Canada Gillian Cartar Nov 17, 2021
217 Shamina Vastani Canada University of Toronto Nov 05, 2021
216 Benno Schmidt Germany Bochum University of Applied Sciences Nov 04, 2021
215 Simen Sommerfeldt Norway Bouvet AS Oct 18, 2021
214 Theresia Ratih Dewi Saputri Indonesia Universitas Ciputra Surabaya Oct 12, 2021
213 Jean-Pascal Boignard France Agile Boarding Oct 10, 2021
212 Ulviyya Mustafayeva Finland LUT University Oct 09, 2021
211 wahab Hamidu Ghana Stanbic Bank Ghana Limited Sep 19, 2021
210 Shanti Hadioetomo Canada Sep 10, 2021
209 Chiara Milanese Italy Student and web designer Aug 24, 2021
208 Alexandre Uchoa Brazil RNP Aug 18, 2021
207 Eduardo Marinho Mascarenhas Brazil Universidade de Pernambuco Jul 26, 2021
206 Tjerja Geerts Netherlands Nyomentum - Business Innovation Design Jul 04, 2021
205 Erik Lundqvist Sweden Cybercom Group Jun 17, 2021
204 Michael Wohlmuther Austria May 25, 2021
203 christophe PHAM France INFOGREEN FACTORY May 20, 2021
202 Gerhard Sprung Austria May 17, 2021
201 Lucien Jaegers Netherlands Philips May 15, 2021
200 Mete Yazici Japan Commoncolors G.K. May 05, 2021