The theme of the workshop was making visible the object of design in the design process, and centred on this diagram describing the generalized design process:
This diagram indicates four generalized phases in a design process, which have been placed between two overlapping dichotomies: Between reflecting and acting, and between using and designing:
Study – “Reflecting using” – The ethnographic examination and abstract reflection on the context and given circumstances under which a design is being used or may be used at some point.
Design – “Reflecting designing” – The abstract composing of concepts, ideas, and solutions based on the research and analysis of the existing tools and context of use.
Technology/intervention – “Acting designing” The concrete building, implementing, and configuring concepts in the form of real technological design to improve the existing tools and use.
Live/Work – “Acting using” – The concrete and actual use of the implemented design. The un-reflected day-to-day practices taking place in the given context.
But, as the workshop organizers noted, this is not (only) meant to be seen as a flow from “research to design to implementation to use”, but rather as a continuum – allowing for “back-and-forthing” between the four activities. Their argument was that we need more integration between these, and that the diagram wasn’t intended to maintain the boundaries between these activities, but rather to break them down.
That was the focus of the workshop: How can we best integrate these diverse elements of the design process to make the best possible solution?
It was at this point in the discussion that it became apparent that the phrase “object of design” isn’t quite transparent: The organizers had meant the object being designed: How can it be made visible throughout process – including the ethnographic study? But I had understood it as the object for design: The context, the potential users, the social relations in which the designed object will take part.
I argued that the main challenge in integrating the four elements above is to maintain a focus on the context, the actual situations where a given tool would be used. That is my main concern in the ethnographic work I do in relation to the design and development work at Socialsquare: Connecting the site of use with the designers and developers who build the new social tools for our clients.
Design in itself can only offer affordances for use, it cannot tell the users how to use it. When we design and build tools, especially social tools online, we seek to build the tools people want to use, but we can only do that by letting them use them. One of the other workshop participants said it best when he referred to a phrase one of his older engineer colleagues often used: ‘Let the user finish the design.’