I have written here before about the mistake of seeing design as a profession and/or a discipline. To me, design is an approach, a way of approaching reality with the purpose to change it. There are no given design areas or disciplines. Instead it is the nature of the problem/situation that usually determines what is a field or discipline. So, for instance, graphic design is a field that has to do with graphic and visual artifacts, architecture is a field that engages with buildings and structure, etc. They are not by nature design fields or disciplines.
Graphic design has some similarities with architecture of course. Some of those similarities can be seen as related to materials, surfaces and structures. Some similarities have to do with how people perceive forms, shapes and colors and their combinations. To me it is obvious that you can approach these qualities either with a scientific approach or with a designerly approach or with a combination. This means that graphic design and architecture can, depending on how we understand them, be seen either as two science based disciplines or two design based disciplines.
This is why it becomes so confusing when people or companies try to state what design is based only on their experiences in one field and only from one persepctive. For instance, Zillions Design (a logo design company) puts out what they call a Periodic Table of Winning Design Elements. They write:
"The following infographic on the Periodic Table of Winning Design Elements, completely sums up what goes on in the design field right from what basic skills designers need to have to design elements to how to handle clients."
Of course they don't mean that this is table in a comprehensive way describes all design elements for all design areas. They probably think about logo design. But they don't state that, which is unfortunate. It creates a lot of confusion. It is possible to develop a periodic table of design elements that is meant to be true for all design areas (see my book "The Design way" as an attempt to do that). I would welcome anyone who would engage in the attempt to further an understanding of design, not as a discipline or profession, but as an overall human approach of inquiry and action that can deliver outcomes that other approaches (science, art, politics, etc) can not.
Showing posts with label design education. Show all posts
Showing posts with label design education. Show all posts
Design is not a profession or a discipline
At a recent design research conference I heard many statements beginning with "we designers..." or "the profession of design...". Almost all these statements are based on the idea that there are certain people that are designers and then others who are not. In many cases participants talked about the design profession (in most cases meaning "those of us who are educated in design schools"). It is as being a designer is a stamp and when you have the stamp then you are a designer.
The way design has developed over the last three decades has made it almost impossible to argue that design is a profession and/or a discipline, but still it seems to be a prevalent belief even among those who know more about design than most everyone else.
I like to make the comparison with other human approaches, for instance, science. Very few would state that being a scientist is a profession or even a discipline. Science is a way to approach the world with the purpose of creating knowledge. The scientific approach can be "used" in any profession and discipline. People engage in science. People engage in design. [Of course, there is the same issue in science, people who believe they are scientists and that science is a profession.]
Architecture has nothing to do with design unless people in architecture engage in design. Architecture can be exercised in a fashion that employs no designerly thinking or activities. Architecture can be performed as a scientific activity or as a process of art, or as a process of randomness and chance. Architecture is not in itself a design profession. Neither is graphic design, interaction design, or any other field. These words however do denote professions, that is, areas where professionals have the task of developing certain types of artifacts or services. They are in many cases also academic disciplines, but that does not make them into design disciplines.
Designing is an human approach for inquiry and action well suited for bringing change into the world. But it is not a profession or a discipline. A person is not a designer, but a person may use a designerly approach to fulfill their goals.
The way design has developed over the last three decades has made it almost impossible to argue that design is a profession and/or a discipline, but still it seems to be a prevalent belief even among those who know more about design than most everyone else.
I like to make the comparison with other human approaches, for instance, science. Very few would state that being a scientist is a profession or even a discipline. Science is a way to approach the world with the purpose of creating knowledge. The scientific approach can be "used" in any profession and discipline. People engage in science. People engage in design. [Of course, there is the same issue in science, people who believe they are scientists and that science is a profession.]
Architecture has nothing to do with design unless people in architecture engage in design. Architecture can be exercised in a fashion that employs no designerly thinking or activities. Architecture can be performed as a scientific activity or as a process of art, or as a process of randomness and chance. Architecture is not in itself a design profession. Neither is graphic design, interaction design, or any other field. These words however do denote professions, that is, areas where professionals have the task of developing certain types of artifacts or services. They are in many cases also academic disciplines, but that does not make them into design disciplines.
Designing is an human approach for inquiry and action well suited for bringing change into the world. But it is not a profession or a discipline. A person is not a designer, but a person may use a designerly approach to fulfill their goals.
Paper back version of "The Design Way" coming in September
I am very happy to announce that Harold Nelson's and my book "The Design Way", published by MIT Press, will be out in paperback in September. The price will be ONLY $19.00! It is rewarding to see how this book is still alive and well. It is about 20 years since we started to work on these ideas. The second edition made it possible for us to update the content. Actually, already when we started to write the book we decided to write it in such a way that it would not feel "old" fast. We were careful with using examples and events that would soon be forgotten. Hopefully this has made the book more stable over time.
Vitruvius was right about design knowledge (2000 years ago)
Many who have studied design theory know that Vitruvius was one of the first practicing designers (architect) and design thinkers who formulated thoughts and theory about design. At the same time I believe that there are not as many today who actually have read Vitruvius' writings. He is most famous for his "Ten Books on Architecture" written sometime in the first century B.C. Most of this book consists of specific directions and guidelines for detailed architectural work.
[The whole book is available online at http://www.gutenberg.org/files/20239/20239-h/29239-h.htm]
.JPG)
I will here only focus on the first chapter of the first book "The Education of the Architect". It is a fascinating text that I find extraordinary full of wisdom in a straightforward and simple way.
I would like to copy the whole chapter, but I have instead chosen to copy a few excerpts from the chapter, just to give a sense of what it contains, and maybe it will lead you to read more. The whole chapter is only a few pages long.
Vitruvius has a clear idea of what knowledge an architect should be equipped with. In Vitruvius text it is possible to exchange "architect" with "designer".
The first paragraph in the chapter is this wonderful statement:
"1. The architect should be equipped with knowledge of many branches of study and varied kinds of learning, for it is by his judgement that all work done by the other arts is put to test. This knowledge is the child of practice and theory. Practice is the continuous and regular exercise of employment where manual work is done with any necessary material according to the design of a drawing. Theory, on the other hand, is the ability to demonstrate and explain the productions of dexterity on the principles of proportion."
It is clear that to Vitruvius the notion of "judgment" takes the position as the most important form of knowledge. It is through a designer's judgment that "all work done by the other arts is put to test". Judgment brings everything together. Judgment is the "child" of both practice and theory, both which Vitruvius eloquently explains. He presents the role of both practice and theory even more clear in the second paragraph where he states:
"2. It follows, therefore, that architects who have aimed at acquiring manual skill without scholarship have never been able to reach a position of authority to correspond to their pains, while those who relied only upon theories and scholarship were obviously hunting the shadow, not the substance. But those who have a thorough knowledge of both, like men armed at all points, have the sooner attained their object and carried authority with them."
Vitruvius also mentioned more detailed knowledge needed but he returns to the larger areas, such as history, philosophy and medicine:
"5. A wide knowledge of history is requisite because, among the ornamental parts of an architect's design for a work, there are many the underlying idea of whose employment he should be able to explain to inquirers."
"7. As for philosophy, it makes an architect high-minded and not self-assuming, but rather renders him courteous, just, and honest without avariciousness. This is very important, for no work can be rightly done without honesty and incorruptibility. Let him not be grasping nor have his mind preoccupied with the idea of receiving perquisites, but let him with dignity keep up his position by cherishing a good reputation. These are among the precepts of philosophy."
"10. The architect should also have a knowledge of the study of medicine on account of the questions of climates (in Greek κλἱματα), air, the healthiness and unhealthiness of sites, and the use of different waters. For without these considerations, the healthiness of a dwelling cannot be assured."
Vitruvius is aware that his list of needed knowledge is long and ambitious, so he adds:
"11. Consequently, since this study is so vast in extent, embellished and enriched as it is with many different kinds of learning, I think that men have no right to profess themselves architects hastily, without having climbed from boyhood the steps of these studies and thus, nursed by the knowledge of many arts and sciences, having reached the heights of the holy ground of architecture."
and he adds later:
"For, in the midst of all this great variety of subjects, an individual cannot attain to perfection in each, because it is scarcely in his power to take in and comprehend the general theories of them."
Of course, for Vitruvius, this type of knowledge is only for men and only for a certain class of men. This is a consequence of his place in history and place. However, this chapter touches on so many issues that today are discussed when it comes to the education of designers, such as, breadth versus depth and practice versus theory. I find this text exciting and a good read for anyone who wants to engage in the question of what a designer should know!
[The whole book is available online at http://www.gutenberg.org/files/20239/20239-h/29239-h.htm]
I will here only focus on the first chapter of the first book "The Education of the Architect". It is a fascinating text that I find extraordinary full of wisdom in a straightforward and simple way.
I would like to copy the whole chapter, but I have instead chosen to copy a few excerpts from the chapter, just to give a sense of what it contains, and maybe it will lead you to read more. The whole chapter is only a few pages long.
Vitruvius has a clear idea of what knowledge an architect should be equipped with. In Vitruvius text it is possible to exchange "architect" with "designer".
The first paragraph in the chapter is this wonderful statement:
"1. The architect should be equipped with knowledge of many branches of study and varied kinds of learning, for it is by his judgement that all work done by the other arts is put to test. This knowledge is the child of practice and theory. Practice is the continuous and regular exercise of employment where manual work is done with any necessary material according to the design of a drawing. Theory, on the other hand, is the ability to demonstrate and explain the productions of dexterity on the principles of proportion."
It is clear that to Vitruvius the notion of "judgment" takes the position as the most important form of knowledge. It is through a designer's judgment that "all work done by the other arts is put to test". Judgment brings everything together. Judgment is the "child" of both practice and theory, both which Vitruvius eloquently explains. He presents the role of both practice and theory even more clear in the second paragraph where he states:
"2. It follows, therefore, that architects who have aimed at acquiring manual skill without scholarship have never been able to reach a position of authority to correspond to their pains, while those who relied only upon theories and scholarship were obviously hunting the shadow, not the substance. But those who have a thorough knowledge of both, like men armed at all points, have the sooner attained their object and carried authority with them."
Vitruvius also mentioned more detailed knowledge needed but he returns to the larger areas, such as history, philosophy and medicine:
"5. A wide knowledge of history is requisite because, among the ornamental parts of an architect's design for a work, there are many the underlying idea of whose employment he should be able to explain to inquirers."
"7. As for philosophy, it makes an architect high-minded and not self-assuming, but rather renders him courteous, just, and honest without avariciousness. This is very important, for no work can be rightly done without honesty and incorruptibility. Let him not be grasping nor have his mind preoccupied with the idea of receiving perquisites, but let him with dignity keep up his position by cherishing a good reputation. These are among the precepts of philosophy."
"10. The architect should also have a knowledge of the study of medicine on account of the questions of climates (in Greek κλἱματα), air, the healthiness and unhealthiness of sites, and the use of different waters. For without these considerations, the healthiness of a dwelling cannot be assured."
Vitruvius is aware that his list of needed knowledge is long and ambitious, so he adds:
"11. Consequently, since this study is so vast in extent, embellished and enriched as it is with many different kinds of learning, I think that men have no right to profess themselves architects hastily, without having climbed from boyhood the steps of these studies and thus, nursed by the knowledge of many arts and sciences, having reached the heights of the holy ground of architecture."
and he adds later:
"For, in the midst of all this great variety of subjects, an individual cannot attain to perfection in each, because it is scarcely in his power to take in and comprehend the general theories of them."
Of course, for Vitruvius, this type of knowledge is only for men and only for a certain class of men. This is a consequence of his place in history and place. However, this chapter touches on so many issues that today are discussed when it comes to the education of designers, such as, breadth versus depth and practice versus theory. I find this text exciting and a good read for anyone who wants to engage in the question of what a designer should know!
Book note: "Convivial Toolbox--generative research for the front end of design"
Sanders and Stappers is doing this well in many ways. The book is first of all nicely designed with great paper! The book is full of interesting design schemas, many of which are quite insightful and interesting. I have yet to read the book carefully and I am not sure I will, not because I do not find it useful but because I am quite aware of most of what the book covers. To me the most interesting elements of the book are the elaborate schemas that in some cases are rich and dense and provide the reader with a lot of insights about the topic in a designerly relevant way. I will definitely use some of those schemas in my own teaching.
So, the book covers in a good way how early design can be supported by generative research. It gives examples and cases on how to do it. I think the book can be useful for anyone who is searching for such support.
At the same time, I find the layout of the book confusing. Numerous different sections, colors, and sidebars. The layout is structured as if it is a basic textbook with readers who need to be guided in detail in their reading, with "hints" and other typical features. It becomes confusing and difficult to read, at least for me.
I was quite intrigued by the title "Convivial Toolbox" since I am well aware of Illich writings and of his ideas. I was hoping that the authors would in a stronger sense build and relate their ideas to the notion on conviviality, but that did not really happen. For instance, to what extent and in what way are the tools described in the book better suited for convivial design than others, and in what way is conviviality supported by the process presented? I was looking for a final reflection or discussion of that but could not find it.
Book note: "Back to the rough ground" by Joseph Dunne
In our research group where we study design practice, we read relevant texts each week this summer and talk about them. Yesterday we read the last chapter, the Epilogue, from "Back to the Rough Ground" by Joseph Dunne.I read this book when it was first published and I keep coming back to it. When it comes to scholarly examinations about what practice is all about, what competence is, what rationality is, there is no other book that can deliver so much wisdom.
Yesterday, re-reading the Epilogue (which I have read many times before), I was again completely overwhelmed with the way Dunne handles this difficult topic. Some paragraphs are so good, it hurts physically to read them!
Book note: "101 Design Methods" and the problematic success of design
I just received my copy of the book "101 Design Methods -- A Structured Approach for Driving Innovation inYour Organization" by Vijay Kumar. This is one of quite many similar books that have been published the last few years, that is, a book that contains a large number of design methods nicely but briefly described.

I have always like this type of book even though I never really use them myself. The same is true for "101 Design Methods". The book contains many of the popular design methods that are used today and Kumar has organized these methods by providing "A Model of the Design Innovation Process".
This model is, in my words, a schema that helps designers think about the design process, what activities are involved, and how the different activities relate to each other. It is a nice schema that invites for further exploration.
Kumar does not discuss design in terms of phases or steps, instead he talks about "Seven Modes of the Design Innovation Process". For each of the methods, Kumar then presents benefits, input, output, and when to use. He also presents "what it does" and "how it works". Everything is well presented and the methods are pedagogically introduced, each on two pages.
As for many of the similar books that introduce methods and techniques in a condensed form, this book also have the same issues. I believe that for someone who is already trained in design and has internalized designerly thinking and is experienced in the design process, a book like this works well. The book then becomes a handbook, a repository, a memory support, an inspirational source for when a designer has to select how to approach a task. For a designer, the descriptions are enough to inspire how to do something based on previous experience, and then they can adapt and adopt the method to the specific situation and need. The two page description reminds the designer of potential methods and also about the core aspects of the method.
However, for someone who is not trained in design, who does not think in a designerly way, the book does not give the same support. Instead, it may even be misleading in the sense that it portraits design as a process of activities that all seem fairly straightforward and "simple". It may appear that given the situation at hand you just decide what you need, or what "mode" you are in, and then uses one of the methods for that purpose. However, this is not the way design works. The complexity of even the "simplest" design situation and process never means that there are obvious choices of methods or techniques.
What we face today with the enormous success of design as a solution to most problems, such as 'innovation' in Kumar's book, is that design is being transformed from a process requiring competence and skills that takes time and effort to achieve into a "quick fix" approach where it is all about picking the right tools. It is as if we would take a traditional carpenters workshop, pick 25 out of the several hundreds of tools in there, arrange them conceptually in relation to what a carpenter does, and expect anyone to be able to do carpentry and achieve high quality furniture. We all know that is not possible. To be a skilled carpenter means to know what tool to use, when and how to use them, and to recognize improvement and quality of outcome. None of these skills are intrinsically part of any method or tool. The skill to be able to think and act like a carpenter is what carpentry is all about.
So, even though I am very happy with the way design has reached the status of today, that all companies and organizations want to be design thinking organizations, I am less happy with the way that this success is manifested in books. The book described above is definitely needed and is a great contribution to many designers. But what we need is more books that can help people to understand design, what it means to be a designer, that can support them in their struggle to develop as a designer. We need books about design that accepts that it is not a "quick fix", not a question of using the right tools, not a question of selecting the right method, but that design is a way of thinking and approaching the world with the purpose of change. And we need books that can do this in an intelligible way that intrigues non-designers and make them understand that the effort needed is worth it if they want to become a designer.
I have always like this type of book even though I never really use them myself. The same is true for "101 Design Methods". The book contains many of the popular design methods that are used today and Kumar has organized these methods by providing "A Model of the Design Innovation Process".
This model is, in my words, a schema that helps designers think about the design process, what activities are involved, and how the different activities relate to each other. It is a nice schema that invites for further exploration.
Kumar does not discuss design in terms of phases or steps, instead he talks about "Seven Modes of the Design Innovation Process". For each of the methods, Kumar then presents benefits, input, output, and when to use. He also presents "what it does" and "how it works". Everything is well presented and the methods are pedagogically introduced, each on two pages.
As for many of the similar books that introduce methods and techniques in a condensed form, this book also have the same issues. I believe that for someone who is already trained in design and has internalized designerly thinking and is experienced in the design process, a book like this works well. The book then becomes a handbook, a repository, a memory support, an inspirational source for when a designer has to select how to approach a task. For a designer, the descriptions are enough to inspire how to do something based on previous experience, and then they can adapt and adopt the method to the specific situation and need. The two page description reminds the designer of potential methods and also about the core aspects of the method.
However, for someone who is not trained in design, who does not think in a designerly way, the book does not give the same support. Instead, it may even be misleading in the sense that it portraits design as a process of activities that all seem fairly straightforward and "simple". It may appear that given the situation at hand you just decide what you need, or what "mode" you are in, and then uses one of the methods for that purpose. However, this is not the way design works. The complexity of even the "simplest" design situation and process never means that there are obvious choices of methods or techniques.
What we face today with the enormous success of design as a solution to most problems, such as 'innovation' in Kumar's book, is that design is being transformed from a process requiring competence and skills that takes time and effort to achieve into a "quick fix" approach where it is all about picking the right tools. It is as if we would take a traditional carpenters workshop, pick 25 out of the several hundreds of tools in there, arrange them conceptually in relation to what a carpenter does, and expect anyone to be able to do carpentry and achieve high quality furniture. We all know that is not possible. To be a skilled carpenter means to know what tool to use, when and how to use them, and to recognize improvement and quality of outcome. None of these skills are intrinsically part of any method or tool. The skill to be able to think and act like a carpenter is what carpentry is all about.
So, even though I am very happy with the way design has reached the status of today, that all companies and organizations want to be design thinking organizations, I am less happy with the way that this success is manifested in books. The book described above is definitely needed and is a great contribution to many designers. But what we need is more books that can help people to understand design, what it means to be a designer, that can support them in their struggle to develop as a designer. We need books about design that accepts that it is not a "quick fix", not a question of using the right tools, not a question of selecting the right method, but that design is a way of thinking and approaching the world with the purpose of change. And we need books that can do this in an intelligible way that intrigues non-designers and make them understand that the effort needed is worth it if they want to become a designer.
Device Landscapes—A New Challenge to Interaction Design and HCI Research
Together with the PhD students Heekyoung Jung and Will Ryan, and my colleague Marty Siegel, I have for some time been working on the idea of device or artifact landscapes (ecologies). We have changed our vocabulary several times trying to capture the nature of relationships between interactive artifacts. We have published a few papers on this research earlier and now a more overall journal article is to be published in a new Korean design research journal.
Stolterman, E. , Jung, H., Ryan, W., and Siegel, M. A. (2013) Device Landscapes: A New Challenge to Interaction Design and HCI Research. Archives of Design Research, 26(2), 7-33
You can find the article here
http://www.aodr.org/
Below is a brief summary of the article:
Background
The number of interactive digital artifacts is growing surrounding personal lives, and individuals have an increasing need to describe, analyze, and interpret what it means to own, use, and live with a large number of interactive artifacts. It becomes critical from a design perspective to better understand the relational aspects among multiple artifacts beyond the use of individual ones. In this article, we examine the nature of networks of interactive artifacts and the way people understand and handle these networks. We introduce the concept of device landscapes as a conceptual tool for the analysis and examination of personal networks of interactive artifacts.
Methods
We describe previous work and discuss the theoretical underpinnings supporting our studies. In particular, we compare and contrast our concept of device landscape to other models of multi-artifact systems with an emphasis on the bottom-up perspective in which landscapes are created by users instead of a perspective given by designers. Also, we summarize and interpret several studies we have completed—including personal inventory study, mapping study, survey, and interview to examine how people perceive and manage their personal device landscapes. Based on our findings we propose a conceptual framework aimed at supporting research on these device landscapes.
Results
From our studies we found that people perceive device landscapes in many different ways and develop their own strategies to manage multiple interactive artifacts, mostly digital devices in use. By investigating high-level patterns from device maps and verbal descriptions, properties and aspects of interactive artifacts are defined to describe the concept of device landscapes.
Conclusion
We also discuss how these personal networks—namely, device landscapes—present new challenges and implications to the interaction design and HCI research community by comparing it to the perspectives of ubiquitous and pervasive computing environments.
[If you are interested in reading the whole article, send me an email.]
Stolterman, E. , Jung, H., Ryan, W., and Siegel, M. A. (2013) Device Landscapes: A New Challenge to Interaction Design and HCI Research. Archives of Design Research, 26(2), 7-33
You can find the article here
http://www.aodr.org/
Below is a brief summary of the article:
Device Landscapes—A New Challenge to Interaction Design and HCI Research
Erik Stolterman, Heekyoung Jung, Will Ryan, Martin A. SiegelBackground
The number of interactive digital artifacts is growing surrounding personal lives, and individuals have an increasing need to describe, analyze, and interpret what it means to own, use, and live with a large number of interactive artifacts. It becomes critical from a design perspective to better understand the relational aspects among multiple artifacts beyond the use of individual ones. In this article, we examine the nature of networks of interactive artifacts and the way people understand and handle these networks. We introduce the concept of device landscapes as a conceptual tool for the analysis and examination of personal networks of interactive artifacts.
Methods
We describe previous work and discuss the theoretical underpinnings supporting our studies. In particular, we compare and contrast our concept of device landscape to other models of multi-artifact systems with an emphasis on the bottom-up perspective in which landscapes are created by users instead of a perspective given by designers. Also, we summarize and interpret several studies we have completed—including personal inventory study, mapping study, survey, and interview to examine how people perceive and manage their personal device landscapes. Based on our findings we propose a conceptual framework aimed at supporting research on these device landscapes.
Results
From our studies we found that people perceive device landscapes in many different ways and develop their own strategies to manage multiple interactive artifacts, mostly digital devices in use. By investigating high-level patterns from device maps and verbal descriptions, properties and aspects of interactive artifacts are defined to describe the concept of device landscapes.
Conclusion
We also discuss how these personal networks—namely, device landscapes—present new challenges and implications to the interaction design and HCI research community by comparing it to the perspectives of ubiquitous and pervasive computing environments.
[If you are interested in reading the whole article, send me an email.]
New book: Mads Nygaard Folkmann's book "The aesthetics of Imagination in Design"
I have the pleasure working with Ken Friedman as Series Editors for a MIT Press book series called Design Thinking/Design Theory. Today I got the fourth book in the series which is Mads Nygaard Folkmann's book "The aesthetics of Imagination in Design". Here is how the book is presented by MIT Press:
"In The Aesthetics of Imagination in Design, Mads Folkmann investigates design in both material and immaterial terms. Design objects, Folkmann argues, will always be dual phenomena—material and immaterial, sensual and conceptual, actual and possible. Drawing on formal theories of aesthetics and the phenomenology of imagination, he seeks to answer fundamental questions about what design is and how it works that are often ignored in academic research."
It is exciting to work with a book series and one of the perks is that you get to see so many book proposals usually a couple of years before they are books, so it is a way of looking into the future. Unfortunately the vast majority of the proposals we get are never written. It seems as if many feel the calling to write a book but few have the time and energy it takes (they definitely do not lack good ideas!).
Anyway, take a look at these books and remember that we are always looking for ideas and manuscripts. Just email me if you want to discuss your ideas. You do not have to have a finished proposal or draft, just some ideas are ok to start with.
Remember that books usually have much more impact on a field than any articles and they stay relevant for a long time and do not get old in the same way.
The Evil of Design
Even though I am happy to see the wonderful push for design thinking and a designerly approach today in academia and in business, it is also a bit disturbing to see the lack of critical thinking about design. Design as an approach is today by many seen as the silver bullet to almost any kind of problem. A design approach is considered to be able to deal with any kind of situation. I do agree that design as an approach is powerful, maybe more so than many believe even among those who advocate it. I do agree that many issues today should be approached in a designerly way. But it is also crucial to remember that design as an approach is not inherently good.
Almost all things that scare us and make our lives difficult and dangerous are designed. Some of the most wonderful examples of great design are also considered to be manifestations of evil. Humans design wars, genoside, weapons of destruction, and maybe even more extraordinary but less obvious designs aimed at suppressing people (such as political, governing or business structures), sometimes even in combination with wonderful 'user' experiences that makes people appreciate being oppressed (what a great design!).
In this new emerging era of design thinking and designerly approaches it is important to remember that design is only an approach--it is a process. It is a powerful approach, but there is no guarantor that the outcome will be good design and there is no guarantee that the design process will not lead to evil designs. At the end of the day, it all comes down to the character of the designer. Values and beliefs guides and shapes the judgements made by the designer. Developing design competence therefore means developing once personal character as well as once design thinking ability.
Anyone engaging in design in a serious way therefore has to be constantly aware of and reflect on the 'nature' of design and also be highly critical of any simple versions of design that promises processes that will lead to good results in some 'automatic' prescriptive guaranteed way. Critical thinking is as important in design as in science.
[In the book "The Design Way" these issues are discussed in the chapters "The Evil of Design" and "The Guarantor-of-Design (g.o.d.)"]
Design thinking revisited by Norman
Don Norman has in some earlier writings been quite critical to the notion of "design thinking", however now he argues that he has changed his mind. I agree with the new Norman. He makes the case that if we see design thinking more as a tool or method then he is ok with it. And he is also careful with stating that it is not the case that all designers are engaged with design thinking, or that all design schools do teach it. I could not agree more. Working with designers all over the world I know first hand that design thinking is not necessarily understood everywhere where the label design is used. Even worse is that a deeper understanding of design as a human universal approach (much broader and critical than design thinking) is almost completely lacking still. But hopefully this is changing in the years to come.
I have one problem with Norman's new position though. He writes "Two powerful tools of design thinking summarize the approach: the British Design Council's "Double-Diamond, Diverge-Converge Model of Design"; and the iterative process of Observation, Ideation, Prototype, and Test called "Human-Centered Design." I think it is dangerous to substitute a way of thinking with a couple of formalized and standardized methods with their own structure and process. Design thinking to me means a critical stance that makes it possible to engage with a situation in a way that is suitable to the context and circumstances. I am sure there are many design situations that would not be suitable to approach by the Human Centered Design process that Norman describes. I have seen numerous design process carried out in an excellent way that in no shape or form resembles that process. So, design thinking, is about thinking, not about particular tools or methods, it is the thinking itself that is the tool!
I have one problem with Norman's new position though. He writes "Two powerful tools of design thinking summarize the approach: the British Design Council's "Double-Diamond, Diverge-Converge Model of Design"; and the iterative process of Observation, Ideation, Prototype, and Test called "Human-Centered Design." I think it is dangerous to substitute a way of thinking with a couple of formalized and standardized methods with their own structure and process. Design thinking to me means a critical stance that makes it possible to engage with a situation in a way that is suitable to the context and circumstances. I am sure there are many design situations that would not be suitable to approach by the Human Centered Design process that Norman describes. I have seen numerous design process carried out in an excellent way that in no shape or form resembles that process. So, design thinking, is about thinking, not about particular tools or methods, it is the thinking itself that is the tool!
Producing knowledge by design for design
The field of design, particularly the philosophy and theory of design, is evolving fast today. Over the last thirty years there has been a plethora of writings about the relation between science/research and design. One of the most contested questions has been to what extent design as a process of inquiry and action also is a legitimate process of knowledge production. It is not strange that the question arises. Science and design have distinct and different purposes as approaches. Jonas Löwgren says it clearly in his recent ACM Interactions article when he writes "The essence of research is to produce knowledge, and the essence of design is to produce artifacts." This is a clean and simple distinction, even though we know it is possible to find examples that makes this definition more complex, but Löwgren states that even if there are other purposes involved in research today, "the knowledge-production purpose is primary".
The same can be said about design of course. Design can have many different purposes but at the core it is all about the process of imagination and production of artifacts (systems, symbols, services, etc), or with other words, it is all about changing reality. Even though the discourse around design as a valid form of knowledge production approach has grown, it is not until lately that we are seeing some real advances. Unfortunately, a lot of energy has been devoted to develop definitions that are compliant with the existing understanding of knowledge production as it is practiced within the scientific tradition. This has led to an outsider perspective on design, that is, design is seen through the scientific definitions, understandings and concepts of knowledge and method. Less energy has been devoted to start from within, with the ambition to develop an insider perspective--a perspective that takes it starting point in a real and deep understanding of design as its own tradition and not seen as "not science".
I made the argument in my article "The nature of design practice and implications for design research" (ref below) that one of the common mistakes done when it comes to design theory is to use an outsider perspective (particularly with a stance in science). Anyway, it is clear to me that we are entering a more productive stage in the development of design philosophy when the insider approach is becoming more common. For instance, the article in ACM Interactions by Bill Gavers and John Bowers on "Annotated Portfolios" and Löwgren article mentioned above are great examples of this emerging realization that design has a real role to play in knowledge production and that the formulation of what that role is has to be done from within design grounded in a deep understanding of design.
A new understanding of design as a knowledge producing approach can be established but not by trying to make design into something it is not. This means that the road forward is not to make or force design to become more scientific or to use scientific methods, instead it means that we have to acknowledge and externalize what the core strength of design is. This is what Gaver, Bowers and Löwgren is doing so well. Löwgren states this well in his article when he concludes:
"To conclude, I strongly support Gaver and Bowers in claiming that design practice has a place in HCI research today, and that the researcher can add knowledge value by providing annotations in addition to the artifacts. My own contribution here is to recognize the proposal for annotated portfolios as an intermediate-level knowledge practice among other such practices. To me, those practices appear to be promising paths toward fruitful academic discourse and collaborative knowledge production that accommodates the nature of design practice without undue “scientistic” reduction."
This is exactly the way forward. However, this is also a challenge of magnitude since it requires anyone who engages with this issue to be equally well prepared in the philosophy of science as well as in the philosophy of design. Even if we are making progress, there are still few who have the ability to make thoughtful contributions based on such double competence, but with a new generation of thinkers who see it as natural to be equally competent in science and design there is hope.
----------------------
Löwgren has a great list of references in his article. To me, these selected references are examples of this new and growing understanding of design as research. I am pleased to see my own writings among the ones I selected :-)
The same can be said about design of course. Design can have many different purposes but at the core it is all about the process of imagination and production of artifacts (systems, symbols, services, etc), or with other words, it is all about changing reality. Even though the discourse around design as a valid form of knowledge production approach has grown, it is not until lately that we are seeing some real advances. Unfortunately, a lot of energy has been devoted to develop definitions that are compliant with the existing understanding of knowledge production as it is practiced within the scientific tradition. This has led to an outsider perspective on design, that is, design is seen through the scientific definitions, understandings and concepts of knowledge and method. Less energy has been devoted to start from within, with the ambition to develop an insider perspective--a perspective that takes it starting point in a real and deep understanding of design as its own tradition and not seen as "not science".
I made the argument in my article "The nature of design practice and implications for design research" (ref below) that one of the common mistakes done when it comes to design theory is to use an outsider perspective (particularly with a stance in science). Anyway, it is clear to me that we are entering a more productive stage in the development of design philosophy when the insider approach is becoming more common. For instance, the article in ACM Interactions by Bill Gavers and John Bowers on "Annotated Portfolios" and Löwgren article mentioned above are great examples of this emerging realization that design has a real role to play in knowledge production and that the formulation of what that role is has to be done from within design grounded in a deep understanding of design.
A new understanding of design as a knowledge producing approach can be established but not by trying to make design into something it is not. This means that the road forward is not to make or force design to become more scientific or to use scientific methods, instead it means that we have to acknowledge and externalize what the core strength of design is. This is what Gaver, Bowers and Löwgren is doing so well. Löwgren states this well in his article when he concludes:
"To conclude, I strongly support Gaver and Bowers in claiming that design practice has a place in HCI research today, and that the researcher can add knowledge value by providing annotations in addition to the artifacts. My own contribution here is to recognize the proposal for annotated portfolios as an intermediate-level knowledge practice among other such practices. To me, those practices appear to be promising paths toward fruitful academic discourse and collaborative knowledge production that accommodates the nature of design practice without undue “scientistic” reduction."
This is exactly the way forward. However, this is also a challenge of magnitude since it requires anyone who engages with this issue to be equally well prepared in the philosophy of science as well as in the philosophy of design. Even if we are making progress, there are still few who have the ability to make thoughtful contributions based on such double competence, but with a new generation of thinkers who see it as natural to be equally competent in science and design there is hope.
----------------------
Löwgren has a great list of references in his article. To me, these selected references are examples of this new and growing understanding of design as research. I am pleased to see my own writings among the ones I selected :-)
Gaver, B. and Bowers, J. Annotated portfolios. interactions 19, 4 (2012), 40–49.
Stolterman, E. The nature of design practice and implications for design research. Int. J. Design 2, 1 (2008), 55–65.
Gaver, W. What should we expect from research through design? Proc. Human Factors in Computing Systems. ACM Press, New York, 2012, 937–946.
Höök, K. and Löwgren, J. Strong concepts: Intermediate-level knowledge in interaction design research. ACM Trans. Computer-Human Interaction (2012).
Design Thinking Readings: Going Deeper
Now and then I post a list of what I consider to be core readings in design theory. This time I decided to call the list Design Thinking Readings: Going Deeper. The reason for this new title is that I want to promote design thinking, but also push those who are engaged in design thinking as a movement or approach to go deeper.
Design thinking is a notion that has received a lot of interest during the last decade, which is a development that I see as extremely encouraging. However, as many others have pointed out, when something gets popular there is a danger that it also looses its core and depth and grounding. I have over the years on this blog commented on many books on design theory and design thinking. Often I try to be positive and supportive to these attempts of developing design thinking as an approach, even though it is not always easy. I truly believe that to move a field ahead, quantity is important, that is, to advance the field we do not necessary need the final book on design thinking but we need many books. My hope is that with a growing body of books the chance that someone can write "the book" becomes greater.
As I mentioned, the purpose of this post is to push the design thinking field towards more depth. If the field want to stay relevant it can not only develop its applicability, it also has to develop its basic foundation. Such a foundation will not be built by an increasing stream of books that popularizes design thinking (even if that is also needed), but by connecting design thinking to existing philosophical and theoretical schools of thinking. Design thinking has to distinguish itself by comparing and contrasting itself to other existing ways of thinking by delving into underlying core ideas and assumptions. This can be done by relating design thinking to existing philosophical traditions, but also by developing design thinking as its own tradition. Both are needed.
Going deeper is not a search for an answer. You will not be able to "find" a ready-made design thinking philosophy in any readings. You have to read it all and compose an overall understanding. And this is where individual effort comes into play--you have to do the work--read and think. We are of course all looking forward to the day when someone is really successful with that composition and able to express it in a book that can help us all.
The list below is in no particular order and is very personal. These are some of the readings that have influenced me in my development of my own design thinking philosophy (as it is presented in our book "The Design Way"). I am really interested in getting feedback on this list. I know that many influential books are not mentioned. I have also limited the list to books (except for a few exceptions) which is just my personal preference when it comes to this kind of readings.
As many of my colleagues and collaborators will notice (since I have not mentioned their books :-), this list is focused on readings that connects to deeper ideas and intellectual traditions and less on modern attempts to develop and apply design thinking. I may develop a list with that kind of readings too some day.
So here we go:
Simon, Herbert. "The Science of the Artificial"
Simon's book is a must in the area. Unfortunately, Simon is not read carefully enough by most people who criticize him. [I have found this article by Hatchuel to be a really good help in reading Simon: Hatchuel, A. (2001). Towards Design Theory and Expandable Rationality: The Unfinished Program of Herbert Simon. In Journal of Management and Governance. Vol 5, Numbers 3-4, September, 2001.]
Rittel, Horst. (1988). “The Reasoning of Designers”,
This short paper is one of the best explanations of what design reasoning is.
Schön, Donald. "Educating the Reflective Practitioner"
I consider Schön to present the most developed design thinking philosophy and theory today. All his readings should be mandatory for anyone who engage in design thinking. But if that is too much, then this book is a good place to start.
Lawson, Bryan. "How Designers Think"
Lawson's book really helped me to form my own understanding of design. Lawson has over the years continued to publish good books on design.
Dunne, Joseph "Back to the Rough Ground"
Probably the best book ever on practical knowledge and judgment.
Krippendorff, Klaus. "The Semantic Turn -- a new foundation for design"
One of the best contemporary books on design theory.
Pye, David. "The Nature and Aesthetics of Design"
This book was first published in 1969 and is a wonderful book on the relation between craft and design, functionality and aesthetics.
Alexander, Christoffer. "The Timeless Way of Building"
Even though Alexander is more famous for his pattern language work (which is usually heavily criticized , this is the book that to me is still relevant and fundamental in its way of posing challenging questions about the purpose of design.
Borgmann, Albert. "Technology and the Character of Contemporary Life: A Philosophical Inquiry"
Of all the readings in philosophy of technology, this is the one that has influenced me the most. A wonderful critique of contemporary design and technology.
Csikszentmihalyi, M. "Flow: The Psychology of Optimal Experience"
Still one of the best and maybe only books in psychology that has direct influence on how to think about design.
Latour, Bruno. "Pandoras Hope: Essays on the Reality of Science Studies"
A book so full of great ideas that it is almost too much. Latour makes the case for reality in a way that makes sense to design theory, it is all about the particular, about here and now.
Feyerabend, P. K. (1975). Against method : outline of an anarchistic theory of knowledge.
Another book that strongly influenced me as a PhD student and I am sure that the basic message from Feyerabend still influences me. Why methods are dangerous and why there are other approaches to change is the message.
Churchman, C. West. (1971). The Design of Inquiring Systems: Basic Concepts of Systems and Organization.
This book made a huge impact on my thinking as a PhD student. Churchman asks the question how we can design a system that can produce knowledge. Design, systems and knowledge, all brought together. [A short version of Churchman's systems philosophy can be found in his book "The Systems approach"]
Kuhn, T. S. (1962) The Structure of Scientific Revolution.
Most people read this extraordinary influential book as being about science. I find the book to be possible to read as a book about design. Notion of paradigm and "normal science" are equally relevant for anyone reflecting on design thinking.
Marcuse, Herbert. "One-Dimensional Man"
All about the consequences of getting stuck in our understanding of the world, and why we have to critically break out of dominating thought figures.
Hillman, J. (1996). The Soul’s Code – In Search of Character and Calling
Another wonderful book that shows what character and calling is all about. Any designer who sees design as based on who you are as much as what you can do should read this book.
Herrigel, Eugen. (1953). Zen in the Art of Archery.
A wonderful book that examines forms of knowing that rests on character and sensibility to reality in a way that good designers should emulate.
Dewey, J. (1934) Art as Experience.
Dewey presents maybe the best foundation when it comes to understanding experience in relation to designed artifacts and systems. Also the philosophical "father" of Donald Schon.
Cross, N. (2010, reprint of 2006 book). Designerly Ways of Knowing.
An excellent book about design as a way of knowing. [A short and simple but great version of Cross's theory of design can be found in his book "Design Thinking"]
Peter-Paul Verbeek (2011) "Moralizing Technology: Understanding and Designing the Morality of Things"
A great book about how to understand designed things.
and finally some self-promotion...
Nelson, Harold & Stolterman, Erik. "The Design Way - Intentional Change in an Unpredictable World"
The 2nd edition is published by MIT Press (2012).
Well, I will maybe update and add more later.....
Book Note: "Observing the user experience" by Goodman, Kuniavsky, and Moed
There are many books that in one way or another describe how to do interaction design (broadly defined). In most cases I do not find these book very interesting for one simple reason. The reason is that they are neither inspiring when it comes to theory, or practical when it comes to guidance. Books like these, mainly labeled as textbooks, are what I see as "in-between" books, that is, they present ideas and theory in a way that is far from grounded and foundational, and they present guidance that is not based on real insights and knowledge about practice.
I just got a copy of the second edition of "Observing the user experience--a practitioner's guide to user research" by Elizabeth Goodman, Mike Kuniavsky and Andrea Moed (Morgan Kaufmann, 2012). To me, this is a book that is not in-between. It is "a practitioner's guide" written in a language and at a level that is very useful. Each aspect of user research is presented in a simple and clear way with concrete and practical guidelines on how to do it. I find the book excellent for anyone who is new to the field and who not just want to know how important user research is but how to actually do it. The authors stay away from making large claims and from relating the practical guidance to more or less developed theoretical frameworks.
However, I think it is important that anyone who uses a book like this complements it other readings that in a solid intellectual way examines the broader aspects of practice and its relationship to theoretical traditions and paradigms.
I just got a copy of the second edition of "Observing the user experience--a practitioner's guide to user research" by Elizabeth Goodman, Mike Kuniavsky and Andrea Moed (Morgan Kaufmann, 2012). To me, this is a book that is not in-between. It is "a practitioner's guide" written in a language and at a level that is very useful. Each aspect of user research is presented in a simple and clear way with concrete and practical guidelines on how to do it. I find the book excellent for anyone who is new to the field and who not just want to know how important user research is but how to actually do it. The authors stay away from making large claims and from relating the practical guidance to more or less developed theoretical frameworks.
However, I think it is important that anyone who uses a book like this complements it other readings that in a solid intellectual way examines the broader aspects of practice and its relationship to theoretical traditions and paradigms.
How to stay competent in the field of interaction design
I am at the moment in Seattle for a few days doing interviews for our NSF project. The project is mainly focused on how professionals understand and use methods and tools. The study I am doing at the moment is aimed at the examination of professional competence and especially on what professionals do to stay competent over time. So far I have done four interviews with highly skilled and experienced UX professionals. They all have impressive experience and competence. It is fascinating with professionals at this level, they are confident, they know that they are competent, and they can explain why. They also know how the industry works and what it takes to stay ahead and to survive in this competitive environment.
In my interviews, these professionals reveal their way of thinking about competence and what they do to stay competent in a rapidly developing field. Not staying ahead of the field, not knowing what is going on, not engaging with colleagues and networks to constantly learn, mean that you will not be the one who will be asked to lead the next project or to work on new creative initiatives. It is a competitive world where a large part of the professional competence is about understanding the corporate environment than knowing the correct tool or method.
The thoughtfulness of these professionals, something they reveal have developed over time, and their insights on what it means to be competent is something that every young professional in the field need to know. I hope that over time I will be able to write brief reports on this ongoing research. I am quite sure that the results will be highly valuable for professionals interested in developing their career. But I also think that the findings are extremely valuable for any employer who is interested in creating a culture where each professional can grow to become the best they can in a way that fits their individual personality and competence.
The interviews will continue. If you are interested in this topic, let me know, either as a professional (maybe to let me interview you) or as an employer who wants to learn more about how highly skilled professionals really think about themselves and their professional environment.
In my interviews, these professionals reveal their way of thinking about competence and what they do to stay competent in a rapidly developing field. Not staying ahead of the field, not knowing what is going on, not engaging with colleagues and networks to constantly learn, mean that you will not be the one who will be asked to lead the next project or to work on new creative initiatives. It is a competitive world where a large part of the professional competence is about understanding the corporate environment than knowing the correct tool or method.
The thoughtfulness of these professionals, something they reveal have developed over time, and their insights on what it means to be competent is something that every young professional in the field need to know. I hope that over time I will be able to write brief reports on this ongoing research. I am quite sure that the results will be highly valuable for professionals interested in developing their career. But I also think that the findings are extremely valuable for any employer who is interested in creating a culture where each professional can grow to become the best they can in a way that fits their individual personality and competence.
The interviews will continue. If you are interested in this topic, let me know, either as a professional (maybe to let me interview you) or as an employer who wants to learn more about how highly skilled professionals really think about themselves and their professional environment.
Book note: "Mapping Design Research"
The book "Mapping Design Research" (2012) edited by Simon Grand & Wolfgang Jonas is a great new addition to the field of design philosophy and theory. The book contains 21 essays covering different aspects of design theory. It is a mix of older seminal writings from recognized design thinkers such as Herbert A. Simon, Christopher Frayling, Bruce Archer, and John Chris Jones. There are also some essays by authors who are not primarily seen as design thinkers, such as Bruno Latour, John Law, Michel Callon, and Friedrich Nietzsche. The book also contains some essays from contemporary design thinkers by among others Wolfgang Jones, Ken Friedman, and Anthony Dunne.
I have not yet had time to read all chapters but several of the chapters are texts I have encountered before. I am looking forward to read the ones that I am not familiar with. It seems to be a good collection and I congratulate Grand and Jonas for putting this anthology together!
I have not yet had time to read all chapters but several of the chapters are texts I have encountered before. I am looking forward to read the ones that I am not familiar with. It seems to be a good collection and I congratulate Grand and Jonas for putting this anthology together!
Understanding Interaction Design Practice
The research project on design methods that we started in September (funded by NSF) is coming along. We are now in the middle of a first interview study where we focus on a range of aspects related to design practice and particularly the use of design methods ("methods" in its broadest possible meaning).
As always when you interview professionals they impress you with the competence they express and their understanding of design and the design process. These practitioners stress aspects of the design process that in many ways are opposite to what non-designers or students believe, for instance that process is more important than outcome, and that judgment is more important than method. They are constantly unwilling to make clear statements about "what works best", "what method is best", "what are crucial skills", etc. Instead they always bring the discussion back to the particular, the particular situation, particular user, particular client, particular technology, and particular design challenge.
It is also fascinating to find that, even though they are highly skilled and competent in what they do, they are also somewhat worried that other professionals in the field are doing things differently and maybe in a better way. This is the case even though they are engaged in professional communities, workshops, conferences, and reads a lot.
It is also clear that the level of knowledge when it comes to design methods, their names, their history, their usefulness, etc. differ drastically.
Anyway, every interview leads to new insights about the everyday conditions of professional practice for interaction design. I am now more than ever looking forward to this research and can see many exciting results in the coming years.
As always when you interview professionals they impress you with the competence they express and their understanding of design and the design process. These practitioners stress aspects of the design process that in many ways are opposite to what non-designers or students believe, for instance that process is more important than outcome, and that judgment is more important than method. They are constantly unwilling to make clear statements about "what works best", "what method is best", "what are crucial skills", etc. Instead they always bring the discussion back to the particular, the particular situation, particular user, particular client, particular technology, and particular design challenge.
It is also fascinating to find that, even though they are highly skilled and competent in what they do, they are also somewhat worried that other professionals in the field are doing things differently and maybe in a better way. This is the case even though they are engaged in professional communities, workshops, conferences, and reads a lot.
It is also clear that the level of knowledge when it comes to design methods, their names, their history, their usefulness, etc. differ drastically.
Anyway, every interview leads to new insights about the everyday conditions of professional practice for interaction design. I am now more than ever looking forward to this research and can see many exciting results in the coming years.
Interaction Design Philosophy & Interaction-Design.org
One of the most ambitious sources of (open) scholarship in the field of HCI and interaction design is today found at Interaction-Design.org. This site is filled with content from some of the most distinguished researchers and designers in the field. I just got an email from interaction-design.org about their newest addition to the encyclopedia. It is an article called Philosophy of Interaction and the Interactive User Experience. The article is written by Dag Svanaes and has substantial comments from Don Norman and Eva Hornecker. Svanaes is ambitious in his approach to reveal the philosophy of the field. This is highly recommendable even for those who might not agree with his analysis. We definitely need more texts like this in the field. Many more.
It is great that we do have interaction-design.org as a source of quality materials that is also free to anyone interested. The site also includes a great calendar of conferences and deadlines and bibliographies of many researchers in the field. Mads Soegaard who is the Editor-in-Chief for this endeavor is doing a great job.
It is great that we do have interaction-design.org as a source of quality materials that is also free to anyone interested. The site also includes a great calendar of conferences and deadlines and bibliographies of many researchers in the field. Mads Soegaard who is the Editor-in-Chief for this endeavor is doing a great job.
Book note: Donald Schön "Technology and Change"
In my quest to read (or re-read) all the books by Donald Schön I am at the moment re-reading his "Technology and Change--The New Heraclitus", published in 1967. I really liked this book when I first read it many years ago, but in a way I think it resonates even more with our present time. It is both possible and easy to read this book as a strong argument for what is today called "design thinking".
Schön builds the whole reasoning in the book around how humans relate to stability and change. Parmenides and Heraclitus are presented as advocates of two archetypal ways of understanding reality in relation to change. Parmenides represents the view where "stability was the only reality; being was continuous, changeless, one; change, in the form of creation or passing away, was inherently contradictory and therefore illusory". On the other hand, Heraclitus saw change as "the only reality" and to whom stability was illusory.
Schön makes the case that society still hangs on to an understanding that is basically Permenidian, even though such a view do not fit with the radical and constantly ongoing technological development that defines our society (and did already in 1967). To cope with such an environment, innovation becomes a core activity and road ahead. Schön writes something that could be written today "Creativity, for the scientist, engineer and marketing man, and generalship in innovation for the manager, now rank with such traditional corporate virtues as loyalty, steadfastness and financial shrewdness. Increasingly, performance in the corporation has to do, in one way or another, with invention and innovation".
In the book Schön dissects what he sees as the dominating understanding of innovation which he calls the "rational view" based on a Parmenidian understanding of reality. He then presents an alternative and Heraclitus inspired view of change, hence the title of the book. It is fascinating to see how in this early book he already have a "theory" of change that later becomes the foundation of his more known work on reflective practice.
Maybe the least known and also most exciting part of the book is when Schön develops what he sees as an ethic of change. In this part of the book he is not as clear as he usually is, which I see as a sign that these ideas are work in progress. Strangely enough, this work on ethics in relation to change and design is something he never really came back to, maybe with an exception of the last chapter in "The Stable State" and in some way in his "Frame Reflection". This is definitely worth some more studies....
Ok, that is it for now....and to repeat myself from some earlier posts. To read Schön is highly recommended. His ideas are extraordinary grounded in solid philosophical reasoning while also based on his professional practice in industry. When a book about technology and change from 1967 feel fresh and exciting to read it is a sign that it contain some great and timeless ideas!
Schön builds the whole reasoning in the book around how humans relate to stability and change. Parmenides and Heraclitus are presented as advocates of two archetypal ways of understanding reality in relation to change. Parmenides represents the view where "stability was the only reality; being was continuous, changeless, one; change, in the form of creation or passing away, was inherently contradictory and therefore illusory". On the other hand, Heraclitus saw change as "the only reality" and to whom stability was illusory.
Schön makes the case that society still hangs on to an understanding that is basically Permenidian, even though such a view do not fit with the radical and constantly ongoing technological development that defines our society (and did already in 1967). To cope with such an environment, innovation becomes a core activity and road ahead. Schön writes something that could be written today "Creativity, for the scientist, engineer and marketing man, and generalship in innovation for the manager, now rank with such traditional corporate virtues as loyalty, steadfastness and financial shrewdness. Increasingly, performance in the corporation has to do, in one way or another, with invention and innovation".
In the book Schön dissects what he sees as the dominating understanding of innovation which he calls the "rational view" based on a Parmenidian understanding of reality. He then presents an alternative and Heraclitus inspired view of change, hence the title of the book. It is fascinating to see how in this early book he already have a "theory" of change that later becomes the foundation of his more known work on reflective practice.
Maybe the least known and also most exciting part of the book is when Schön develops what he sees as an ethic of change. In this part of the book he is not as clear as he usually is, which I see as a sign that these ideas are work in progress. Strangely enough, this work on ethics in relation to change and design is something he never really came back to, maybe with an exception of the last chapter in "The Stable State" and in some way in his "Frame Reflection". This is definitely worth some more studies....
Ok, that is it for now....and to repeat myself from some earlier posts. To read Schön is highly recommended. His ideas are extraordinary grounded in solid philosophical reasoning while also based on his professional practice in industry. When a book about technology and change from 1967 feel fresh and exciting to read it is a sign that it contain some great and timeless ideas!
Subscribe to:
Posts (Atom)
Being retired
So, now I have been retired since May 2025. It is great! I have not done anything related to my work life (yet). Well, I am connected with ...
-
I am developing a theory of interaction (!). In the process of doing that, I am trying to categorize my theory. To do that I need to know wh...
-
For some time now, my good friend and colleague Ron Wakkary has talked about the book " Thing knowledge - a philosophy of scientific in...
-
Nigel Cross has for a long time been one of the most prominent researchers of design. He has a background as an architect and industrial des...