The Blind Men and the Elephant
The fable illustrates that individuals often perceive only part of a complex reality, leading to incomplete understanding and conflict; to grasp the whole, one must be open to others' perspectives and understand how parts interact.
THE IDEA
The Blind Men and the Elephant
In the fable of ‘The Blind Men and the Elephant’, most of us recall that several blind men approach an elephant for the first time. (1) After touching parts of the elephant, the blind men discuss their felt experience and try to make sense of it. Each man had a different experience. One associated the elephant’s tusk with a spear, another, the trunk with a snake, and yet another the ear with a fan. After discussing each other’s experience, the blind men tried to reach consensus as to what this creature was.
The fable ends with the blind men being unable to reach any consensus on what the elephant is. Each man understood one part of the elephant, but no one individual understood the whole. As explained by Mintzberg et al: “Since no one has had the vision to see the entire beast, everyone has grabbed hold of some part or other and ‘railed on in utter ignorance’ about the rest. We certainly do not get an elephant by adding up its parts.”(1) The fable invites people to compare partial observations and examine how the parts interact. Combining viewpoints can reveal missing connections, though agreement alone does not establish that the resulting explanation is correct.
When to use it
In team decision-making, to encourage diverse viewpoints and avoid groupthink.
When analyzing a business problem, to consider all functions (marketing, finance, operations).
During conflict resolution, to help each party appreciate the other's perspective.
In systems thinking, to understand that the whole is more than the sum of its parts.
FROM THEORY TO EVERYDAY LIFE
In practice
Product Development Disagreement
A company is developing a new smartphone. Marketing focuses on customer desires (camera quality), engineering on technical feasibility (battery life), and finance on cost reduction. Each team argues for their priority, but without a holistic view balancing all factors, the product may fail to satisfy the market.
Fable's Lesson in a Team Meeting
In a project review, designers point to delays in testing while testers point to buggy code. Comparing the timeline, requirements, and dependencies reveals that ambiguous requirements contributed to both problems. Sharing perspectives helps the team investigate a connection that neither account had established alone.
A MOMENT TO REFLECT
Put it to work.
Which perspectives or relationships might be missing from your current account of a complex problem?
Think of a recent disagreement where each party had a valid but partial view. How could you have integrated those views?
In what situations might you be acting like one of the blind men, and how could you widen your perspective?
CONTINUE THE CONVERSATION
Source texts
- Cynefin - Weaving Sense-Making into the Fabric of Our World ED02 (Dave Snowden Sonja Blignaut Zhen Goh)