O Danny Blog Entries  

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.

Originally posted at Tuesday, October 2, 2007 | Comments (0) | Trackback (0)

Previous Entry
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! ...

Recent Entries
This RSS Feed Has Changed

Five Things I'm Thinking About

How to Program a Conference

Why I'll Never Write Fiction Again

50 Before 50

Thoughts on my 40 Before 40 List

Designing Devices

Albums of the Year 2009

Top 25 Albums of The Decade 2000-2009

Designing for Interaction 2

September 2010
August 2010
June 2010
March 2010
February 2010
January 2010
December 2009
October 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
  O Danny Boy is About Me, Dan Saffer, and has my Portfolio, Resumé, Blog, and some Extras. It also has the blog I kept of my graduate studies and ways to Contact Me.  
  Blog RSS Feeds
Blog Excerpts
Full Entries
Design Entries Only
Atom Feed