Donald Schön: The Man Who Looked Beyond the Instructions


Ask someone how they do their work, and they’ll give you the steps. Ask what makes them abandon those steps, and the conversation gets interesting.
I’m always interested in what experienced people notice that the rest of us miss.
An editor senses that something is wrong with a manuscript before they can quite explain it. A facilitator asks one question and changes the direction of an entire discussion. A consultant hears the problem a client describes and suspects there’s another problem underneath it.
Where does that ability come from? And how do you help someone else develop it?
Those questions bring me to Donald Schön.
An MIT professor, Schön explored how professionals think through situations that don’t fit neatly into what they’ve been taught. His 1983 book, The Reflective Practitioner: How Professionals Think in Action, examined the judgment and improvisation that people bring to their work.
What caught my attention was how much of that thinking can disappear when we explain what we do.
We give people the method. We describe the outcome. Somewhere between the two, we leave out the moment when we realized our original approach wasn’t going to work.
Personally, that’s the part I’d like to hear about.
When Experience Interrupts the Plan
Schön used the term reflection-in-action to describe how people reconsider and adjust their approach while they’re working. Something surprises them. They pay attention, question their understanding, and try something different.
Think about leading a roundtable.
You’ve prepared the questions. You have interesting people around the table. The discussion should practically run itself.
Except nobody has much to say.
You could keep moving through your questions. After all, you spent time preparing them.
Or you could stop and ask what you’re missing.
Perhaps everyone is being polite. Perhaps the question is too broad. Perhaps the conversation people actually want to have is a little more uncomfortable than the one you planned.
The next decision matters more than the agenda.
There’s another possibility, too. You may have misunderstood the problem.
You thought you needed better questions. What the room needed was a reason to speak honestly.
That distinction is worth exploring. Before we explain how we solved something, we should explain how we decided what needed solving.
What We Lose When We Clean Up the Story
This is particularly relevant when someone wants to turn their experience into a book or a learning program.
There’s a natural tendency to make everything orderly. Here’s the framework. Here are the steps. Here’s how it works.
I understand the appeal. Nobody wants to read a manuscript that wanders around for 200 pages looking for its point.
But there’s a difference between making an explanation clear and making the experience sound inevitable.
What did you misunderstand at first? Which detail made you reconsider? When would you advise someone to do the opposite?
Those questions belong in the material too.
Sometimes the useful conversation begins with, “Well, it depends.”
My next question would be, “On what?”
The answer might involve timing, trust, resources, or something particular to the people involved. Now we’re getting somewhere. We’re beginning to understand the conditions behind the advice.
The exceptions deserve attention as well. If your method works well in some circumstances and poorly in others, explaining that helps people decide when to use it.
A reader needs enough understanding to make a decision when their circumstances differ from yours. And they almost certainly will.
Give People a Decision to Make
There’s a practical way to bring this into a learning experience.
Tell the story, but pause before revealing what happened.
Here’s the situation. Here’s what we knew. Here’s what wasn’t going according to plan.
What would you do next? And what would you want to know before deciding?
Then explain the choice you made and what followed.
That gives people an opportunity to examine their own reasoning. They may notice something you missed. They may choose differently and have a perfectly reasonable explanation.
I’d find that a much more interesting discussion than asking whether everyone understood the framework.
It also helps to capture these moments while they’re fresh. A short note after a difficult meeting or an unexpected change can preserve details that disappear from the polished version later.
What surprised me? What did I change? Why?
Those few lines could eventually become the most useful example in a chapter, a course, or a roundtable.
Why This Matters When We Work With AI
Schön made an observation that feels particularly relevant today:
“Old questions are not answered—they only go out of fashion.” sjbae.pbworks.com
I suspect we’ve all sat through a meeting that proved his point.
A familiar problem returns with a new name. Someone proposes a new tool. We move forward without quite establishing what happened to the last solution.
AI gives us plenty of new possibilities. But some familiar questions still deserve our attention. How do people develop judgment? How do we pass experience on? How do we recognize when we’ve misunderstood the problem?
I use AI every day, and I appreciate how much it helps me organize and develop my thinking. Schön’s work makes me consider what I’m giving it to work with.
If I supply a tidy outline of my process, I shouldn’t be surprised when I get a tidy explanation back.
Have I included the difficult decision? The exception? The moment when I realized I’d been asking the wrong question?
Those details give us something worth exploring.
I can also use AI to question the explanation. Where have I skipped a decision? What would a newcomer need to know? Under what circumstances might this advice fall apart?
The answers still need my scrutiny. But those questions can help me examine things I’ve become so accustomed to doing that I barely notice them anymore.
That’s what makes Schön interesting to me today. His work gives us a reason to look more closely at the experience we’re trying to share.
Before we turn it into another article, course, or presentation, perhaps we should spend a little longer asking what actually happened.
The moment you changed your approach may be the part someone else most needs to understand.
What’s something you’ve learned to notice in your work that you rarely think to explain?



Comments