Reflective Practice

Thinking Tools6.4 Conducting Follow-Up and Taking FeedbackAlso known as Reflection-in-Action, Reflection-on-Action

Developed by Donald A. Schön (The Reflective Practitioner, 1983).

Builds a practitioner's judgment through two habits, reviewing cases after the fact and noticing during the work, which grows a repertoire of cases to draw on.

One workshop reflected on twice: during the work, and in the write-up that evening

At each of the facilitator's turns, pick what she does: the pause in the room, then three lines of the evening write-up. The verdict says whether the pick builds a case she can recall next time or only a feeling about the day. Illustrative.

The workshop

The facilitator

The workshop

The facilitator

Select a stage to read it, or play the sequence.Forty minutes in. The facilitator is mapping a claims process from the front of the room. Forty minutes in, the two supervisors have stopped talking, the eight clerks are waiting on them, and the wall holds six steps.The pause. The plan says keep mapping from the front. Pick what she does next.Pick a move to see the reply.The clerks answer in single words, watching the supervisors. Two more steps go up by the break.No pause: the move stays, and so does the silence.She judges it failing and splits the room into pairs, one supervisor and one clerk each. The wall fills within the hour.Reflection in action: the move is corrected while the work is still going.The day ends. The map is finished. That evening she gives herself twenty minutes to write up the session while the details are clear.The situation. The first line of the write-up names the situation. Pick the line.Pick a move to see the reply.Six weeks later, nothing in a new room would bring this entry to mind.A label: too general to be recalled when it matters.The line names a cue she can recognize the next time it appears.A case: specific enough to be recalled in the middle of the work.What happened. The supervisors fell silent each time a step they owned was drawn as a wait. In pairs, each heard a clerk describe the step and could correct it without defending it.The surprise. The next line records what did not go as expected. Pick the line.Pick a move to see the reply.The entry ends in regret, with nothing to use next time.Rumination: a verdict on herself, and no case.She had never seen a process map read as blame. That is where her stock of cases was thin.The surprise: it marks where her existing cases ran out.The move to keep. The last line is the move she adds to her repertoire. Pick the line.Pick a move to see the reply.Next time she will feel she should be careful, and still not know what to do.A resolution: it names no cue and no action.She tags it as like the budget review where the regional heads stopped talking.A move: when this happens, do that, usable without rereading the case.Six weeks later. In the first hour with a finance team, the same silence falls. The case comes to mind with its move, and she pairs the room at once. The write-up is what gave the pause something to draw on.

Reflective moves made: 0 of 4Reflective moves made: 1 of 4Reflective moves made: 2 of 4Reflective moves made: 3 of 4Reflective moves made: 4 of 4

  1. Forty minutes in (The workshop). The facilitator is mapping a claims process from the front of the room. Forty minutes in, the two supervisors have stopped talking, the eight clerks are waiting on them, and the wall holds six steps.
  2. The pause (The facilitator). The plan says keep mapping from the front. Pick what she does next.
    • Push on: call on the clerks by name and keep the mapping going. The clerks answer in single words, watching the supervisors. Two more steps go up by the break. No pause: the move stays, and so does the silence.
    • Pause: is this move working, and what does this room remind me of? She judges it failing and splits the room into pairs, one supervisor and one clerk each. The wall fills within the hour. Reflection in action: the move is corrected while the work is still going.
  3. The day ends (The workshop). The map is finished. That evening she gives herself twenty minutes to write up the session while the details are clear.
  4. The situation (The facilitator). The first line of the write-up names the situation. Pick the line.
    • A tough workshop with a quiet room. Six weeks later, nothing in a new room would bring this entry to mind. A label: too general to be recalled when it matters.
    • Owners went quiet when their steps were drawn as waits. The line names a cue she can recognize the next time it appears. A case: specific enough to be recalled in the middle of the work.
  5. What happened (The workshop). The supervisors fell silent each time a step they owned was drawn as a wait. In pairs, each heard a clerk describe the step and could correct it without defending it.
  6. The surprise (The facilitator). The next line records what did not go as expected. Pick the line.
    • The morning went badly, and I should have seen it sooner. The entry ends in regret, with nothing to use next time. Rumination: a verdict on herself, and no case.
    • The supervisors read the map as a verdict on them. She had never seen a process map read as blame. That is where her stock of cases was thin. The surprise: it marks where her existing cases ran out.
  7. The move to keep (The facilitator). The last line is the move she adds to her repertoire. Pick the line.
    • Pay more attention to group dynamics. Next time she will feel she should be careful, and still not know what to do. A resolution: it names no cue and no action.
    • When the owners of the work go quiet, pair each with someone who does it beside them. She tags it as like the budget review where the regional heads stopped talking. A move: when this happens, do that, usable without rereading the case.
  8. Six weeks later (The workshop). In the first hour with a finance team, the same silence falls. The case comes to mind with its move, and she pairs the room at once. The write-up is what gave the pause something to draw on.

An example

Forty minutes into a process redesign workshop with a claims team, the facilitator noticed that the two supervisors had stopped talking and the eight clerks were waiting on them. Her plan was to map the current process on the wall from the front of the room. She paused, judged that the move was failing, and split the room into pairs, one supervisor and one clerk each. The wall filled in an hour.

That evening she spent twenty minutes writing up the situation, what she did, what she was responding to, what surprised her, what worked, and what did not. The surprise was specific. The supervisors went silent each time a step they owned was drawn as a wait, because they read the map as a verdict on them. The move she kept was one line: when the people whose work is being mapped go quiet, pair each of them with someone who does the work beside them. Six weeks later, in the first hour with a finance team, she saw the same silence and paired the room at once.

Why it works

Experience teaches only when it is turned into cases a person can recall. A short written review converts a vague impression into a named situation, a move, and its result, and the surprise is the most useful part, because it marks the place where the practitioner's existing stock of cases was wrong or thin. Over a few years those reviewed cases become what expert judgment draws on: a new situation reminds the practitioner of an old one, and the old move comes to mind along with the conditions it needed.

The pause during the work is the same habit run at speed. It works only because the reviews have stocked memory with cases to compare against. Without them, a pause in the middle of a session produces doubt and no alternative move.

The thinking behind it

Donald Schön Donald Schön, a philosopher of professional practice at MIT, set out the two habits in The Reflective Practitioner (1983). Reflection in action is thinking about what one is doing while doing it, so the work can be corrected as it goes; reflection on action is reviewing it afterward. He took the critique in an architecture studio as his model of how the habit is taught. Earlier, with Chris Argyris, he had separated single-loop learning, which corrects an action, from double-loop learning, which questions the assumptions behind it.

How to run it

  1. Write it up within a day. Twenty minutes the same evening, while the details are still clear, is worth more than an hour a week later.
  2. Name the situation in one line. A specific line such as owners went quiet when their steps were drawn as waits can be recalled later; a label such as a tough workshop cannot.
  3. Record the move and the cue behind it. What you noticed matters as much as what you did, because the cue is what you will recognize next time.
  4. Write the surprise before the verdict. Whatever did not go as expected shows where your current cases ran out.
  5. Keep one move and drop one. Phrase each as when this happens, do that, so it can be used without rereading the case.
  6. Link it to an earlier case. A line naming the past case it resembles builds the connections you will draw on in the middle of the work.
  7. Pause at set points during the work. After the first hour and after each exercise, ask whether the current move is working and what the situation reminds you of.

Where it goes wrong

Rumination passes for reflection. The entry replays how badly the session went and ends without a move; spot it when no line reads when this happens, do that, and do not close the entry until one does.

Only the failures get reviewed. Sessions that went well hold moves too, and a journal made only of failures teaches caution and little else. Review one good session for every bad one.

The pause comes before the cases exist. Early on, stopping in the middle of a session to ask whether a move is working brings doubt with nothing to replace the move. Keep writing reviews after the event for several months before leaning on the pause.

When to use something else

  • After-Action Review. When a team, not one practitioner, needs to learn from an event together and agree on what changes next time.
  • Double-Loop Learning. When the cases keep pointing at an assumption that the goal itself rests on, and the goal is what needs questioning.
  • Cognitive Apprenticeship. When the aim is to pass a senior person's cases on to newer staff by narrating them during the work.

Where it sits in SOLVE eX

Go to the source

  • The Reflective Practitioner: How Professionals Think in Action, 1983

Back to the catalog