Showing posts with label public policy. Show all posts
Showing posts with label public policy. Show all posts

Monday, November 19, 2012

Design and design thinking in public services


Design Commission Inquiry into Redesigning Public Services
Evidence from Lucy Kimbell
Session 11.10.2012

This is an edited version of the comments I made giving evidence to the Design Commission Inquiry into Redesigning Public Services taking place over the past few months, led by Policy Connect and its Associate Parliamentary Design and Innovation Group. This has involved many people from a wide range of backgrounds giving evidence about the role of design and design thinking in public services to the expert steering group. The Social Design Talks series I co-organise with Jocelyn Bailey of Policy Connect and Guy Julier of the Victoria and Albert Museum/University of Brighton is also feeding in to this process.


Lucy Kimbell: This is quite academic so I apologise but I do think it’s useful… I’ve made some notes to organise my thoughts and they’re in three broad categories. The first: what is design? What is that word doing? And for who? Secondly, is design thinking changing that in some way – in terms of how, operationally, you can embed design in organisations… and then thirdly design as a professional field and its weak institutional base and why, even though design people think we know how to sort these things out, we somehow don’t have the institutional power to be in there straight away – we have to make the case constantly.

One of the first things to address is that even if you’re in design, it’s incredibly hard to define what design is. Do we mean design in the mode of engineering, do we mean architecture, do we mean communications design, do we mean digital interactions? And even if you look at the academic literature on design, there are two major distinctions, which then come out – is design about giving shape and form to things? And that thing could be a physical product or it could be a digital interaction. Or is it about making change happen? 

The important definition here is from Herbert Simon, from 1969: everyone who devises courses of action, to change existing situations into preferred ones, is doing design. Anybody who is trying to change anything into a preferred situation is basically doing design. And that is not about giving shape and form, making stuff. That is a massive tension that comes up again and again in these discussions.

Then that stuff around changing behaviours and interactions and services and systems is much more palatable when you look through that second lens. But that tension is incredibly strong – this is not trivial, that design is really hard to define.

Let’s turn to a third definition, which takes that Herbert Simon idea, and pushes it a little bit further…
In Herbert Simon’s book, The Sciences of the Artificial, 1969 – he won the Nobel prize for economics – he did a lot of work in computer software and artificial intelligence, and he came out thinking the thing that we’re all doing is actually design. That quote I just gave is the most famous quote from it. But it’s part of a much longer chunk which then goes on to say, in essence management, medicine and engineering are all design professions. And if you say that to a doctor they think ‘well I diagnose and then I’m trying to change the state of the patient – which has a physical effect – so yes’. But then you have this problem which some designers go into of saying actually ‘design is everything’. If you push it that far you are saying design is everything, and therefore designers can tackle anything. Which is not necessarily the case. So that definition on the one hand seems right, but it also alludes to this question about design and management – are they really different? Management is about supporting people to do whatever they want to do better – which might be citizens, or might be customers buying an airline ticket…

Armand Hatchuel is a professor from the Ecole des Mines in Paris – which is an engineering school, but he basically writes in management theory – and he is the most interesting and profound person writing in design theory in the last 10-20 years. He revisits Herbert Simon and says ‘Simon was absolutely right, design is critical for organisations and mostly ignored.’ He then presents two situations. You’ve got a group of people who want to go out on Saturday night. They decide they want to go to the cinema – they’re going to ‘design’ their Saturday night. Going to the cinema is basically choice selection. You’ve got a these films on in these cinemas, how do we choose? But we know what the end result is. We don’t know how good the film will be, but it’s a defined problem. That is choice. Making choices.

Actually, what design is: the example he gives is designing a party. It’s the same group of friends, on a Saturday night – not going to the cinema, they’re going to design a party. What’s a party? It could be any number of things. It could be ten people, or a hundred people, it could be with dancing, it could be with food. It’s an unknown – the outcome isn’t yet defined. And that (although he has a much more theoretical version of it, actually quite readable) that is what design is: it’s about expanding the set of options. Not about selecting between options.

Herbert Simon, although he is saying design is important, actually means selecting between options. Whereas design is about the creation of new options. So it is about creativity and generativity.
A limited number of people actually read Armand Hatchuel – even if you’re in management – but design theory people mostly don’t read him. So while this is theoretical stuff, it points to these problems that most of us on the ground have in conversation with a client, which is about ‘what actually are you doing?’ Are you designing a physical thingy, or are you helping us change how we engage with citizens? Which is a change process, which is then a different thing, and necessarily involves ‘the organisation’, which most designers are terrible at doing. They don’t know how to do that: it’s not their training. Some of them might have ended up being good at that, at working with people and facilitation, but they don’t have the analytical skills for doing stuff inside organisations. And unlike for products, when organisations are designing services, the consumption and production is happening at the same time. The organisation is the entity that is the service: it is just a load of interactions with digital and physical things, and with people.

This raises a lot more questions which, quite frankly, for me, are not answered right now. But it comes back to this definition: what is design about? And in reality you’ve got both of those things – you do want the webpage to be well designed, and the leaflet, and the interaction with your Citizens Advice advisors – the person-to-person face time stuff. Those all do require designing. But does it mean that designers are necessarily good at that? That’s one of the reasons why this is so hard: and it is really hard. It is not as though academics – those of us who read and write about this stuff – are in agreement about what is the core of design.

A simpler version of this is – if you look at the dictionary definition, there is the verb and the noun. When you’re talking about the ‘design of a service’, there’s the noun: the actual finished arrangement of the service. And then there are blueprints and artefacts along the way, which are designs towards the final design. Then there’s the process of ‘doing designing’, and then there’s the field as a profession. So that’s four different potential meanings for the word design. And if we’re talking with a local authority manager who is buying design: what are they buying? Which of those four things? And again, what does a person who calls themselves a designer, who maybe went to CSM and did web design and is now peddling service design: what is it that they are offering? Are they good at all those things? I’ll come to this again later – how we know what to go on.

So, another thing then from within the management perspective…  I have read a lot of the management literature, I teach design on an MBA, where I am confronted with making a space for this design stuff, but  there is a sense that all my other colleagues are asking ‘well what are you adding? We already teach that.’ ‘What do you mean by design?’ always comes out. Hence I’ve bothered to read all this literature and get clearer for myself. But for them, it’s two things. Really it’s a phase in new product development. Design is not the same as new product development. It is a phase in new product and service development. There’s your first ‘research and discovery’ – what you’re trying to do, your aims and objectives. Then your engagement with the detail of the users etc, the analysis of what they want, and segmentation. And then there’s design, and then there is prototyping and roll-out. So design is a phase. If you look at management literature design is a phase. But for example, what the Design Council are saying is, as designers we own product development. We can do that whole arc. And maybe some do, really well, but actually in most organisations that I’ve come across, ‘a manager’ does that whole arc. A product manager, with a management training, or a project manager, is responsible for that whole arc – and the design bit is a bit in the middle. But designers want to take over the whole thing. And some do incredibly well at that.

But there is a tension there again about what that word ‘design’ is doing.

Thomas Kohut: So would a design manager say ‘well I can do that whole thing?’

Lucy: No it’s worse than that, some designers think they can do the whole thing. They can elicit what the users want or should have or could have, analyse that, interpret that, engage with stakeholders, articulate the requirements, visualise, prototype, idea generate, blah blah blah – through to then someone delivering it. So a designer will try and do that. My observation about organisations I’ve worked with, which range from Deutsche Bank to Vodafone – there are few people called ‘design managers’. They exist in the Design Council’s universe. They barely exist in most organisations unless they’re very product centric.

Julian Grice: Well they’re certainly not service innovation people… And of course (and I agree with everything you’re talking about), as a designer you always stray to the very front of the argument – because actually it’s all about the user. And sometimes there will be some insight that modifies ‘this plan for that particular service’.

Lucy: But the designer doesn’t own it. They own it. And this is one of the things I’ve learned from teaching MBAs. I used to teach at the Royal College – I used to teach designers who were utterly brilliant, but at the end of the day when I started teaching MBAs I thought ‘oh this is so much more fun’. Because these are the people who own the project. They hire a designer to help them with this whole arc. And the venture and the opportunity and all of that. They scope that, and then they write the brief, which a good designer will probably then turn into a different brief, and do that front end work. But the management people own the design. Not the designer.

Carol Moonlight: What we’ve seen – and maybe a parallel shift is needed. What we’ve seen in the online world, is the IT people, the techie people own it, which is invariably a bad idea. They should be called on as consultants, and give their expertise as appropriate, but they shouldn’t own the end to end process.

Lucy: So that’s why this is actually about management, not about design. It’s about who owns that thing. And that comes back to the Herbert Simon definition – it’s about change. It’s about the shift online, or the changing relationship with users, or saving money by getting citizens to cut costs by doing whatever it is. Those set of aims at the beginning of a project – which generally designers are not involved in – are formulated around policy and organisational goals. So the design of public services is actually a management question, not a design question. But there are then opportunities for designers, design thinking, to play into that, because those managers rarely come from that background.

Jocelyn Bailey: You might be about to come on to this, but how is it then that the design profession has ended up positioning itself entirely outside of that process?

Lucy: Exactly! So if most managers think that they are designing a service – and I work with people who are designing a service – I’m currently working with the Metropolitan Services Trust, a housing provider and particularly offering services for older people… They are designing the service. I’m not designing it. They just hired in The Young Foundation, and my team to do a little tiny bit of work – they are definitely designing it. We’re just helping them with a few gaps where I’ve said ‘I can help you here… and I think you should do this…’ and they said ok. But they are designing it.
So the design response to the fact that actually managers own all of this, whatever they are technically called in an organisation, is to say either: ‘we can do the whole arc for you… give us everything and we can do that. We’ve got this thing called “design thinking” that you can’t do. You think you know your users – well we can know them better. We’ve got some special methods, we’ve got some special participatory ways of eliciting more deeply what they want. You’ll sit them in a room in a focus group and ask them, we’ll go study them. So we’ve got methods ’. Which I am going to come to shortly.

And the other design response – like from the Design Council’s work – is about trying to quantify ‘our impact is “this”. If you hire us you’ll get a better design’ – which is incredibly hard to measure. And I would say, having read a lot of the literature, most of those attempts to define the value of design, aren’t very good. Yet. And as you know the Design Council and the AHRC are commissioning some work on that. It’s not easy to measure… to get clear comparative studies. And most design consultants want them. They want to be able to say ‘I did this, if we hadn’t involved ourselves… the impact of us on your project was this, this and this.’ But it’s very hard to get that… And we’re in this culture where you have to have statistics, and maybe some qualitative evidence… So that’s one of the responses as well, is to say ‘let’s get some really good data to prove that we’re really great’.

One response is to say ‘we’ve got this magical design thinking’, the other is to say ‘we’ll get you better data’. And then the third, which I think is more tricky but more interesting is to reconstitute the problem itself – to say ‘this isn’t even the right question’. And just to do stuff, in a completely different context, which then reframes what the question should be. An example for me would be My Society – they’re not necessarily designers, although they’ve got some designers in there – where they just say ‘we’re just going to go and do it over here’. Which then changes the nature of the debate. They don’t ask the DWP to hire them as consultants, they just go and do it because something should exist, and they believe that’s the way it should be done.

Returning to the Herbert Simon definition of ‘making change’… they’re making an artefact. A different artefact, over here, that is great – and then it forces other people to realise they can’t do it themselves. ’We would never have asked for that, we would never have written the brief, but oh look it does all this other stuff and it changes how the conversation happens.’

Carol: Just returning to outcomes… Evidencing that is expensive – longitudinal studies are expensive. Very rarely do we get the money to do it.

Lucy: There are potential ways around that though. If we’re in a culture where we need to have better research about outcomes… universities for example are really good at research. They would be the potential organisations you could work with…

Julian: Whilst designers always complain about the brief never being right – it’s the collaboration in that arc that is important. And designers will always bleat on about the fact that they do have voice, amongst a number of other voices that is worth listening to, before you present them with their phase. Consumer brands are better at that than public services, broadly.

Lucy: You’re also battling against professional culture. But to get on to the design profession… the third thing I wanted to say is then, is the design profession – meaning the people who went to design school of some kind, call themselves a designer (not a manager), think about this stuff a lot – what is it that that profession is doing right now.

And one of the important things is that, unlike engineers and unlike architects, those other kinds of designers are not a chartered profession. They are not strong institutionally. They weren’t founded in the 1880s, they don’t have a Royal Charter, they don’t have a guiding professional body. They don’t have strong rules about who is in and who is out, and what happens if you fail. You can’t get sued in the same way – you’re probably not going to kill anybody from your bad design (whereas you might if you are an engineer and your building falls down). So then the boundary work – that managing of who is in and who is out is done by those institutions. In the sort of design worlds that we’re in – anyone is in. Anyone could call themselves a designer tomorrow – print a card saying user interaction designer – and then everyone would say, ‘oh, really?’ It’s a culture, it’s not institutionally strong…

And that matters because it’s about the ability to speak to power, and make claims about your authority and your professional expertise. So I would say design, meaning not engineering or architecture, which of course are diverse design fields anyway and design is a multitude of fields, obviously… But it’s institutionally weak. It’s got a poor academic knowledge base. It’s got utterly brilliant practitioners, but they are mostly working in very small firms, with good interpersonal links and so on, but there is not a strong knowledge network, and ways of recognising what is good knowledge, and what isn’t. And maybe that was fine for product design or graphic design or communications, maybe that was fine… But it’s really not ok for this context. For talking to government.

So there are some people who are trying to now create a stronger charter for design – but they’re about 150 years too late in creating that institution.

Jocelyn: Who is doing that?

Lucy: I think James Moultrie is involved. And a design lecturer at Nottingham Trent. Anyway so there is a bunch of people on the back of the same analysis saying ‘right we’re going to try and make that thing’ – whether that works in the current environment, where professions don’t have the same value as in the 1850s… It’s a different thing. Though we are all professionals flogging our skills and knowledge to other providers.

Julian: There is a huge irony in all of that designers are schizophrenic on their own topic: they desperately want credibility and authority and voice… but on the other hand they love fragmentation, divergence – and they can’t possibly agree.

Thomas: And they are in business and making money without it. You can see they would question the need for a professional body.

Julian: Well they all say that they do. But the reality is convincing them they are all part of the same thing has been challenging. What you need, is a crisis. A crisis in the design sector which creates a complete lack of credibility…

Lucy: Yes. Some really terrible things happening from bad design. If buildings falling down did that over some decades for architecture… death and destruction is one kind of crisis. So what is the same thing for design…? I’m not sure it’s going to play out in that way. And the other interesting parallel is that management consultants don’t have that, and they do just fine. They peddle recipes and methods, they peddle professional knowledge – they don’t have authorising bodies either, so maybe it’s not required. But they have numbers. They have different modes of operating as well.

So those are some questions for the field – for the multitude of professions. For me it’s not surprising that this is incredibly complex  stuff and difficult for government departments to buy, because they don’t know what design is – because no-one else does – they don’t see professional authority, and competence that is validated in ways they understand…

And then we come to design thinking – one of the other things that’s being peddled. I think that’s been an interesting development. And when I think about what characterises a designerly approach (so this refers to people from the culture of design, who studied design, work in design consultancies, care about user experience and what things look like – as one symptom of their behaviour) I think there are three or four different characteristics. These vaguely map onto design thinking, but I have a particular take on that which we could later get into…

So one is the focus on – not human-centredness, I don’t think that’s the right term – but human scale. Focussing on experiences and capacities of users, which is very much the case in the citizen space, in a social and material world. One of the problems when that language of ‘human-centred’ gets adopted by these manager-types – they are just adopting marketing speak. They say they know they need their services to be citizen centred. I’ve already read lots of documents that say ‘our services will be citizen centred’. But they don’t know what it means. They can’t operationally do it. They are not of the culture which really profoundly attends to human experiences at human scale  and pays attention to the artefacts. Designers do pay attention to the artefacts within the social world. Most managers think the artefacts are something you do later once you’ve worked out the strategy. The artefacts come later (unless they’re within some aspects of operations management). So that is something that does distinguish the designerly approach: it’s at the human scale. It’s not the macro picture, it’s actually this quite small ‘what are we doing in this room right now, what are the objects, what are the human interactions?’

And I’m not saying that other people don’t do it. This is one of my problems with design thinking – when you look closely at these things – although you could say designers in this culture do do those things, it doesn’t mean others don’t. For example: the army really cares about ‘stuff’. Because if that goes wrong, in the middle of an invasion, then you’re f*****. And the same with Citizens Advice – if you get the forms and the bits of paper wrong then it doesn’t work. So there are other professions that do care about the interactions of the people and the stuff and the teams. But certainly designers do do that. And the probably care more about the crafting of those things, as a starting point.

Secondly: I would say designers are analytical – to do any design work, somebody has to do some analytical work (the segmenting of the users, etc – and working out which of the things they’ve moaned about are the ones that matter). But actually I think more profound from a designerly training/ background/ profession/ skill is the ability to synthesise by giving shape and form. So it’s ‘I’ve listened to everything you’ve said, now here is my sketch for that webpage and how it should be.’ The very rapid synthesis, not ‘let’s write a list of how it could be changed, and then write another list, and then have another five meetings’, but ‘here it is right now, on a piece of paper’. Which is not the same as making it visual. For me the emphasis is on the synthesising. The ability to say ‘I’ve heard what you’ve said and those interviews from those five users and now I’ve synthesised it’. That very fast, very quick work. And that is in the production of artefacts. In which the visual plays an important part. And a lot of designers will say it’s because they are visual – and that is part of it but more important for me is the synthesising ability.

A third thing is: coming back to Hatchuel – the generative and the creating. The creating of the new. And I think for cultural, psychological, cognitive, motivational – all sorts of complex reasons – some people are really good at generating ideas and some people are not. So I think those designers generally are good at having lots of ideas. And some of those managers sitting in DWP are not. They might have one idea, and then they really stick to it. Typically the studies of designers show they have a gazillion ideas, and they just keep having more and more. And there’s for them a sort of pleasure in having lots of ideas. And other people are not like that. So there is definitely something about generative creativity, which is celebrated and practiced in design culture. And rewarded.

And the fourth thing is an exploratory inquiry approach, which includes prototyping. It’s not that you have the right answer… You may get solution fixation, but you may also just keep throwing away your ideas from one day to the next. So it’s not just the generation – it’s the co-evolution of the problem and the solution (Nigel Cross in design theory writes about this). So it’s not a linear model, where you understand the problem, and you work towards a solution, which is the model in books. It’s more like a real life model – you have an understanding of the problem, you suggest a solution, and the insight that gives you makes you keep going back to re-evaluate the problem and find better solutions – you keep evolving the problem and solutions. This often gets translated as ‘iterative’. The fact that is it iterative is not the important thing, it’s the fact that you keep refining your understanding of what the issue is that you’re working with. Most organisations are not geared up to do that. They want to define a problem, sort out a solution, put some resources to it, and then make it go away. Again, it’s not only designers – entrepreneurs do this as well – but research shows it is certainly true of designers.

One other thing that is part of that exploratory approach is the assumption by designers that they don’t know best – they usefully don’t know. Their lack of expertise is generative for a project. The whole design approach is actually about continuous learning for the organisation. Now of course there are management things that are about continuous process improvement – which aren’t a million miles away. But they’re less fun/ messy – much more outcome-y – there is something culturally distinct about them, although there are overlaps.

If you look at design thinking and the people who write about it, you can see echoes of these things. This is just my formulation of some of the key distinguishing things. And so it comes back to the question of who has authority to do it. Other people may well recognise in their work, that they already do these things – so then it’s really hard for designers to claim that as their professional territory. Because if other people are already practicing these things – what is it that designers are contributing?
The only thing I can suggest is what I have observed from people who are not designers coming on my MBA course. And they choose it not really knowing what it is, and by the end of it they are better able to see the service world they’re in.

Through all of that stuff I’ve just given you the condensed version of, the students think about their world of work differently – they see themselves as being in a learning process, they pay more attention to the artefacts at human scale – they see that the touchpoints and the artefacts matter more than they thought. They are aware of what good design is, in a different way to before. That is achieved by a learning journey that is partly reading some theory, but also doing designing. And you could equally well do that with some senior civil servants. It has potential amazing effects. It’s not about a designer standing there telling them about a great web page.


Tuesday, October 30, 2012

Why a design dinner in Oxford in 2012?




On Thursday evening, around twenty people will gather for a dinner in Oxford. Curated by Phil Clare and Caroline Bucklow of the Knowledge Exchange and Impact Team in Research Services at the University of Oxford, and me (an associate fellow at Said Business School), this dinner aims to stage a new conversation about design within and around Oxford and its global and local networks.

In contrast with other design dinners, often associated with events such as the Salone furniture fair in Milan, this one is perhaps less glamorous, although we do include some internationally-renowned practitioners and academics among the guests. In contrast to many other Oxford dinners, we’ll be talking about a field of expertise and practice that perhaps curiously is not well-represented in the university, which has schools of engineering, computer science, business and fine art, but not industrial design, product design, communications design or architecture.

Guests include leading people from the design world, including from small, emerging studios, people working in established innovative consultancies and others from large corporations with an interest in design, as well as academics from different faculties and resources across Oxford University, as well as guests from Oxford Brookes University across the city. Although I haven’t checked – there are 800 years of archives to look through – this may be the first such dinner in the Oxford ecology. We think it’s timely for these reasons.

Firstly, the profession and practice of design are taking up a new place on the world stage. Borrowing a term from art history, we might see as designers working within an ‘expanded field’. There are numerous examples of designers and architects such as Josiah Wedgwood or Victor Papanek addressing the issues of their day. But what is striking about the last decade is how designers trained in design schools now see their role as contributing to global challenges such as educational standards, climate change, public service design, or humanitarian disasters. Examples are Project H, openideo.org and Participle.

Secondly, several academic fields have been exploring what a design-based approach can bring to research and teaching. For example in research, the Arts and Humanities Research Council and Design Council are scoping out a research programme in the design of services. Within management education, there are now several universities around the world (including Oxford) teaching “design thinking” – the application of designerly approaches and methods to solving “wicked” problems and stimulating innovation.

Thirdly, within business, developments such as the cloud, 3d printing, mobile broadband, and a focus on delivering services, experiences and interactions, has lead to designers and design-based approaches being brought in not just to make things look pretty, but develop and explore concepts from day 1. Examples here are Berg London, Samsung and Intel.

Fourthly, the London 2012 Olympics and other cultural events have highlighted the role of the symbolic in day-to-day life. Creating and staging collective experiences requires the design and production of places, artefacts and signs, and paying attention to the design of the social interactions in which meanings are created. These are all activities that are central to designerly practices.

The aims of our dinner are however more modest. We won’t necessarily discuss these issues. But we do hope that participants will enjoy having conversations about their work and hearing from others, within an institution that has a great deal of history but also is a site of critical thinking and innovation. We believe this will provoke new relationships and lines of enquiry that might lead to new projects.  The design of a dining experience seems a good way to start that.



Thursday, June 23, 2011

Five things people designing solutions to social problems should know

Designers are now working in a range of contexts that are quite different to what many of them were educated for. Some are designing public services, others work on humanitarian or development projects, others are creating social enterprises. Common to all these is an interest in social problems and the belief that designers’ ways of working – in particular “Design Thinking” – has special ways to solve them. We think designers have much to contribute to different kinds of community, but we suggest there are some important things they need to know.

1 Social problems don’t just exist “out there” waiting for socially-minded designers or social entrepreneurs to trip over. On the contrary, they are constructed by the interplay of individuals, organisations, things and what brings them all together. Designers should focus their attention as much on how they and others construct social problems rather than just working towards solving them.

2 Objects too can intentionally or otherwise spark a social problem into existence. Designers who have got busy designing “intangible” services rather than mundane things should be aware that their special knowledge about how to make stuff is of immense potential value in constructing problems as social problems.

3 Design Thinking and its optimistic process pushes designers ever onward in pursuit of a solution based on responding to stories of personal troubles. This might not be right for messy, intractable social issues. Designers should attend to the nuances of the social worlds they work in and consider what they are driving themselves towards, and who and what is shaping this and why.

4 Like any other actor in a social world, designers are able to interpret the world around them, and come up with ideas to change it. Those who look, uncritically, towards Design Thinking to answer the world¹s most wicked social problems are missing some important resources. We¹d encourage designers to draw on ideas and concepts from the social sciences - not just borrowing ethnography as a methodology but going deeper into understanding how social problems are constructed. For example concepts such as reflexivity can help designers become aware of how their own commitments shape how they understand what is going on and what they think they can change.

5 Unlike architects, engineers and many other professionals, designers do not have clear disciplinary boundaries, strong institutions or professional codes of ethics. Designers with ambitions to design solutions to social problems are working in dangerous territory and should develop credible tools to reflect on the nature of their work and its possible and actual impacts.


The provocations are drawn from “Design Thinking and the Big Society: From Solving Personal Troubles to Designing Social Problems” by Simon Blyth (Actant) and Lucy Kimbell (Taylor Haig).


Thanks to Cassie and Alex for pointing out the missing no.4.

Tuesday, March 08, 2011

Guest post: Derek Miller: Design Ethics for International Peace and Security

Intro
This is a guest post by Derek Miller, founder of the Policy Lab and senior fellow at the United Nations Institute for Disarmament Research (UNIDIR). The Policy Lab provides research and design services at the policy, organization, and field-levels to reduce barriers, create conditions, and design solutions for strategic engagement with local communities. It is the successor to the Security Needs Assessment Protocol (SNAP) project of the United Nations Institute for Disarmament Research in Geneva (2006-2010). The SNAP project was an innovation initiative to explore the potential for best process approaches to the design of local action on security matters by UN operational agencies. With Derek and his colleague Lisa Rudnick, and ethnographer Gerry Philipsen of the University of Washington, I co-organised a three-day conference on Strategic Design and Public Policy at Glen Cove, NY, in June 2010, the brought together specialists from design, policy and cultural research to explore the idea of bringing local knowledge to the design of local action in the context of security and disarmament.


Design Ethics for International Peace and Security
October 2010

Lecture delivered to the University of Gothenburg, Business and Design Lab, 6 October 20101
by Derek B. Miller

Thank you for coming today. I hate it when I’m booked into a large room and no one comes. I have to suffer the double indignity of talking to myself and then having my own words echoed back at me.

My thanks as well to professor Ulla Johansson, whom I met at a conference in Cleveland on the convergence of design and management.

I do want to discuss a topic that I believe is important. It is not a topic I have seen addressed in any great detail or with particular urgency, and yet the topic deserves both. If we to boil it down to just a phrase, I’d say the topic is design ethics, and my particular concern is better ensuring that the ever-closer relations that design is forming with public policy is informed by the necessary seriousness of mind required to achieve some real good in the world. Underlying that aspiration is also a concern. The concern is that failure to do so could mean that we actually cause a harm.

As designers look towards ever-new domains for social innovation, especially in public service, it would be wise to ensure that this aspiration towards social betterment is guided by the tutored consideration of our actions and their impact on others.
My perspective on design comes from outside the field looking inward. My vantage point for reflecting on design has been Security Needs Assessment Protocol project at the United Nations Institute for Disarmament Research in Geneva. Started in 2006, SNAP was an innovation initiative into the design of community-level peace and security projects and programmes by the United Nations. I designed and ran that programme with Lisa Rudnick.

SNAP was supported by the Swedish, Dutch and Norwegian foreign ministries and its purpose was conceptualize, design, and test new ways to A) generate local knowledge at the community level and B) turn it into a strategic asset in the design of local-level interventions. Our work was thematically concerned with community security — that is, attending to matters of violence — though the applicability of our work extends rather farther.

Recently, I’m pleased to say, the 22nd Biennial of Industrial Design (BIO 22) being held at the museum of Architecture and Design in Slovenia selected SNAP as one of the “good practice examples” in the field of Service and Information Design to recognize this innovation in bringing social research, design, and international peace and security closer together. I’d like to add that our introduction to the field of design was assisted by our colleagues at Live work in London and Oslo. This wasn’t a client relationship but rather, since 2008, has been an on-going conversation into the relationship between our professional domains. Our conversations with Lucy Kimbell at the Said Business School at Oxford further contributed to our induction into the profession of design. Those conversations continue.

The process of bringing together the professional domains of socio-cultural research, design, and international peace and security was a revealing exercise. And today, albeit briefly, I want to share a few things it revealed. The center of gravity for this discussion might be termed “responsible design.” The framework for considering responsible design is the topic of ethics.
To discuss this properly, I find it helpful to begin with a distinction. The distinction is between an ethos for doing good, and the ethics of doing good. An ethos is a general orientation, or set of guiding principles. It is like choosing a direction, like facing east rather than west.

Many designers today, especially the younger generation of designers, want to do some good in the world. They no longer seem satisfied simply creating objects of desire for profit. This is laudable. But for the good intentions of the design profession to actually result in some good, it is going to be necessary to carefully attend to how we design. Design is both a social process, with implications for others who are participants to that process, and also brings something new into the world that may have social force. Attending to both matters responsibly will be essential as the field moves forward.

This is especially true as design steps into the wider world of international peace and security — given that the issue here is not consumer value but life and death.

If an ethos is an orientation, then ethics is the set of rules we establish and enact to guide and judge to our actions.
There is some limited discussion about ethics in design, but in comparison to codes of conduct in, say, anthropology, architecture, and medicine, one would be forgiven for finding them undeveloped. Design ethics appears to be under-theorized, and under- codified given that design research is now crossing the borderline into social research, including ethnography, which involves research with or on human beings. It is worth recalling, for example, that since 1947 and the establishment of the Nuremberg Code, the voluntary consent of people to research has been treated as “absolutely essential” by many organizations. Though written in direct response to medical experimentation, design research is now stepping into a world, as mentioned, where the process of learning, and the outcomes of learning both have social implications. It is time to turn an eye towards the ethics of design research.

Perhaps even more importantly, design is also stepping into the area of social action, through such activities as social innovation, whereby the outcome of a design is a social change in the world. This invites a rather obvious question. What, exactly, is guiding your conduct? It is a profit motive that allows the market to regulate value? Or will you uncritically adopt the mandates and missions of the organizations that hire you? Will you trust your own inner voice to lead to you to proper conduct, or will you endeavor to determine what common ethical grounds can be created for cooperation? How will you do that?

We are not going to solve this today. But we can take some preliminary steps to map out the terrain that we are going to face. That terrain is conceptual. It is a place of ideas, and the relations between ideas that in turn guide our actions. Clarity is helpful in that regard. So let’s first try, for just a moment, to conceptualize and situate design in continuum between knowledge and action.

Close your eyes for a moment. Try to remember the world before Powerpoint. Imagine two circles beside one another. They do not touch. The circle on the left will be labeled knowledge. The circle on the right will be labeled action.
What is the relationship to be between knowledge and action? And where does design fit in that relationship both conceptually and procedurally?

In my field, of international peace and security, we can actually see the institutionalized distinction between knowledge and action. The university system and think tanks, policy centers, and research NGOs constitute the “knowledge sector.” They get money from governments to go generate knowledge and then bring that knowledge across the street to the decisionmakers in the operational agencies as well as to the politicians. These latter people are the decision makers. They are the consumers of knowledge. (If we’re lucky). This is not ideal, but it is real.

Those who generate knowledge are welcome to advocate for certain types of actions. But ultimately, it is the elected leaders, representatives or the civil servants who will really decide. (I’m speaking here about liberal democratic systems, and the international institutions modeled on them. That might not be the whole world, but it is that part of the world that cares about design.)

Notice how something interesting has happened here. One of the inadvertent functions of democracy is to keep knowledge distinct from action. Action is to be a product of democratic choice, and bureaucratic implementation, not professional knowledge.

That is, action comes from decisionmaking, and decisionmaking is a political process, subject to political correction. You don’t like the decision, you throw out the decisionmaker and elect another one. Design exists only in debate. Not as a process for moving knowledge to action.

What is absolutely crucial to understand here is that the legitimacy of actions by decisionmakers — whether they are policymakers or civil servants — is derived from the political philosophy of democracy itself. Liberalism. The social contract. Self-government. We the people. That sort of thing. That is why it’s OK for them to do things to you. Raise your taxes. Tear up your roads. Go to war on your behalf. Change your health system. Legitimacy, in political processes, is presumed by the system. Is not a product of the system.

Here’s what’s good about the democratic model: It allows for, and creates, systems and processes to try and ensure that the will of the people is expressed in the action of decisionmakers — whether at the highest or lowest levels. Said differently, social action is meant to be derived from democratic processes. Insofar as democracy is good, social action will be legitimately enacted.

Here’s what’s bad about it: There’s no mechanism for good designs to be introduced into the system, because no one is really wondering what to do. When answers are dictated by political processes, people don’t entertain a lot of questions. Instead, they are given platforms, mandates or missions to fulfill. Because that’s what people want. The knowledge-to-action nexus simply does not create space for design process.

So is that end of the story? If there’s no design space in public policy, isn’t that the end of the road for design?

Actually, no. I think it’s just the beginning. And here’s why. The times are changing. Deep in the bowels of democratic nations, the very definition of legitimacy is starting to evolve. People don’t just want a voice anymore. They don’t just want to elect people who will advance their will. They are starting to demand results.

If at one time governments simply had to make hard decisions about peace and war, the economy, and other matters, today, the systems into which they are making decisions is so complex, so non-linear and dynamic, that sheer force of will and character is no longer enough. Climate change, global terrorism, the depletion of fossil fuels and the energy crisis, the shortage of clean water, the threat to the nation-state system in most of Africa and the Middle East, the breakdown of almost every social service including transportation, health, and education... these aren’t decisionmaking issues. They can’t be solved by leadership alone.
These are design issues. They require tutored and fastidious attention to the process of both generating knowledge, and moving it to action through processes of design.

I think the door is opening for design if we conceptualize design as a process for moving knowledge to action in innovative, rigorous and ethical ways. Design is the application solution for knowledge.

It's time to go back to the circles. I want you to push those two even farther apart now and make space for one right in the middle. And we will label that one “design.”

If we see little space for design in public policy due to certain philosophical premises in democracy — which become manifest as routines in bureaucracies — we do see comparably more space for design between knowledge and action in industry, where results somehow depend on the design of solutions to problems. Here, legitimacy isn’t presumed. It’s earned.

It is no wonder, then, that designers and business leaders are thinking that design can now be applied to public policy.
After all, if people want results, and we design results, it should be a pretty smooth transference of skill sets. And so, with energy and a whole lot of money, design is stepping into the unknown and promising that it can lead.

And yet, for those of us who are serious researchers and are serious public policy people, one can’t help but sense a certain loose relationship between design today and the simple notion of rigor.

I had a professor at Oxford who once said, “the less you know about something, the easier it is to develop a theory about it.”

As design moves away — or at least broaden from — its creation of objects of desire to social processes and systems, it is reaching a point of creative tension with its own premises. These premises are challenged as it steps into new domains, and also as it steps into new cultural systems. Premises about value. About utility. About rationality. About social relations. Even about the very nature and use of time.

This is a wonderful moment because design now has a chance to step through the open door being offered by the re-imaging of public services and government. It is a formative period too, because the directions you set out on will have profound implications down the road as the paths further diverge. Get it right, and design will take it’s place between the philosopher and the king at the high tables of social influence. Get it wrong, get distracted, go the easy route, and design will be a trendy, marginal field that could never gets act together.

My concern right now — as I advocate for design in public policy — is that the field is adopting some rather under-developed theory at what seems to be alarming rate, at a very formative moment. In the rush to be useful, to be seductive, to be creative, to be responsive, the professional field of design might be taking shortcuts that will lead it quickly to irrelevance. There could be a “design bubble” developing and it could pop.

One way to avoid this is to not mistake the panic of industry to find new ideas with the quality of ideas its finding. Panic buying tends to push the price of ideas, and therefore the investment in them, down. In a panic, any old idea will do.
However. If the goal here is really to achieve some social good in the public service, lead design into a more socially influential future for the greater good, and actually mainstream design at the nexus between knowledge and action, then we might just need to slow down, and grow up.

Those are two odd requests for design because, historically, it hasn’t needed to. But as design looks towards public service, and as business looks towards emerging markets, fragile states and conflict zones, business as usual is going to get people killed.
That’s not a mere turn of phrase. Here are the topics I deal with at UNIDIR, in no particular order. Small arms and light weapons, landmines, conflict prevention, crisis management, post-conflict reconstruction, peacebuilding, weapons collection, disarmament, demobilization and reintegration of ex-combatants, crimes against humanity, child trafficking, gender-based violence, conflict analysis, conflict sensitive operational programming, and that’s just the small stuff. Add biological, chemical and nuclear weapons, weaponization of space, terrorism and counter-terrorism, state fragility and just basically war, and we’re starting to fill out the topics that come up on Monday mornings at 11 at UNIDIR’s staff meetings.

These are real, grown up issues that need real, grown up attention by people who are committed — professionally – to trying to figure out what is wrong with their own ideas, and not what is right about them. Designers are worryingly not involved in that process. Design is trying to prove itself, rather than disprove itself. It is the latter, though, that will serve the social good.

Allow me to explain. What my don at Oxford meant by his quip was that every idea seems like a good idea until you learn what’s wrong with it. And generally speaking, you learn what’s wrong with it by trying to.

There is a very strong school of thought in science, and I count myself in this camp, that believes we cannot truly prove things. What we can do, however, is disprove things. We try to figure out, not what’s right about a given course of action, but what’s wrong with it. If you turn it over and over and over again in your mind and can’t think of anything, you give it a go. We haven’t proved it’s a good idea. But we’ve hopefully weeded out the worse ideas and in doing so raised our confidence in the course of action we’ve chosen. Karl Popper is a key reference here.

Today, design does not seem to be centrally concerned with building theory or processes that can be disproved. In fact, it doesn’t seem to be interested in process at all. It seems to be interested in thought. And yet, thinking and acting are not the same. If one can engage in “design thinking” then it stands to reason that one can have “design thoughts.” But ... now what?

The problem with so-called design thinking is that it is about just that ... thinking. Mapping out — or just speaking metaphorically — about ways of thinking is not the same as producing systems, processes or frameworks for mobilizing thought to action.

Design thinking — though a catchy slogan to be sure — is not a developed analytical concept, is not distingusiable as a means of thoughts from other forms of thought, and let me go on record saying it is not a “methodology.” In the words of Gertrude Stein, there’s no there there. If it cann’t be distingusihed, defined, enacted, or falisfied, I’m not sure what it can do other can sparkle and hypnotize.

For “design thinking” to be worthy of serious consideration, rather than just rhetorical appropriation, it will need to evolve into an actual analytical framework that tells me something about the world, and in turn allows me to differentiate it, genuinely, from other forms of thinking. Right now, it doesn’t. In a nice blog entry at the Harvard Business Review, Peter Merholz (9 October, 2009) shared a smiliar lament. He wrote, “We have librarians, and historians and fine artists. All of these disciplinary backgrounds allow people to bring distinct perspectives to our work [in business], allowing for insights that wouldn’t be achieved if we were all cut from the same cloth. Do we need to espouse ‘library thinking,; “history thinking,’ and ‘arts thinking.’” Merholz was right to call this absurd and to point out that design thinking is merely clever repackaging of some social science — but sadly, not good social science.

The reason this troubles me, rather than just distracts me, is that “design thinking” is directing creative attention away from the pursuit of intellectual clarity, and the progression of design as a serious endeavor. And part of that failure is ours. Ours as a design community. And at this point, for this reason, I will include myself among this world of designers.

Our collective failure to demand clarity from ideas — especially when our ideas lead to actions of moral consequence — is an expression of moral weakness. It takes courage to demand clarity. To stand in front of the masses and say, “I don’t understand. You are going to need to explain that again.” And an idea continues to make no sense, we must entertain the notion that the fault is not ours. Some things in the world are wrong. And it requires courage to say so.

I would like to see a new contract formed between design and public policy. But only if that contract is well written.
I want to end this presentation by briefly mentioning what we’ve done to establish a new agenda and programme of work for design and public policy.

In June of this year, the SNAP project at UNIDIR, in cooperation with the Said Business School at Oxford, and the Center for Local Strategies Research at the University of Washington, hosted an agenda-setting event called Strategic Design and Public Policy. It included top thinkers and practitioners in cultural research, design, and international peace and security. It put together a real and serious agenda. It is not as shiny as some of the other things on offer today. But I assure you, isn’t dull either.

In considering those three circles again, it is now clear – following that event – that there are serious issues between and among all three of these thematic areas that are going to need attention if a new model for legitimate and socially beneficial design is to be developed. We need to step away from metaphor and mystical thinking, and get serious about strategic design.

The Strategic Design and Public Policy agenda, created at Glen Cove in New York, explicitly notes the theoretical, methodological and practical gaps between the generation of knowledge and its application to design processes, on the one hand, and the integration of design processes and products into public policy on the other. We view these as matters for attention, and challenges, not obstacles.

In the discussion that drew the event to a close, participants from cultural research, design (especially service design) and public policy suggested next steps as an agenda for strategic design and public policy. These steps are already being implemented in at least half a dozen organizations including UNIDIR at the UN, the University of Washington, and live|work, among others. It is a detailed agenda, but there are four categories for action.

These are:
1. Supporting cooperation to develop new methods, tools and practices to learn more about each others’ ways of working;
2. Developing resources for cooperative action;
3. Promoting awareness of strategic design and its value for public policy and programming; and
4. Pursuing solutions for social betterment through social action.

This cooperative agenda opens possibilities for research, design, and public policy to start working in closer synergy in a rigorous, ethical and systematic manner to build the foundations we all need to take more confident action for the public good. And I hope you’ll join us.

I’m delighted to speak here at Götenberg on this topic, and my hope is that is the beginning of a conversation and not the end.