The Multi-Level Learning Coach 57
American Management Association
www.amanet.org
place, restricting improvement and the achievement of important goals.
In Chapter 1, we discussed how defensive routines, often triggered by
red- light learning, can lead to blame, bias, distortions, and the inability
of project and program teams to resolve problems e ectively in sustain-
able ways. Multi- level learning works to build re ection and learning
into work routines on a continuous, systematic basis so that people are
not thrust into these situations only when problems occur. Yet potential
embarrassment, face-saving, and the perception of personal threat often
lie just under the surface, even when everything appears to be working
ne. The multi- level learning coach, in his objective, substantively neutral
role, can help groups at all levels mitigate the e ects of defensive routines
by diagnosing and intervening to facilitate more e ective communication
patterns. This can enable groups to resolve problems proactively before
they snowball into larger issues, blowups, and surprises that trigger a red
light on the status report.
The Ladder of Inference (Argyris, 1990) is a model that can help us bet-
ter understand how our perceptions create a self- reinforcing loop in which
our individual beliefs in uence what information we select and hear, and
how what we select and hear in uences the actions that we subsequently
take. As people react to one another’s behavior, the Ladder of Inference
works unconsciously in the background and can explain how information
that goes untested and unvalidated in our own heads can undermine our
ability to communicate e ectively, leading to escalations in con ict and
organizational dysfunction.
We will use as an example an interaction between two people that oc-
curred on a large- scale global project that was ultimately cancelled. The
goal of the project was to select and implement an enterprisewide soft-
ware package, one that would eventually a ect thousands of employees.
The CIO of the company considered it a mission- critical project. A con ict
arose between two managers on the team. The rst was Bernard, who was
assigned the responsibility for “developing the high- level strategy.” The
second was Tracy, who was responsible for translating this strategy into
“detailed requirements.” Neither manager had done this type of project
before, and both had expressed concerns about whether or not the project
would succeed.
Bernard, having nished the high- level strategy document, said to
Tracy, “I’ve completed my part of the project plan, which was to develop