Friday, July 14, 2017

How designers can know about the future

I have written on my blog earlier about one of my favorite books, Donald Schon's "Beyond the stable state". Unfortunately this is a book that is almost forgotten. Probably because people see it as 'old'. It was first published in 1971.

The core idea of the book is that there is no 'stable state' in the world and never will be. Change is the normal, stability is abnormal. Schon makes the case that any form of knowledge that can support designers, therefore, need to be based on the notion of 'no stable state'. I will here only point to the most wonderful pages in the book where Schon presents his notion of 'projective models'. This is a concept that captures what designers do and in his language an 'existentialism' approach instead of a 'systems analysis' approach. He develops this briefly in a subchapter called "Other ways of knowing". He does this on only 10 pages, p 227-237.

It is possible to read the argument in this book as a challenge to more scientific approaches that are built on the idea that knowing about potential future solutions (designing) can best be done by engaging with and extrapolating what we know is stable in the world. Schon's proposal presents an approach that takes the full richness and complexity of everyday reality into consideration. It leads to a realization that 'knowing' as a designer cannot be disconnected with who you are and your experiences and your ability to capture the ultimate particular conditions of each design situation.

I can't write more just know, but I am working on this idea of 'projective models' from Schon and hopefully, it will become a chapter in a book I am slowly working on.

(By the way, if you know someone who has written about this concept, please let me know.)

Tuesday, June 27, 2017

HCI research contributions to the world of knowledge

Here is a fun exercise:

make a list of the knowledge contributions that HCI research has produced over the years.

First some definitions:
Assume that HCI research is about the interaction between humans and interactive computational objects.

The human part is quite straightforward. It refers to any human being, groups, organizations or societies of human beings.

The "computer" part is less clear, but to me, it makes sense to see that as interactive computational objects. Both interactive and computational seem to be part of a general understanding in our field. There are many objects that are not computational but interactive, or the other way around, but we mainly focus on those type of objects that are both. The notion of object is of course complicated. Traditionally it refers to physical machines, but it has changed and can now be any composition and manifestation of functionality that anyone sees as the part a human is interacting with. Ok, these definitions are not enough, but a simple starting point for the exercise.

So, if this is what HCI research is studying with the purpose to understand, explain, reveal, challenge, and improve etc. then what are the major contributions that the field has produced over the years? What do we know about this interaction between humans and interactive computational objects?

Of course, there is a huge pile of knowledge that our field has produced about details when it comes to interfaces, interaction, design and development, technological aspects, etc. But, what if we try to formulate contributions at a very high level of abstraction.

For instance, if the field of HCI is stating that interaction with computational interactive objects is different than interacting with non-computational interactive objects? If so, would that be a major contribution?

It would be exciting to see the field try to formulate some major knowledge contributions that would complement the world of knowledge. Of course, it does not mean that the field would agree on these contributions but at least they would be seen as some kind of substantial knowledge that other fields and the world would benefit from knowing.

Monday, June 19, 2017

Jerker Lundequist "Norm och modell"

[This post will be in Swedish]

Jag sökte en bok idag. I en av mina hyllor hittade jag istället Jerker Lundequists doktorsavhandling från 1982. Titeln är "Norm och modell - samt ytterligare några begrepp inom designteorin". Jag vet inte hur många som har läst Jerkers avhandling, men den var enormt viktig för mig. Jag hade precis startat min doktorandutbildning och sökte förtvilat efter texter kring designteori och kanske ännu mer efter exempel på hur designforskning skulle kunna utföras. Jerkers text och ansats passade mig perfekt. Han arbetar med en filosofisk metod, analytiskt, begreppsanalys, definitioner, etc. något som jag hade troligen sökt men inte tidigare sett.

Jag blev så betagen av Jerkers ideer att jag reste till Stockholm för att träffa honom. Jag var nervös och visste inte riktigt vad jag skulle säga när vi träffades. Men det blev ett bra möte. Han var pratsam och vi diskuterade designteori i ett par timmar på arkitekthögskolan där han jobbade. Jag träffade honom ett flertal gånger senare under årens lopp.

Nu när jag bläddrar i hans avhandling kommer en massa minnen tillbaks och en massa ideer. Det är så tydligt nu hur påverkad jag blev av hans arbete och hur mycket det formade mitt eget tänkande, och fortfarande gör.

Nu när jag läser lite här och där i hans avhnadling blir det tydligt för mig att hans text, ideer och tankar är relevanta än idag. Fler borde läsa honom!

Friday, June 02, 2017

Why designing is not irrational

Any approach that is aimed at changing our reality is an expression of a specific understanding of what it means to be rational, to think and act in a rational way. Most people strive to be rational in some sense, but it is obvious that what it means to be rational varies.

When I look back on my own research over the years, the notion of rationality has always been at the core of my studies. Actually, my Ph.D. dissertation had the title "The Hidden Rationality of Design Work". The core idea of the dissertation was that as long as we can't reveal the hidden rationality of designing, it will stay difficult to describe and understand, and even more important...teach. The study of designing has since then made huge progress in revealing the 'hidden rationality' of design (see Schon, Cross, Krippendorff, etc).

One of the major problems with the notion of rationality is, to me, that people confuse what being rational means with one specific interpretation. This narrow understanding of being rational is highly influenced by what is seen as the highest form of rationality--the scientific process. But most people do recognize that depending on what we are trying to achieve, we need to embrace different forms of reasoning. It is crucial to understand that we have to embrace the notion that rationality comes in many flavors, each bringing certain strengths and weaknesses. If this is not understood, it becomes a problem.

For instance, some people argue that design thinking means not being rational. Some even argue that designers are, or even have to be, irrational in their thinking and doing. This is however only true if we understand 'being rational' in a very narrow sense. 

To argue that designing is irrational is, therefore, a mistake. Designers are rational and have a well-developed rationality (if they are good at what they do). Designing requires both logic and rationality, but it is a logic and rationality that is aimed at exploring and developing new ideas that can lead to not-yet-existing designs. This means that what is rational as a designer is not the same as what is applied by someone involved in trying to explain how reality works or create an understanding of some particular aspect of our reality. Design thinking is aimed at changing reality into something that we do not know what it is,  into something that is only an imagination. Such a process requires certain forms of thinking and acting, it requires a certain form of rationality. The 'hidden' rationality of designing. 

Ok, this is already too long, but as a takeaway idea, I would propose that anyone involved in the study of designing or has ambitions to improve designing spend a bit more time trying to understand the notion of rationality. It is a theoretical tool that is extremely important in any exploration of human approaches of inquiry and action.

-------------------
Stuff to read:
Robert Nozick "The nature of rationality" 
John Dewey "How we think"
Horst Rittel "The reasoning of designers"

and if you want something really good
Joseph Dunne "Back to the rough ground"

and here is an article to download that I wrote a few years back about this topic

Stolterman, E. (2008). The nature of design practice and implications for interaction design research. in  International Journal of Design, 2(1).

Friday, May 26, 2017

Book note: "Homo Deus" by Yuval Noah Harari

I am apparently one of the few that has not read Yuval Noah Harari's first book "Sapiens". I did not even realize this until I got his new book "Homo Deus: a brief history of tomorrow". Now after I have read "Homo Deus" I understand why the first book got so much attention and praise. It is not often you find a book that takes on the biggest possible perspective of humanity, its history and future, and manages to do it without completely making a mess of it.

After I read the book, I read several reviews of it, most of them were quite bad. They do not really seem to get the basic ideas in the book and therefore end up with arguments and critique that clearly David Runciman in the Guardian. Runciman presents the book in a way that, in my view, represents the ideas quite well. I will therefore not here write much about the book, instead, just read his review.

A couple of my own thoughts about the book. Harari introduces the notion of "Dataism" at the end of the book. I found the chapter "The Data Religion" to be fascinating. The way he describes dataism, what it means and what it leads to, opens up many questions and challenges especially related to my own field. Of course, Harari is extraordinary bold, uses the biggest possible brush to paint his picture, which means that as a reader you easily react on details that you may find incorrect or problematic. That is unfortunate since it means you might miss the bigger picture. To get something from a book like this, you have to engage with it at the level of the big ideas it tries to explore. Anyway, the notion that dataism is the next religion and that it can make humanism extinct is quite an ambitious and maybe to many a scary idea. Harari states that if this is correct then humans are not 'needed' anymore.

One strength of the book is, of course, the way it is written. It is easy and fun to read. Great examples and clear arguments. The text is full of conclusions and statements that most would not even dare to express. I truly enjoyed reading the book and I agree with Daniel Kahneman who write on the back of the book "Homo Deus will shock you. It will entertain you. Above all, it will make you think in ways you had not thought before".

Monday, May 22, 2017

Brief book note: The Science of Managing Our Digital Stuff by Bergman & Whittaker

I guess all of us are every day reflecting on how to organize our 'digital stuff', that is, our digital documents, pictures, videos, presentations, etc. Even though we know this, we are often overwhelmed by the speed of the growth of our digital stuff and even more about how to handle it. If you read blogs and magazines there are millions of pages with advice on how to organize, de-clutter, save, purge, etc. However, most of this advice are based on some individuals personal experience and experimentation and not on any broad (empirically based) understanding of what works for most people. That means that all of us can be inspired by the advice we read and then try it on our own, but sometimes we might want to know more about what 'really' works.


In the new book by Ofer Bergman and Steve Whittaker we are presented with what they argue is "The
science of managing our digital stuff".

The book is based on many years of research in the field. The book covers aspects of managing stuff that most of us are familiar with but do not really know much about if it works or not. The book is however not a handbook. The authors are quite clear about that. They write "We believe that research should be very careful in recommending 'good practice'. First, it is difficult to measure whether a practice is good or not. More importantly, ....., individual preferences are prevalent in PIM [personal information management], so that even if a practice is good for some people, research still needs to provide evidence that it will be good for others who implement the same practice. For this reason, we refrain from giving practical advice in this book." (p 235) (I really appreciate this position and I wish we would see it more often.)

Even if this book will not help you to solve your everyday problems of organizing your digital stuff it will help you better understand what the problem is and why it is so difficult. And for those who study any form of organization of data at the intersection between people and machines, this is a great book.


Thursday, May 18, 2017

Brief book note: The Death of Expertise by Tom Nichols

In these days of 'alternative facts' and a growing rejection of science and truth, it is both depressing and refreshing to read a new book by Tom Nichols "The Death of Expertise--the campaign against established knowledge and why it matters".

Nichols has a wonderful way of describing what is going on today with a dismissal of knowledge and expertise. The book is full of extraordinary examples that he examines closely in an intelligent and clear way.

Nichols asks if this is a new problem and his answer is yes. He comments on what is different from earlier times when he writes:

"The death of expertise, however, is a different problem that the historical fact of low levels of information among laypeople. The issue is not indifference to established knowledge; it's the emergence of a positive hostility to such knowledge. This is new in American culture, and it represents the aggressive replacement of expert views or established knowledge with the insistence that every opinion on any matter is as good as every other. ... This change is not only unprecedented but dangerous." (p 20).

This is a depressing picture and as Nichols argues it is not only unfortunate, it is actually "dangerous" and as such something that needs to be dealt with.

Even though Nichols does not provide any simple solutions and ways forward, he is a strong advocate for reason and rationality. And he discusses to some extent what it would take to strengthen the role of reason in our society.

What I particularly like about the book is that Nichols is not looking at the problem from an elevated and superior position, he is not just complaining and blaming others, instead, he approaches the issues with a lot of self-reflection and also criticism of those who are supposed to 'know'--the experts. Overall, a timely and great book.

Monday, May 15, 2017

"..matters which no lips of man could teach"

One of the most frequent questions and comments I hear in relation to the notion of 'Design Thinking' is actually not about design, instead it is about the word 'thinking'. "If design thinking is such an efficient approach to change why is it only about thinking?" This is a very good question and in many cases a question that leads to highly uncomfortable answers.

In our book, The Design Way, we argue that designing is about the hand and the mind, about thought and action. We do this by introducing the old greek notion of sophia as a form of knowledge that combines the hand and the mind. Or as we call it "the knowing hand".

This idea that as an excellent designer of any kind you need both your mind (theory) and your hand (practical skills) is not new. For instance, in one of the first books on design, Vitruvius wrote: "Pytheos made a mistake by not observing that the arts are each composed of two things, the actual work and the theory of it." (Vitruvius, P 11). In the following pages Vitruvius makes a strong case that any architect [or designer] needs to be trained and skilled in both theory and practice.

Christoffer Frayling makes a similar comment in his book "On craftmanship". In one of the chapters, he elaborates on the need for students to have practical hands-on experiences complementing their education. He refers to John Ruskin who wrote: "Let a man once learn to take a straight shaving off a plank, or draw a fine curve without faltering, or lay a brick  level in its mortar, and he has learned a multitude of other matters that no lips of man could teach him." (Frayling, p 84)

Of course, Donald Schön made the same argument over and over in his writings (heavily inspired by the ideas of John Dewey). One of my favorite texts on this topic is to be found in Dewey's book "How we think". In the chapter on Judgment, Dewey makes an extraordinary case for how to develop once judgment ability. One core argument is the need for repeating encounters with situations of different kinds, that is, the particulars of each practical situation teaches us more than any theory without action can.

Unfortunately, we live in a society where the 'split of sophia' is still alive, where the hand (practical knowledge) is separated from the mind (theoretical knowledge). The proponents for each of these tend to look down on the other. It is as common to see statements that denigrate any form of theoretical or philosophical knowledge as to see statements that look down on practical knowledge and skills.

When it comes to designing, this type of division is completely out of place. Designers need to have a deep understanding of the theory, principles and philosophy that guides their own work and how it relates to more universal ideas and philosophies, while at the same time have sophisticated training in the concrete skills, materials, techniques, and procedures needed in their field. And of course, neither of these two is enough in itself, it is only when they are combined into a whole, when 'sophia' is reconstituted that they create the knowledge foundation that can lead to excellent designs.

This means that 'design thinking' is not only about thinking. It is about doing design. And doing includes both the hand and mind. I mentioned above that this is a conclusion that is in many cases highly uncomfortable since it means that those who are drawn to the thinking aspects of design has to accept that no design is a result of pure thinking. At the same time, those who love to do design, has to accept that excellent design is a result of their actions being inspired and informed by thinking. So, go think and do.

-------------------------------

Dewey, John. (1991, originally 1910). How We Think. Prometheus Books.

Frayling, Christoffer. (2012. On Craftmanship--towards a new Bauhaus. Oberon Masters.

Nelson, H. & Stolterman, E. (2012). The Design Way – Intentional Change in an Unpredictable World. 2nd Edition. MIT Press.

Vitruvius. “Ten Books on Architecture" Chapter 1. ( the whole book is here http://www.gutenberg.org/files/20239/20239-h/29239-h.htm)

Wednesday, May 10, 2017

Knowledge Claims Made in Design Research

I am happy to report that an article by my PhD student Jordan Beck and me has just been published in a new issue of She Ji: The Journal of Design, Economics, and Innovation (Volume 2, Issue 3, Pages 179-270, Autumn 2016).  [If you can't download the article, email me]

The title of the article is:

Examining the Types of Knowledge Claims Made in Design Research

The article discusses what distinguish research in design areas when compared to other research areas. We do this by focusing on what type of knowledge claims researchers make in their publications. We found some fairly clear differences between research areas and also some distinct patterns when it comes to research in design.

Here is the abstract of the article:

"Abstract
While much has been written about designerly knowledge and
designerly ways of knowing in the professions, less has been written about
the production and presentation of knowledge in the design discipline.
In the present paper, we examine the possibility that knowledge claims
might be an effective way to distinguish the design discipline from other
disciplines. We compare the kinds of knowledge claims made in journal
publications from the natural sciences, social sciences, and design. And
we find that natural and social science publications tend to make singular
knowledge claims of similar kinds whereas design publications often contain
multiple knowledge claims of different kinds. We raise possible explanations
for this pattern and its implications for design research."

And here is the last section "Conclusion" from the article:

"Conclusion
Multiple knowledge claims of different kinds within individual journal publications
might be the consequence of a young, multidisciplinary field. Another explanation
might be that scholars publishing in Design Studies tend to embrace the values of
design and science, which may account for those publications making claims of
fact and claims of policy. Finally, a third explanation might be that scholars publishing
in Design Studies are writing for multiple audiences with diverse needs. For
example, if a scholar is attempting to write for professional designers, it becomes
relevant and useful to make claims illustrating the utility or applicability of findings
in practice.

Our purpose in writing this article is not to make generalizable claims about
design research or the design field. Nor are we attempting to characterize all publications
in Design Studies, Nature, or the American Sociological Review. We do believe that
our comparison of publications in these three journals can serve as grounds for further
inquiry. It would be possible, for instance, to analyze a more comprehensive
sample of Design Studies publications to determine whether the pattern we describe
in this paper is generalizable. It would also be interesting and worthwhile to compare
our results with an analysis of other design journals to see if and how knowledge
claiming in other design journals manifests different patterns. Moreover, in
this paper we only discuss the kinds of knowledge claims made in design research
as opposed to the legitimacy of the claims in the field or the reasons for publishing
these kinds of claims.

We believe that understanding knowledge-claiming practices is an important
part of intellectual culture building. And it might be a fruitful area for design
research to distinguish itself from other intellectual cultures, since many of the
scholars and researchers working in the discipline apply research methods that
are not unique to design—like anthropology and ethnography—and they work on
topics that could be studied by other fields. Design could be considered a social
activity and, thus, studied by sociologists and psychologists on their terms and
within their culture. The knowledge claims contained in publications, therefore,
could be seen as an interesting and important distinguishing feature of the design
discipline whereas its objects and methods of study might be less distinguishable
from others.

We should continue to engage in the kinds of self-reflective questions that
brought the discipline to where it is now. But we should also begin to think more
intentionally about the kinds of knowledge we are producing and what the consequences
of its production might be."

Friday, May 05, 2017

Book Note: Byung-Chul Han "In The Swarm"

I am reading my second book by Byung-Chul Han. The title is "In The Swarm: digital prospects". Han is a professor of philosophy and cultural studies in Berlin. His books are very short, this one is about 80 short pages. I mention that since it means that you can more see his books as long articles.

So, I will only here comment on the notion of the 'digital swarm' that is the core idea of the book.
Contrary to many other theories of what the digital revolution has led to, Han argues that it does not lead to increased broad political and community involvement. The reason for this is that what we see as a consequence of digital media is not a establishing of a 'mass' or 'crowd' or any other social construction that has a 'soul' or a 'spirit'. Instead, the digital swarm consists of 'isolated individuals', there is no 'we'. There is no "internal coherence. It does not speak with a voice" (p 10).

This 'swarm' has, according to Han, characteristics that do not correspond to the popular image of what social media leads to or can do. One is that it leads to a "gathering without assembly--a crowd without interiority". Sometimes these individuals come together in gatherings, for instance in "smart mobs". Han continues, these individuals "collective patterns of movement are like swarms that animals form, fleeting and unstable. Their hallmark is volatility." (p 12). 

To me, this type of language makes sense in relation to phenomena we experience on social media. Large swarms of people 'liking' and supporting a protest during a fleeting moment in time, just to move on, to the next 'issue' or 'cause', without creating or constituting a sustainable structure or foundation that can engage with real issues, in real time.

Of course, we all know examples where social media truly makes a difference and have influence our society. however, Han's reflections are, in my view highly interesting and raise a lot of questions. I am eager to read more in this book, even though it has already been valuable enough to me.

Thursday, April 20, 2017

"Things That Keep Us Busy - The Elements of Interaction" proofs are sent

Ok, yesterday Lars-Erik Janlert and I sent our final edits to the proofs of our forthcoming book "Things That Keep Us Busy - The Elements of Interaction". If everything goes well the book will be out in August/September. The 'book' is already available on Amazon. And you can preorder it!

Friday, April 14, 2017

Concept-driven interaction design research

Today I carefully read an article that I wrote with Mikael Wiberg and published in 2010 in the HCI journal. The article is titled "Concept-driven interaction design research". It is not always fun to read something you have written a while back, but in this case I was pleasantly surprised. I really liked it!

One reason why I liked it is that since we published the article the field of HCI research has developed and it seems as if the article and its contributions are better suited for today than when it was published.

I also really like the basic idea in the article, that is, that it is possible to use a concept-driven design approach with the purpose of theoretical advancements.   (I think you can download the paper here)

Here is the abstract of the paper:

"In this article, we explore a concept-driven approach to interaction design research with a specific focus on theoretical advancements. We introduce this approach as a complementary approach to more traditional, and well-known, user-centered interaction design approaches. A concept-driven approach aims at manifesting theoretical concepts in concrete designs. A good concept design is both conceptually and historically grounded, bearing signs of the intended theoretical considerations. In the area of human–computer interaction and interaction design research, this approach has been quite popular but not necessarily explicitly recognized and developed as a proper research methodology. In this article, we demonstrate how a concept-driven approach can coexist, and be integrated with, common user-centered approaches to interaction design through the development of a model that makes explicit the existing cycle of prototyping, theory development, and user studies. We also present a set of basic principles that could constitute a foundation for concept driven interaction research, and we have considered and described the methodological implications given these principles. For the field of interaction design research we find this as an important point of departure for taking the next step toward the construction and verification of theoretical constructs that can help inform and guide future design research projects on novel interaction technologies."

Tuesday, April 11, 2017

A forgotten but crucial aspect of designing

One of the most exciting reactions I get when I talk to professional designers about the design process is when I mention what I call the practicalities of designing. With this notion I try to capture all those seemingly 'trivial' aspects of designing that are so easy to forget when we talk about design thinking. The practicalities of designing can briefly be listed as:

Time (not having enough)
Resources (not having enough)
--------------------------------------
Information (not having enough)
Knowledge (not having enough)
Competence (not having enough)

Every design process and designer lives with these practicalities. The first two are the most concrete and also the ones that are most often forgotten and neglected. Designing is about projects. A project has some kind of a starting point and some kind of an end point. The process is to a large extent defined in time and by resources. In most cases, time and resources are decided without any deep understanding of the particulars and specifics of the design process in question. It is done during the 'contracting' process (another aspect of designing which is not given enough attention unfortunately).

The three practicalities under the line are maybe less concrete but are equally practical.  When it comes to information, for instance, there are situations during every design process when the designer experiences that there is both too much information and not enough information. And even though every step in the process creates more (useful) information it also leads to a need for even more. Designers struggle constantly with overwhelming (too much) but insufficient (not enough) information.

My point here is that these practicalities (and there are of course others) are not glamorous or exciting, especially not time and resources, but they are crucial and they define designing. To understand designing requires a deep understanding of these practicalities.

My experience is that if you want to talk to designers and be taken seriously you have to show that you understand and respect the practicalities of designing. You have to know what it means to engage in a design process without enough time and resources, with too much and but insufficient information, without enough knowledge and competence, etc. You need to be able to talk about these practicalities in a language that make sense to professionals and make them recognize that you respect all aspects of their practice.


Friday, April 07, 2017

Why designing is all about you and not the method or tool

Working with students and professionals over the years have helped me understand what aspects of the design process that makes designers stressed and insecure. One factor is the role of methods and tools in designing. Common questions I get are "what are the best methods and tools to use in designing?" and "can you do human centered design while being 'agile'?" or "can 'personas' be used when working with highly specialized products?", etc.

The basic assumption underlying all these and similar questions is that a method and tool to some extent can function as a 'guarantor', that is, that the use of the method or tool can promise successful outcomes. It is possible to see this assumption as a hope for increased 'predictability' in the design process. Predictability in this case means a hope that if we use 'method A' then we can with higher certainty predict that the outcome of the process will score higher on some measure of success scale.

This type of reasoning is not strange. Who would not like to see our design attempts to have a higher level of predictability, so we could be more sure of the outcome? The problem with this reasoning is however that it places too much importance on the role of methods and tools and reduces the importance of the designer's judgment. And such reasoning has some drastic consequences. For instance, it means that if we are able to produce better methods with higher level of 'guarantee' the role of the designer goes down, ultimately even disappears.

In a simple schema that we present in our book "The Design way", we show this in simple way. The circles represent the designer(s).

The left side of the figure shows the logic that I described above, that is, that methods and tools (input) is in some logical relationship with the outcome, will influence the outcome. This means that it is possible to control the outcome of the design process by choosing the right 'input' (methods, tools, etc). This implies that using a certain method will with some certainty improve the outcome. This is a way of thinking that I find utterly problematic and quite wrong.

To me, the design process is at its core a process that is governed by the designers judgment, as is shown on the right side of the figure. Whatever the 'input' is (methods, tools, knowledge, etc), it is the designer(s) judgment that form and shape a certain outcome.

So, the answer to the questions I started this post with is that 'of course, methods and tools matter' in designing, they can help designers or be in the way in their preferred way of working, but they can not in any way predict of guarantee any form of quality of the outcome. This means that designing is all about you as a designer and not about methods and tools.

I realize that this is too rich question to discuss in a blog post...maybe I will return to it later.....

--------------------------------------
Addition:
After publishing this post I got this wonderful question from Deepak (thanks!).

"Are there methods, tools and processes to improve the "you", i.e the designer and designer judgement ? Or is the process just called life :) - that is every designer lives in a unique combination of circumstances and such circumstances ultimately shape their judgement(due to various conscious and unconscious biases)."

My answer is 'yes'. There are ways (even methods and tools) that can be used to develop, grow, and deepen a designers ability to make judgments. For instance, Donald Schon provides a whole range of ways of thinking suitable for this purpose, and there are others too. So, yes it is definitely possible to develop a designers judgment ability.

Monday, April 03, 2017

Designerly Thinking Workshop Reflections

I am just back after a full day workshop on "Designerly Thinking and Doing" in Chicago last week. It was a great day with wonderful participants who contributed with a lot of insights, comments and questions.

It is as always fascinating to hear the stories from individual designers about their professional experiences in widely diverse organizational environments. The stress and frustation of not being understood, the importance of everyday practicalities related to design practice, the philosophical differences between professional groups, the misconceptions about what the design process requires, etc. But also experiencing the enormous energy and willingness among these professionals to learn more, to keep developing, to take the next step. There is a passion about design that in many cases goes far beyond professional need and organizational loyalty. These professionals not only want to do good design work, they are to some extent addicted to it and need to know how to get there.

Anyway, here is the agenda for the day, even though we did not follow it in detail :-) If you are interested in knowing more, just write to me.

AGENDA
9.00 Who I am and who you are
The day in overview
Discussion, who has been trained in design thinking, what are your experiences, why are you here
Approach of the day, schemas
The design map
No problem, no process, no solution
Design Thinking is not a process that leads to good design, it is all about you
10.00 A brief history of design thinking, what does it look like, some examples
Schools of thought about design thinking
What is designerly thinking as a practical method
11.00 Why engage in design at all
What is it that makes designing appealing
The uniqueness of designing
Design Challenges, risk, courage, no process, overwhelmingly complex, insufficient information,
unpredictability, first intentions, depth, value, judgment,
12.00 LUNCH
1.0 Who am I as a design thinker
How to assess design thinking character and competence.
2.00 Developing your own designerly expertise,
How do you stay aware of the development of the field
How do you keep your competence relevant and how do you develop it
3.00 Design thinking and leadership: Build culture (wide), Organize process (middle), Develop expertise
(narrow),
Creating a design culture in your group, team, section and organization
Overcome organizational pushback when implementing a design thinking strategy

Next step!

Wednesday, March 22, 2017

Designerly Thinking and Doing workshops

Just a brief reminder of upcoming workshops.


I will hold a workshop on Designerly Thinking and Doing in Chicago on March 31st. Click on the link if you want to know more.

I am planning to hold the same (similar) workshop in Bloomington, IN, later this Spring, probably in May. Let me know if you are interested. It will be similar purpose and content (but less expensive).

You might be wondering with is different with my workshops in relation to many others out there. Most other workshops on 'design thinking' focus on the design process and some simple tools suitable for the process. In my workshops I focus on the individual's thinking and character, that is, what designerly thinking and doing means when it comes to an individuals competence, abilities, and skills. And on why they matter, and how they can be developed. We will focus on how to grow and become a thinking designer, instead of just describing some activities or tools. It is who you are as a whole person that makes you designer, how you can think, how you can make informed judgments, and how you can assess and evaluate when, where, and why a designerly approach is appropriate or not.

Monday, March 20, 2017

Why Design Thinking Needs Systems Thinking

I was a young student in my first year at the university. I had never heard of systems thinking or any other kind of thinking either. I had entered a program with focus on systems analysis and information systems, and I had no idea what it was all about. Pretty soon I had my first encounter with a real university professor. In the very first course the professor had us read “The Systems Approach” by C. West Churchman. The book was so different from anything else I had read. For the first time, I read something that was intellectually stimulating at the same time as it felt real and practical. I loved the book. 

Due to the same professor, throughout my undergraduate and doctoral years I was "forced" to read, think, reflect and discuss the works of Churchman. We had lectures, seminars and discussions around Churchman’s work. Churchman was as a visiting professor at our department. All this, of course, strongly influenced my intellectual development. My mind was devoted to systems thinking.

But it became too much! I actually came to a point were I had to free myself from the intellectual tradition I was trained in. I realized that systems thinking was not enough, at least not for me. I found that it was too much focused on analysis, on revealing the conditions of the already existing, while I became more and more interested in the not-yet-existing, and therefore moved towards ideas and traditions more focused on design inquiry and action. I tried to find out what creativity, innovation and design was all about. 

In recent year my thinking has changed again. All the ideas that were introduced to me by Churchman is slowly making a “comeback”. I believe this is not something that I am the only one to experience. We are entering a world that through new technology, changing cultures and markets rapidly becomes more complex. Design today is almost never about creating something closed and contained. Almost everything is systemic by design and part of other systems. This is especially true when it comes to digital products and systems. The infusion of computational and communication abilities into almost every new artifact radically changes our whole environment. Nothing is separated from anything else. There are no separable components. We find ourselves in a true world of systems.


In such a world of extreme complexity we need intellectual tools suited for that challenge. And it is obvious to me that popular forms of 'design thinking' are not equipped with such tools. It is as if the pendulum has swung too far on the side of 'creative' and 'innovative' aspects of designing while tools that can support serious investigations of the complexity of reality is neglected. 

I have realized that I am, in a way, back to where I started. In my attempts to handle this complexity I find support and guidance in the thoughts and ideas of Churchman and of systems thinking in general. In his books he reflects on the many aspects of systems and of complexity. He tries to makes these reflections go hand in hand with basic aspects of life itself by always pushing the questions of what systems thinking could and should be used for. These are all issues pertinent to design. Design thinking today is in need of systems thinking. The work of Churchman is relevant and useful in a way I think he would have liked, that is, not as an isolated theoretical lens without relevance outside academia, but as a pragmatic approach to reality with the focus on making a difference.

Friday, March 17, 2017

Why 'design thinking' is risky

When design thinking is promoted it can look like this

"Design Thinking is a mindset. Design Thinking is about having an intentional process in order to get new, relevant solutions that create positive impact. It’s human-centered. It’s collaborative. It’s optimistic. It’s experimental." (link to text)

It sounds really good. But what is not mentioned is that designing is also complicated, difficult, hard and risky. So, why is it that 'design thinking' is portrayed as this fun, exciting and highly positive process without mentioning how risky it is. Well, some people who advocate for 'design thinking' are selling it. They have selfish reasons for making design thinking look exciting, fun and useful and they do not want to stress 'negative' aspects of design thinking. They want everyone to believe that they can easily learn and use design as an approach.

There is of course no serious problem with describing 'design thinking' in a positive light. Designing is intrinsically an optimistic and positive approach. It is built on a core belief that  positive change in the world is possible, that we can make a difference. And to be honest, to those who are trained in designing, the process is rewarding and fun, despite (or maybe thanks to) it being complex and difficult.

However, a process aimed at producing the not-yet-existing is by definition risky. A design process is intended to lead to something that we have not seen before, something new, something different. It means that there is no way of knowing if the process is moving in the right direction, if what is designed will work in its intended context, until it is too late. Designers have to trust what they do. They have to trust the process and their own judgment. And since there is no 'guarantor of design' (that is, anything that can guarantee a 'good' result) the final outcome is a consequence of the designer's judgment and therefore also the responsibility of the designer.

It is not difficult to find examples of bad design in the world. I take this as a clear sign that designing is difficult. It means that whoever decides to approach a situation/problem with a design approach also has to accept that the process may seriously fail. And they have to be ready to take the responsibility for that.

Designing is different from many other process that have well defined goals and outcomes, that have well developed steps and procedures that can to some extent guarantee that if you follow the process you will end up with a good or adequate result. Designing is a process that is 'designed' to not lead to expected outcomes, which is why it cannot be prescribed in detail and why there is no way to clearly 'measure' what a good design is.

So, remember that the design approach is powerful in what it can achieve, but that that power comes at a cost. It is risky. Unpredictable. And difficult. And requires a good design judgment and not just a superficial understanding of what 'design thinking' is.


Wednesday, March 15, 2017

Things That Keep Us Busy: The Elements of Interaction

Our new book is now on Amazon, even though it will not be available until September. But it can be pre-ordered.

Things That Keep Us Busy: The Elements of Interaction (MIT Press) 
Hardcover – September 1, 2017
by Lars-Erik Janlert (Author), Erik Stolterman (Author)

There is no cover yet and not much information, but there is a description:

"We are surrounded by interactive devices, artifacts, and systems. The general assumption is that interactivity is good -- that it is a positive feature associated with being modern, efficient, fast, flexible, and in control. Yet there is no very precise idea of what interaction is and what interactivity means. In this book, Lars-Erik Janlert and Erik Stolterman investigate the elements of interaction and how they can be defined and measured. They focus on interaction with digital artifacts and systems but draw inspiration from the broader, everyday sense of the word.

Viewing the topic from a design perspective, Janlert and Stolterman take as their starting point the interface, which is designed to implement the interaction. They explore how the interface has changed over time, from a surface with knobs and dials to clickable symbols to gestures to the absence of anything visible. Janlert and Stolterman examine properties and qualities of designed artifacts and systems, primarily those that are open for manipulation by designers, considering such topics as complexity, clutter, control, and the emergence of an expressive-impressive style of interaction. They argue that only when we understand the basic concepts and terms of interactivity and interaction will we be able to discuss seriously its possible futures."

Tuesday, March 07, 2017

What design judgment is

A designer is constantly involved in making judgments. The reason is that any decision has to be made based on insufficient information. At the same time, a designer is commonly overwhelmed by the richness and the complexity of the situation. So, dealing with an abundance of information that still feels insufficient while being pressured to move forward means that judgments have to be made. However, even though judgment is a core ability for designers and is mentioned frequently, it is not well defined. So, what is it?

In one of his writings the famous philosopher John Dewey discusses at length what judgment is. This is done in his book "How we think" (which is a wonderful text). I am re-reading this book at the moment and will later write more about some of the core ideas in this book and how they are crucial to anyone engaged in designing.

Below are a few quotes from the chapter. I would like to reproduce the whole chapter, since every page is full of sentences that are both insightful and beautiful!



Dewey on why having more information does not reduce the need for judgment:

"For learning is not wisdom; information does not guarantee good judgment. Memory may provide an antiseptic refrigerator in which to store a stock of meanings for future use, but judgment selects
and adopts the one used in a given emergency -- and without an emergency (some crisis, slight or great) there i no call for judgement." (p 107).

Dewey on why judgment can be developed:

"Long brooding over conditions, intimate contact associated with keen interest, thorough absorption in a multiplicity of allied experiences, tend to bring about those judgments which we then call intuitive; but they are true judgments because they are based on intelligent selection and estimation, with the solution of a problem as the controlling standard. Possession of this capacity makes the difference between the artist and the intellectual bungler." (p 105)

Dewey on why judgment cannot be prescribed:

"No hard and fast rules for this operation of selecting and rejecting, or fixing upon the facts, can be given. It all comes back, as we say, to the good judgment, the good sense, of the one judging. To be a good judge is to have a sense of the relative indicative or signifying values of the various features of the perplexing situation; to know what to let go as of no account; what to eliminate as irrelevant; what to retain as conducive to outcome; what to emphasize as a clue to the difficulty....In part if is instinctive and inborn but it also represents the funded outcome of long familiarity with like operations in the past. Possession of this ability to seize what is evidential or significant and to let the rest go is the mark of the expert, the connoisseur, the judge, in any matter." (p 104)

Friday, March 03, 2017

Design versus Designing

Since a few years I have stopped using (or at least tried to) the word 'design' when it seems more relevant to use the notion of 'designing'. The reason is that I try to be more specific with aspects of design I am addressing.

To me, design is a concept that is broad and extraordinary inclusive. It covers almost anything that has to do with design in all its manifestations and forms. Designing, on the other hand, is more narrow. It is concerned with the practice of design, of the process of design, that is, of design(ing) as an activity.

When it comes to some other similar concepts, such as art and science, the terms are commonly seen as denoting large societal phenomena including their history, present and future. The terms cover all cultural, social, educational, and professional aspects of the phenomena. At the same time, when it comes to the practice or activity the broad terms are no usually used. Instead concepts such as the 'artistic process' or the 'scientific process' are common. Or we talk about 'doing' art or science. The terms science and art are usually not reduced to only signify the practice or process of doing it.

In the same way, the concept of 'design' should be used to denote the larger societal phenomenon of design.

So, why does this matter? Well, if we do want to say specific things about the activity of design, then it seems more appropriate to use the term designing. When people talk about 'design thinking' or 'research through design' it is probably more correct to talk about 'designing thinking' and 'research through designing'. Of course language wise some things have to be changed, not just adding an 'ing'.

The meaning of the 'history of designing' is very different from the history of design. Theory of designing is different from theory of design, etc. I understand that this is minor, minor, thing in the big picture but it matters.

We have many other similar problems in the field of design, for instance with the notion of 'design research' which in some cases means 'the research done by designer during a design process', and in other cases mean ' research about design' and sometimes 'research about designing'. OK, enough...

Friday, February 10, 2017

Why Design Thinking is Not Enough

If you go to Youtube and look for "design thinking" you will find a large number of videos with TED talks and other talks all explaining what design thinking is, how important it is, how to do it, etc. Some are good. They present an understanding of designing that is ok, but in many cases they are quite simplistic, and surprisingly quite often based on the speakers personal experience of realizing the "power" of design as a new creative process to solve problems. The speaker have "seen the light", and the light is design thinking. Again, this is all well, we do need as many as possible to be introduced to a designerly way of thinking. The world needs design thinking.

But, it is not enough. Any approach used by humans to engage with the world in an intentional way, for producing knowledge (as the scientific process) or for producing art (as the artistic process) or for producing change (as the design process) has to be supported. The scientific process has for the last couple of centuries been develop within a larger culture that recognizes, enables, supports and advances it--the academic culture as manifested by universities. This academic culture has developed together, in parallel, with the scientific process. The two have over time influenced each other, and they have more or less had a common goal. The broader academic culture knows what a scientific process is and what it requires to be successful and it sees as its task to make that happen.

If we now look at design thinking instead of the scientific process, a very different picture emerges. Design thinking is in most cases not protected and supported by a broader culture such as the academic culture protects and support the scientific process. When I talk to professional designers in all kinds of industries this is one of the most frequent 'complaints' I hear. these professional designers are happy to be involved in design, but they do not feel understood and definitely not 'safe' or protected. Instead, I often hear them describe their reality having to 'defend', 'explain', and 'fight' for design as a suitable approach. They feel threatened and are always looking for ways to argue for what they do, even to the extent that they start to change the process to look more like processes that might already be recognized and appreciated within the culture where they work.

This is why design thinking (in all its varieties) is not enough. Any design approach needs to be situated within a designerly culture that understands what design is, what is requires, and when it is appropriate (and not). Design thinking needs a surrounding culture that protects its strengths, uniqueness and core so it can perform and deliver what it promises. Companies that bring in design thinking as a quick fix, as a 'tool', as a 'method' will fail unless they engage in creating a broader designerly culture.