{"id":4140,"date":"2015-05-17T12:23:37","date_gmt":"2015-05-17T16:23:37","guid":{"rendered":"http:\/\/www.easterbrook.ca\/steve\/?p=4140"},"modified":"2015-05-17T12:23:37","modified_gmt":"2015-05-17T16:23:37","slug":"the-karlskrona-manifesto-on-sustainability-design","status":"publish","type":"post","link":"http:\/\/www.easterbrook.ca\/steve\/2015\/05\/the-karlskrona-manifesto-on-sustainability-design\/","title":{"rendered":"The Karlskrona Manifesto on Sustainability Design"},"content":{"rendered":"

I’m heading off to Florence this week for the International Conference on Software Engineering<\/a> (ICSE). The highlight of the week will be a panel session<\/a> I’m chairing, on the Karlskrona Manifesto. The manifesto itself is something we’ve been working on since last summer – a group of us\u00a0wrote the first draft at the Requirements Engineering conference in Karlskrona, Sweden, last summer (hence the name). This week we’re launching a website for the manifesto<\/a>, and we’ve published\u00a0a longer technical paper<\/a> about it at ICSE.<\/p>\n

The idea of the manifesto is to inspire deeper analysis of the\u00a0roles and responsibilities of technology designers\u00a0(and especially software designers), given that\u00a0software systems now shape so much of modern life. We rarely stop to think about the unintended consequences of very large numbers of people using our\u00a0technologies, nor do we\u00a0ask whether, on balance, an idea that looks cool on paper will\u00a0merely help\u00a0push us even further into unsustainable behaviours. The position we take in the manifesto is that, as designers, our responsibility for the consequences of our designs are much broader than most of us acknowledge, and it’s time to do something about it.<\/p>\n

For the manifesto, we ended up thinking about sustainability in terms of five dimensions:<\/p>\n