Review: The Reflective Practitioner (Part II)

See Part I of this review for the introduction and background.

The everyday life of practitioners involves “tacit knowing-in-action,” that is, we instinctively know stuff and know how to do stuff, even if we can’t explain how to do it. We make judgments, evaluate situations, and recognize patterns without much thought. Shades of Malcolm Gladwell’s Blink here. But practitioners sometimes need to think about what they are doing while they do it. This is what Schön calls Reflection-in-Action. Something challenging or puzzling happens and the practitioner has to reflect on what the best way is to address it, what his or her actions should be in response to it. This is where the “art” of practice comes in.

An expert practitioner, Schön says, (I’m paraphrasing here) is one who can selectively manage large amounts of information, spin out long lines of invention and inference, and has the capacity to hold several ways of looking at things at once without disrupting the flow of inquiry. Schön notes that it is important to realize that in most areas of practice, there are competing schools of thought about the nature of the practice and how to best solve problems. But the structure of reflection-in-action crosses the divide between them.

Here’s how reflection-in-action works, according to Schön:

When the phenomenon at hand eludes the normal categories of knowledge-in-practice, presenting itself as unique or unstable, the practitioner may surface and criticize his initial understanding of the phenomenon, construct a new description of it, and test the new description by an on-the-spot experiment.

This isn’t a rare occurrence, Schön asserts. Indeed, for some practitioners, this is the core of their process. I certainly know it is for me, frequently.

Chapter 5, “The Structure of Reflection-in-Action,” is really the heart of this book, and I’ve underlined about half the chapter in my copy. I’ll do my best to summarize.

When confronted by an unusual situation, practitioners “seek to discover the particular features of his problematic situation, and from their gradual discovery, designs a intervention.” The problem is not given–“There is a problem in finding the problem.” Practitioners, while still having relevant prior experience, still treat each case as unique, and thus “cannot deal with it by applying standard theories and techniques.” The practitioner has “a reflective conversation” with the situation.

The first part of this conversation is to reframe the situation, to put yourself into the situation and impose some sort of order onto it. By reframing, practitioners seek to both understand the situation and to change it. When reframing, practitioners have no idea what the implications of the new frame will be, just that within the frame, practitioners can then practice the methods they know to try to solve the problem.

Once the situation is framed, practitioners take reframed problem and conduct experiments on it to “discover what consequences and implications can be made to follow from it.” If these consequences and implications don’t suit the practitioner, the situation is reframed again and again until it does. In design, we call this iteration. The situation itself “talks back” through the unintended effects and practitioners have to listen and change the frame appropriately.

How do practitioners know if they have chosen the right frame? Schön lays out the criteria:

  1. Can I solve the problem I have set?
  2. Do I like what I get when I solve this problem?
  3. Have I made the situation coherent?
  4. Have I made it congruent with my fundamental values and theories?
  5. Have I kept inquiry moving?

Thus, Schön, says, practitioners judge a “problem-setting by the quality and direction of the reflective conversation to which it leads. This judgement rests, at least in part, on his perception of potentials for coherence and congruence which he can realize through his further inquiry.”

How practitioners construct experiments to test problem frames is in Part III of this series.

MEdia

It was a strange week for me. Even though I was heads-down working on a project for most of it, I somehow ended up in BusinessWeek. Twice. (And no, not because I’m married to a BW reporter.) And I had a podcast by Read/Write Talk released too. Fun!

The first BW article, Designing for Diabetics, features the project I worked on for most of the summer: Charmr, a system for managing diabetes. The second BW article is a flattering review of my How to Lie with Design Research talk I gave at the Design Research 2007 conference last week.

The Read/Write Talk podcast is simply me rambling on about interactive gestures and the interactive gestures wiki. There is a transcript if you prefer that to hearing my voice babbling into your ear.

Review: The Reflective Practitioner (Part I)

I’ve been circling around Donald Schön’s The Reflective Practitioner: How Professionals Think in Action for years now and finally got around to reading it. As it turns out, I should have read it a long time ago, since it has so much to say (indirectly) about design and what it means to be a designer today, especially designers in the experience design realm. As it turns out, there is a reason for the fact we’re constantly fighting about things like role/discipline boundaries and titles. The book also offers and analyzes a way of working that is very very much how I work and, I suspect, how many people in my field do as well.

The Reflective Practitioner was written in the early 1980s and took as its premise that the world of work was changing rapidly, that there was a group of people (Richard Florida’s Creative Class mostly) who, unlike doctors, engineers, and scientists, didn’t rely on technical knowledge for their expertise. Schön calls these people “practitioners” and their ranks include everything from social workers to city planners to architects and designers. People who, in the words of Charles Reich, “can be counted on to do their job, but not necessarily to define it.”

Practitioners, Schön says, have “an awareness of complexity that resists the skills and techniques of traditional expertise” and are “frequently embroiled in conflicts of values, goals, purposes, and interests.” (Much like ever project I’ve ever worked on!) Being a practitioner means that the traditional methods and techniques of analytical thinking and scientific process simply don’t work. Problems in the messy world of practitioners “are interconnected, environments are turbulent, and the future is indeterminate.” What is called for under these conditions, Schön argues, are professionals who can, as Russell Ackoff says, “design a desirable future and invent ways of bringing it about.”

All isn’t roses for practitioners, however. We’re struggling against 400 years of Technical Rationality, which is “problem-solving made rigorous by the application of scientific theory and technique.” Technical Rationality is ingrained in our workplaces and in our universities, and the professions that practice it (doctors, lawyers, engineers) are emphasized and revered over those that don’t. Professions that practice Technical Rationality apply general principles (medicine, law, physics) to specific problems to achieve unambiguous results (health, justice, bridges, etc.).

However, Schön points out, “Increasingly we have become aware of the importance to professional practice of phenomena–complexity, uncertainty, instability, uniqueness, and value conflict–which do not fit the model of Technical Rationality.” Instead of simply problem solving, practitioners instead need to problem set. That is, “to determine the decision to be made, the ends to be achieved, the means which may be chosen.”

Schön says,

In real-world practice, problems do not present themselves to practitioners as givens. They must be constructed from the materials of problematic situations that are puzzling, troubling, and uncertain. In order to convert a problematic situation to a problem, a practitioner must do a certain kind of work. He must make sense of an uncertain situation that initially makes no sense.

Problem setting is where we “name the things to which we will attend and frame the context to which we will attend to them.” This cannot be achieved by Technical Rationality, because Technical Rationality depends on understanding what the end is. Only through naming and framing, which do not depend on applying general scientific principles, can these complex problems eventually be solved.

This, however, doesn’t stop practitioners from looking for tried-and-true methods and techniques that will solve all their problems in a neat way. You see this all the time with designers at conferences and on mailing lists, searching for the next great method. Schön says that for practitioners, replying on methods and techniques will leave them solving problems of relatively little importance, for both clients and society at large. It is only by “descending into the swamp” where the practitioners must forsake technical rigor that the really important and challenging problems will be found.

How practitioners should do this is in Part II of this review.

How to Lie with Design Research

I just gave this talk at the 2007 Design Research conference. Since I can’t imagine a better combination of audience, conference subject, presentation topic, and program placement (I was the last speaker of the day), it’s unlikely I’ll ever give it again although it certainly is a lot of fun and the crowd seemed to enjoy it.

David Armano filmed the opening couple of minutes of the performance, so you can get a flavor of the presentation. Watch the video before looking at the slides, otherwise, you might have no idea what is going on.


Supposedly a podcast will eventually be released as well.

Here are the presentation slides with my notes (9.5mb pdf). Realize that half of this presentation is in the performance. It might be like reading a transcript of The Colbert Report and wondering what was so funny about it.

Bravery

Through the CMU grapevine, I heard that Randy Pausch, one of the professors there, has only several months left to live due to pancreatic cancer. Randy is married with three young children and I believe we both attended the same church when I lived in Pittsburgh. His final lecture on Achieving Your Childhood Dreams will be this Tuesday, September 18, 2007 at 4:30 pm (EDT) at CMU. It will also be webcast live at that time.

I wish the Pausch family comfort and strength.

Interaction08 Registration Now Open

I am very pleased to announce that we have opened registration for the first annual Interaction Design Association’s conference Interaction08, to be held in hip, historic Savannah, Georgia February 8-10, 2008. The conference features keynotes from Alan Cooper, Bill Buxton, Sigi Moeslinger, and Malcolm McCullough, and talks from Jared Spool, Dan Brown, Régine Debatty, Matt Jones, Aza Raskin, Jenny Lam, Sarah Allen, and Molly Wright Steenson. We also have workshops led by Marc Rettig, Darja Isaksson, Todd Warfel, and Jeff Patton.

We’re also still accepting submissions for Lightning Sessions until September 15, 2007.

Fall 2007 Happenings

Some miscellaneous stuff of note.

Vote for my SXSW panels: Feeding the Creativity Beast and From Long Tail to Fuzzy Tail (w/David Armano and Jared Spool).

Come see me do my gadfly routine at the Design Research conference in late September when I do a talk on How to Lie with Design Research.

In October, I’ll be in my hometown (thankfully), speaking at my publisher’s conference Voices That Matter Web Design Conference on Gaming the Web: Using the Structure of Games to Design Better Web Apps.

Two Adaptive Path events: MX East, which is a retreat-like conference outside of Philly focused on design strategy and management. Then in November in Vancouver, the world-tour of UX Intensive continue. My interaction design day is the middle of a great (if exhausting) week of workshops. For both events, use my discount code of FODS and get 15% off.

Can Anyone Be a Designer?

Probably because I sit next to trained cook and decent butcher Ryan Freitas (whose article on the similarities between cooking and design (pdf) you should read instead of this post), I’ve been reading books lately about chefs and cooking, namely The Nasty Bits by Anthony Bourdain and Heat by Bill Buford. (I recommend both, simply for the appreciation you will have the next time you eat at a restaurant as to what went into making your meal.) At the same time, a recent thread on the IxDA mailing list once again had designers arguing about whether anyone can be a designer–or whether, in fact, everyone already is.

The movie Ratatouille posed this same question (sort of) about cooking: Can anyone cook?

The answer is, of course, yes. Anyone can cook, to varying degrees. But not everyone can be a professional chef, line cook, butcher, or the myriad of other positions that make up a professional kitchen and the food industry in general. It takes training and a certain temperament and physical endurance. You can be a great cook at home, but that has absolutely no bearing on your ability to be in a professional kitchen, as New Yorker writer Buford found out in Heat.

The same is true, perhaps to a lesser degree, for design (or for that matter any craft that combines artistry and skill). Anyone can design. It’s a human activity, to give ideas form and expression in order to ameliorate a less-than-ideal situation. But not everyone can be a professional designer and work at the level most professional designers do: where money, time, and reputation (yours and your clients’ and your users’) are at stake. And for some designers, like those of medical devices, military systems, and emergency response systems, the stakes are even higher: users are literally entrusting their lives to the designers. I don’t know about you, but I want someone who knows what they are doing designing the important products and services I use.

The problem is though, like the customer in the restaurant, everyone thinks they can design, and will offer an opinion, informed or not, on design work. Having an opinion on design isn’t the same as being a designer. Some opinions are simply better than others. Not just from designers, either. I’ve stolen great design ideas from developers, business analysts, executives, research subjects…hell, anywhere I can get them. But we need to be judicial about the opinions we accept and those we reject. It’s a matter of professional judgement.

What sets a professional designer apart from the amateur should be the quality and variety of the choices the professional designer makes while working. Even though it isn’t always possible (ours being a subjective art), professional designers should strive to make deliberate choices in their work that can be defended. In designing your home, you don’t have to defend your choices to anyone (except maybe your family). In designing products and services that will be bought and sold and used for serious purposes, your decisions had best be good: informed by an understanding of the context of use and tempered by experience, talent, and skill. This is why I get paid.

Revising Designing for Interaction

It’s been almost two years since I started writing my book Designing for Interaction. In that time, the industry and the profession has changed and so have I. If I was to write the book now, I’d write it differently. And that’s what I’ve just proposed to New Riders: a second edition of D4I to come out next summer.

Here’s the TOC I’ve proposed, including topics that readers thought I had left out of the previous edition and incorporating more subjects for intermediate-advanced designers. Let me know if you think I’ve left anything important out.

Introduction to the Second Edition

Ch.1 Three Ways of Thinking About Interaction Design

Ch.2 The Four Approaches to Interaction Design

Ch.3 A Process and a Toolkit for Interaction Designers

Ch.4 Strategic Interaction and Experience Design

Ch.5 Design Research for Interaction Designers

Ch.6 Creating Design Concepts

Ch.7 Making Good Design Decisions

Ch.8 Documenting and Communicating Designs

Ch.9 Prototyping and Creating Form

Ch.10 Creating Smart Applications and Clever Devices

Ch.11 Interactions Across Applications and Platforms

Ch.12 Fixing Broken Products

Ch.13 The Future of Interaction Design

Epilogue: Designing for Good

As you can see, the book will be significantly revised and expanded, probably to about 350 pages, or roughly a third more than the current edition of D4I. I’ll also be retaining some of the best features of the last book, including interviews with interaction design luminaries and up-and-comers. And yes, there will be bibliographies at the end of each chapter so the curious can read further on each topic.

Let me know what you, my loyal readers, would like to read about, and I will try to provide.