In the previous article, drawing on Argyris and Schön's work, we looked at why organizations often struggle to learn despite the importance and investment they place on training and learning programs. We saw that much of the problem lay in the gap between what organizations say they believe and the assumptions that actually guide their behavior. When that gap goes unnoticed, and when there is little room to question the mental models and practices shaping how problems are understood, learning tends to remain limited.
Previous article in this series
Why Organizations Struggle to Learn: Insights from Argyris and SchönIn this article, we build on that discussion by turning to Peter Senge’s broader perspective. Rather than focusing only on how learning happens or breaks down within organizations, Senge asks a broader question: what would an organization look like if learning were actually built into the way it operates?
This idea became known as the learning organization.
In The Fifth Discipline, Peter Senge argues that for learning to become part of how an organization actually functions, certain conditions need to be in place. Senge describes these as five disciplines: systems thinking, mental models, shared vision, personal mastery, and team learning (Senge, 1990).
Systems thinking sits at the center of Senge’s framework. He describes it as “the conceptual cornerstone of all the five learning disciplines” and “the cornerstone of how learning organizations think about their world” (Senge, 1990, p. 54). At its core, it represents a shift of mind: the ability to see complexity, recognize relationships and interdependencies, and understand an organization as a whole rather than as a collection of separate parts.
Part of developing this way of thinking involves noticing that many organizational problems are not entirely new. Across companies and industries, similar structural dynamics tend to appear again and again. The context may change, but the underlying pattern often remains familiar.
For example, across organizations we frequently see situations such as:
- a short-term solution that quietly creates a bigger problem later (Fixes that Fail)
- one team becoming increasingly successful and receiving more resources, while others gradually fall further behind (Success to the Successful)
- performance targets slowly being lowered because they have become too difficult to reach (Eroding Goals)
- addressing symptoms rather than the underlying cause, which makes the system increasingly dependent on temporary fixes (Shifting the Burden)
Senge refers to these recurring structures as systems archetypes. One of the effects of systems thinking is that people begin to recognize these patterns. Instead of treating every situation as entirely new, there is often a moment where someone thinks: “I have seen this before.”
At that point, attention shifts away from the individual event and toward the structure behind it. The focus is no longer only on what happened, but on the pattern that might be producing similar outcomes across situations. In that sense, systems thinking involves a kind of metacognitive step back.
Someone might look at a situation and think:
“This looks like a fixes-that-fail dynamic.”
“This is starting to resemble success-to-the-successful.”
▶ Illustrative Example: Fixes That Fail
A company notices that sales have started to decline and launches large discount campaigns.
Sales increase temporarily, making the strategy appear successful.
Customers begin to expect constant discounts and become less willing to buy at regular prices. The company becomes dependent on promotions to maintain revenue.
What initially looked like a solution slowly reinforces the very problem it was meant to solve.
Seen through a systems thinking lens, the situation no longer appears as a single event. It begins to resemble a familiar structural pattern, and a reminder that cause and effect are not always linear or close in time.
What makes this shift of mind difficult is that the structures we observe in organizations are closely tied to how people interpret reality in the first place.
Mental models refer to the underlying assumptions, beliefs, and taken-for-granted explanations people use to make sense of what is happening around them, very similar to the espoused theories described by Argyris and Schön. These assumptions shape how organizations interpret problems and design their systems: the goals they set, the metrics they track, the incentives they create, and the products they bring to market (Monat et al., 2020). When mental models go unquestioned, they can quietly lead to poor decisions.
That is not because people are careless. It is mostly because mental models feel so obvious from the inside. When you are operating within them, they simply look like common sense.
▸ Illustrative Example: Misleading Customer Service Metrics
A company wants to improve its customer service and sets a goal to resolve issues as quickly as possible. To support this, average call duration becomes a key performance metric and shorter calls are rewarded.
Shorter calls mean more efficient customer service.
Call center employees begin ending conversations as quickly as possible. Customers often have to call back. Over time customer satisfaction drops and the total number of incoming calls actually increases.
What went wrong? The issue is not bad intention or being careless. It is the assumption behind the metric. By equating efficiency with speed, the organization undermined the value of solving the problem during the first interaction and shifted employees' attention in the wrong direction.
In Senge's framework, shared vision refers to a collectively held sense of the future an organization wants to create. In theory this sounds powerful, but in practice it can appear somewhat idealistic. Senge suggests that a shared vision becomes meaningful when organizational goals connect with what individuals themselves care about. Rather than simply announcing a direction, the aim is to create conditions where people can see how their own aspirations relate to the organization's broader purpose.
This idea has been received some critism. Some scholars argue that expecting employees to internalize organizational goals to this degree may be unrealistic (Calhoun et al., 2015). From this perspective, it is difficult to imagine how an employee would begin to experience organizational problems as if they were their own. Senge's intention, however, is not to demand total identification with the organization, but to create conditions where people experience their work as meaningful and impactful.
In practice, shared vision is closely tied to mental models. If people within an organization interpret problems through very different assumptions, a common direction is hard to establish. For one team, success might mean cutting costs; for another, improving the customer experience. In such cases, teams may end up moving in different directions despite a formally stated vision.
▸ Illustrative Example: Two Ways Vision Is Introduced in Organizations
- The leadership team writes a vision statement during a strategy meeting
- The sentence is refined until it sounds inspiring
- It is announced at a town hall or in a company-wide email
- Slides and posters repeat the message
People understand the sentence. But it remains something the organization says rather than something people feel connected to.
- Conversations begin instead of a finished vision statement
- Teams reflect on questions such as:
- ▸ What do we want customers to experience differently because of our work?
- ▸ What kind of problems do we want to become known for solving well?
- ▸ What would make us proud of the way we work?
- ▸ What should we never compromise on, even under pressure?
- Recurring themes begin to appear across teams
- These themes gradually form the basis of a shared direction
This kind of process allows a vision to emerge from the bottom up rather than being imposed from the top down. People begin to recognize their own ideas within the emerging direction.
At the same time, these conversations make different mental models visible. Teams reveal what they actually prioritize: customer trust, product reliability, speed, cost control, or internal collaboration.
The discussion also shifts attention away from performance targets alone and toward meaning. Instead of asking only how to perform better, people begin to reflect on what kind of work they want to stand behind.
Personal mastery refers to the ongoing commitment a person has to their own growth and learning. Not in the sense of only accumulating skills or credentials, but in the deeper sense of continuously clarifying what actually matters to them and honestly assessing where they currently stand. Senge describes it as "the discipline of continually clarifying and deepening our personal vision" (Senge, 1990).
What makes this relevant for organizations is that people who practice personal mastery tend to hold their assumptions a little more loosely. They are more willing to say “I might be wrong about this” and more able to sit with uncertainty without immediately reaching for a familiar explanation.
▸ Example: Personal Mastery in Practice
A product manager has spent years working on a tool that her team built from scratch. The tool has been central to how the team operates, and she really believes in it.
When user feedback starts suggesting the tool is no longer meeting people's needs, her first instinct is to defend it, to explain why users are using it wrong, or why the feedback is coming from an edge case.
It is a very human response. The tool is tied to her identity, her effort, and her past decisions. Personal mastery does not eliminate that reaction, but it creates enough self-awareness to notice it.
Am I protecting the tool, or am I actually evaluating the evidence?
That small shift, from defending to questioning, is where learning becomes possible. In an organization full of people practicing this kind of reflection, problems surface earlier, assumptions get challenged more regularly, and feedback does not get filtered out before it reaches the people who need to hear it.
Senge describes team learning as the process through which a group develops the ability to think and act together, not just coordinate tasks, but build on each other's thinking. The foundation of this is dialogue: the kind of conversation where people suspend their assumptions and actually listen, rather than waiting for their turn to make a point.
Most professional conversations are closer to debate than dialogue. People come in with a position, present evidence for it, and try to win. That works well enough for some decisions. But for complex problems, it tends to narrow the thinking rather than expand it.
▸ Example: Debate vs. Dialogue in A Product Launch Review
A cross-functional team trying to figure out why a product launch underperformed. Each team member interprets the situation through a different lens:
Each of them has data to support their view.
The conversation ends in a compromise that no one is fully convinced by, or in whoever has the most authority getting their way.
The team stays in the discomfort of not yet knowing long enough to notice that several explanations might be partially true and that the deeper issue may be that the teams were not aligned earlier in the process.
That realization does not come from any one person. It emerges from the conversation itself. And when it does, the team is not just solving the problem in front of them. They are building the capacity to think together more effectively the next time. This is what Senge means when he says the learning of a team can exceed the learning of any individual within it.
When we look at Argyris and Schön's work together with Senge's ideas, a certain resemblance between individuals and organizations begins to appear. Organizations, much like individuals, tend to rely on familiar patterns. They repeat what has worked before, even when the situation has changed. Stepping outside those patterns can feel uncomfortable or risky.
Over time, organizations can begin to develop something like a character. Certain habits of thinking and reacting stabilize and shape how new situations are interpreted. Yet, as Argyris and Schön remind us, an organization is not simply the sum of the people inside it. Formal structures, incentives, routines, and power relations also shape what becomes possible within the system. At the same time, the strengths and limitations people bring with them do not disappear; in many ways, they become amplified and embedded in the system itself.
Because of this, the hesitation individuals feel when questioning their own assumptions can easily appear at the organizational level as well. A system may defend its familiar ways of working in much the same way a person defends a long-held belief. When that happens, learning becomes difficult for very similar reasons. The challenge, then, is not simply how to encourage learning, but how to create conditions where questioning existing patterns becomes possible.
Sometimes the first step toward systems thinking is simply asking better questions. The following reflection sheet offers a few prompts that can help teams look beyond the immediate event.
Download the systems thinking question guide (PDF)REFERENCES
Calhoun, M. A., Starbuck, W. H., & Abrahamson, E. (2015). Fads, fashions, and the fluidity of knowledge: Peter Senge’s “The Learning Organization.” Handbook of Organizational Learning and Knowledge Management, 225–248. https://doi.org/10.1002/9781119207245.ch11
Monat, J., Amissah, M., & Gannon, T. (2020). Practical applications of systems thinking to business. Systems, 8(2), 14. https://doi.org/10.3390/systems8020014
Senge, P. M. (1990). The Fifth Discipline: The Art & Practice of the Learning Organization. Random House Australia.
Comments
Post a Comment