<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for mattward</title><link>http://disqus.com/by/mattward/</link><description></description><atom:link href="http://disqus.com/mattward/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 07 Jan 2009 13:53:31 -0000</lastBuildDate><item><title>Re: Choosenick!&amp;nbsp;&amp;raquo;&amp;nbsp;Service Design job with Imagination at Lancaster: Go back to Uni to become a service designer!</title><link>http://www.choosenick.com/?action=view&amp;url=service-design-job-with-imagination-at-lancaster-go-back-to-uni-to-become-a-service-designer#comment-4964882</link><description>&lt;p&gt;Although i understand the sentiment behind this post, i think you've over simplified and misunderstood a range of different issues.&lt;/p&gt;&lt;p&gt;First is the division or definition of the word 'research' as opposed to 'design'. Although research is a component of any good design practice, it can also be a practice in itself. 'Design research' is at the same time understanding the world, whilst testing out new potentials and opportunities for change. It acts on the world in many different ways, informing and changing the material (and immaterial) landscape, whilst hopefully pushing the boundaries of a discipline without the constraints of client/designer relations. To limit 'academic' research to a non-progressive reflectionism is to miss the opportunity and true nature of design itself. Within academia there’s a wide range of different types of 'research', the academy has been (and still is) struggling with the nature and definition of the term research, i'm more in favor of collapsing the separation - to make stuff is to find out about the world, to design stuff is to create new knowledge.&lt;/p&gt;&lt;p&gt;The second issue is around the concept of 'participatory design' or 'user centered design' - both of these terms have a long tradition - service design didn't invent these and always fall into the trap of claiming well-established tools, approaches and techniques. Most of the methods Engine, Live|Work and Thinkpublic use have their genesis in universities - from Action Research of the 40's and 50's to the Scandinavian approach to participatory design rooted in the trade unions of the 70's. So if any 'borrowing' is taking place, you should look closer to home.&lt;/p&gt;&lt;p&gt;My third (and final) issue is around the 'taxpayers money' comment. Public sector work, that all 'service design' agencies do, use taxpayers’ money. Engine, Live|Work and ThinkPublic have all benefited from the use of taxpayers money... in fact one could argue, that their 'brand credibility' has been built from the public sector work that they’ve done. The ethics around the use of public money is complex - i'm sure i don’t want to enter the quango/ppp debate!&lt;/p&gt;&lt;p&gt;Anyway, just a couple of thoughts ;-).  Should be continued over that beer.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mattward</dc:creator><pubDate>Wed, 07 Jan 2009 13:53:31 -0000</pubDate></item></channel></rss>