19/11/2017 What is a designer: Things, Places, Messages
After today’s Research Methodology class, I felt really motivated to do some additional reading in the library. I wanted to learn more about the role of research and “asking questions” in relation to my own practice. “What is a designer: Things, places, messages“ by Norman Potter (2002, originally published in 1969), is one of my favourite books and I already quoted some content when writing about graphic design as the art of problem solving right at the start of this module. It’s more like a reference book than to be read from start to end, although I really recommend reading it as it raises some interesting concepts about the possibilities and limitations of design. In a number of essays, Potter discusses central issues such as the difference between design and art, art school education, what is good design? as well as the responsibilities a designer has back to the audience and society at large.
In chapter 15, he introduced the importance of asking questions and finding informative answers to the factors what, where, when, why, who and how. When it comes to problem solving, most problems will be presented in ways that may be diffuse, ill-defined, or actually misleading, hence their nature has to be determined first (Potter, 2002: 133). In the diagnostic phase of the design process, the designer will observe, compare, relate, distinguish, question, discuss, research, measure, estimate, and record (Potter, 2002: 137). Asking questions will help them
to gain a sufficiently objective awareness of the parameters and contexts of the problem, taking full account of relevant facts, interests, possibilities and limitations (Potter, 2002: 133).
to focus and clarify their own response and to exclude irrelevant responses (Potter, 2002: 133). The designer show avoid to project their own interests, jump to quick conclusions or prejudice certain issues before further investigation.
to gain a better sense of the feel, weight, media context of the job and relate themselves productively to its potential. (Potter, 2002: 133)
to construct a satisfactory working brief (Potter, 2002: 133) on which successes can be measured.
Potter continues by stating 15 general considerations to be followed when asking questions. I have summarised them in the following list:
The extent of questions will vary, as each problem has unique structures and requirements for communication, however, they should not be based on the apparent scale or simplicity of the problem. I think what Potter means by this is that even a simple problem may have more complex structures underneath its surface. Questioning its causes, conflicts and impact may extend or alter the possibilities beyond our initial recognition (Potter, 2002: 134).
Problem solving requires a dialogue between the designer and client, or between the designer and the total situation, so ultimately the success of questioning very much depends on the designer’s own attitude and approach. Thoroughness will be beneficial as often the answer to one question is the genesis of the next. (Potter, 2002: 134)
There are a number of non-measurable factors which are crucial to the understanding of a problem. Most problems will involve a client, most will involve human relationships, and therefore an effort of identification with other people’s viewpoints is vital. (Potter, 2002: 134) Especially when it comes to user-centred design, listening to their needs, desires, fears and interests can build a good foundation for a final design solution.
When asking questions, the designer’s intention must be reflected both in the structure and tone. Potter states it would be a mistake to rely on formal means to establish informal truths, facts are best investigated formally, opinions or attitudes informally. (Potter, 2002: 135)
Facts and opinions will be inextricably mixed in the client’s experience of their proposed problem, hence the delicacy of the diagnostic technique. (Potter, 2002: 136) Often the client does not really know what needs to be done and relies on the designer for clarification.
Generally, asking questions is more about a diagnosis, not about instantly finding a cure. Questions seek answers and design solutions will arise later in the process. (Potter, 2002: 136)
And finally, questions and answers qualify and reinforce but do not substitute judgement and decision. (Potter, 2002: 136)
I found this reading really helpful as Potter gave the whole ”problem identification stage” a more structured methodology to follow. Asking strategic questions and finding informative answers plays a central role in my practice, hence I believe being guided by his principles may give more direction and focus and possibly even lead to more meaningful starting points. Problem solving requires the designer to be able to assess and diagnose a situation, so contextual and critical thinking will be required to draw logical conclusions and connect the different layers to the design problem.
Sources:
Potter, N., 2002. What is a designer. London: Hyphen.
Photograph by Merbecks, V. (2017)