Design and complexity

19
Design within complex systems Why it’s important to recognise the right kind of problem

description

Knowing what kind of problem you are solving, helps you to communicate more realistically about the outcome of your project

Transcript of Design and complexity

Page 1: Design and complexity

Design within complex systemsWhy it’s important to recognise the right kind of problem

Page 2: Design and complexity

Using technology successfully in a social context is more a social than a technological challenge.

[I]t is a question of finding the problem and consequently of positing it, even more than of solving it. For a speculative problem is solved as soon as it is properly stated.

Gilles Deleuze, Bergsonism, 15

Page 3: Design and complexity

Three types of problemsH.W.J. Rittel, M.M. Webber, Dilemmas in a General Theory of Planning.

Page 4: Design and complexity

Simple problem

Once the problem is clearly stated, both the solution and the pathto the solution become clear

Page 5: Design and complexity

Complicated problem

Although the problem can be stated, and the solution is clear, the path towards that solution can be long and complicated

Page 6: Design and complexity

Complex problem

Since the problem cannot be clearly stated, the solution andthe path towards that solution remain unclear

Farrow Partnership Architects – Biology of Business: Complex Adaptive Systems.

Page 7: Design and complexity

Complex problems• Cannot be solved. • Have solutions that are always “work in progress”.• Are better understood in the process of solving them.• Are affected by your activities in the world.

H. Brignull, No rest for the wicked: a UX designer’s job is never done

Page 8: Design and complexity

Three strategies to deal withcomplex problems

Page 9: Design and complexity

AuthoritarianIf the problem is defined by one person, and others cannot challenge this, creating a solution that meets the brief becomes possible.

N. Roberts ,Wicked problems and network approaches to resolution, 4

Page 10: Design and complexity

Authoritarian+ Quicker problem definitions when fewer people involved.

- Authorities can be wrong about the problem and the solution.

- Experts tend to search for solutions within their narrow expertise.

- No-one but the experts learns from their attempts.

N. Roberts, Wicked problems and network approaches to resolution, 4,5

Page 11: Design and complexity

CollaborativeBy joining forces parties can accomplish more as a collective than [on their own]. At the core of collaboration is a ‘win-win’ view of problem solving. [...] [T]hey assume a ‘variable sum game’ that seeks to ‘enlarge the pie’ for all parties involved.

N. Roberts ,Wicked problems and network approaches to resolution, 7

Page 12: Design and complexity

Collaborative+ Each stakeholder holds some truth in dealing with complex problems.

+ Because the problem is defined by more people, the solution is more likely to be beneficial.

- Adding stakeholders to [...] problem solving [...] increases ‘transaction costs.’

- Collaboration requires practice; it is a learned skill.

N. Roberts, Wicked problems and network approaches to resolution

Page 13: Design and complexity

CompetitiveCentral to the pursuit of competitive strategies [...] is the search for power. To the extent a competitor can build a power base larger than his opponents, [...], he can increase his chances to win and define the problem and solutions in a way he sees fit.

N. Roberts ,Wicked problems and network approaches to resolution, 5

Page 14: Design and complexity

Competitive+ Problems can be solved by ‘winning’ and moving to authoritarian strategies.

+ Without a clear path, it is preferable not to go forward in any one direction.

+ They challenge the institutionalisation of power.

- Because many solutions are tried at once, it’s very resource-intensive.

N. Roberts, Wicked problems and network approaches to resolution, 4,5

Page 15: Design and complexity

Which strategy to use?

Page 16: Design and complexity

It depends

Authoritarian Collaborative Competitive

Complexity

Page 17: Design and complexity

Key point

Designers always deal with complex problems, failing to recognise (and communicate) this will lead to failedprojects, disappointed clients and frustrated designers

Page 18: Design and complexity

SourcesBookG. Deleuze, Bergsonism

Articles:H.W.J. Rittel, M.M. Webber, Dilemmas in a General Theory of Planning.N. Roberts, Wicked problems and network approaches to resolution.

SiteFarrow Partnership Architects – Biology of Business: Complex Adaptive Systems.http://www.slideshare.net/FarrowPartnership/biology-of-businessH. Brignull, No rest for the wicked: a UX designer’s job is never done.http://www.90percentofeverything.com/2009/01/19/no-rest-for-the-wicked-a-ux-designers-job-is-never-done/

Photos:Slide 2: http://ce399resist.wordpress.com/2011/04/13/society-of-control-by-gilles-deleuze-lautre-journal-1990/Slide 8: http://www.flickr.com/photos/tambako/584155228/Slide 9: http://www.flickr.com/photos/dunechaser/104968146Slide 11: http://www.flickr.com/photos/irievibrations/3675852330Slide 13: http://commons.wikimedia.org/wiki/File:Abraham_Diepraam_-_peasants_brawling.jpgSlide 15: http://flickr.com/photos/tambako/2524829095

Page 19: Design and complexity

Thanks,Sjors

@sjorsnotura.com