THE BLIND MEN 1
THE BLIND MEN AND THE ELEPHANT
It was six men of Indostan
To learning much inclined,
Who went to see the Elephant
(Though all of them were blind),
That each by observation
Might satisfy his mind.
The First approached the Elephant,
And happening to fall
Against his broad and sturdy side,
At once began to bawl:
âGod bless me! but the Elephant
Is very like a wall!â
The Second, feeling of the tusk,
Cried, âHo! what have we here,
So very round and smooth and sharp?
To me âtis mighty clear
This wonder of an Elephant
Is very like a spear!â
The Third approached the animal,
And happening to take
The squirming trunk within his hands,
Thus boldly up he spake:
âI see,â quoth he, âthe Elephant
Is very like a snake!â
The Fourth reached out an eager hand,
And felt about the knee:
âWhat most this wondrous beast is like
Is mighty plain,â quoth he;
ââTis clear enough the Elephant
Is very like a tree!â
The Fifth, who chanced to touch the ear,
Said: âEâen the blindest man
Can tell what this resembles most;
Deny the fact who can,
This marvel of an Elephant
Is very like a fan!â
The Sixth no sooner had begun
About the beast to grope,
Than, seizing on the swinging tail
That fell within his scope,
âI see,â quoth he, âthe Elephant
Is very like a rope!â
And so these men of Indostan
Disputed loud and long,
Each in his own opinion
Exceeding stiff and strong,
Though each was partly in the right,
And all were in the wrong!
Moral:
So oft in theologic wars,
The disputants, I ween,
Rail on in utter ignorance
Of what each other mean,
And prate about an Elephant
Not one of them has seen!
âJohn Godfrey Saxe (1816-1887)
3
CHALLENGING OUR CERTAINTY
A revolution in project work has exploded over the last decade. Companies now create products in radically different ways than before. Instead of dedicated teams mustered to achieve reasonable goals, cross-functional, highly technical, fast-time-to-marketâ driven teams are common. Product requirements have shifted away from a definite set toward an indefinable one. Not surprisingly, product-development teams now disappoint more often than they deliver. Many more projects fail to satisfy their sponsorsâ expectations than ever satisfy them.
Most project traditions persist in spite of these fundamental changes. Most companies expect project managers to control these projects the way they controlled simpler projects in the past.
- Management lays fixed track, expecting everyone to get on it and stay on it, or get back on it should they stray.
- Funding authorities cling to traditional success criteria, expecting âon-time, on-budget, on-specâ performance, in spite of this shifting context.
- Auditors continue to expect detailed plans early in projects, even though both auditors and project managers know they will be shocked by the magnitude of the changes in them over time.
- Managers still gauge progress by inches, expecting their team members to explain every deviation from the plotted course.
I speak with a certain client every few months. Heâs spearheading his organizationâs process-improvement effort. He reports his shortcomings each time we chat. His original plan targeted a broad set of changes. A few months later, his results forced him to reduce the scope. His fallback plan called for heavy customer involvement, which the customers couldnât deliver. Heâs frustrated with his obvious lack of progress. Every time we talk, he reports that heâs working longer hours. âThis place just doesnât get it,â he says. âThe status quo seems to be winning.â
He has finally accomplished a significant toehold toward his objective, but he expected to be at the top of the cliff by now. Rather than celebrating his significant breakthroughs, he punishes himself and those around him for an obvious âlack of progress.â Of course the breakthroughs donât seem very significant when compared with what the original plan said was supposed to happen.
4
Some authors call these projects âwicked.â I think this term misses the point. James Thurber told the story of his Civil Warâ veteran grandfatherâs relationship with the automobile. His grandpa thought of his car as just another sort of horse, and a particularly stupid and unmanageable horse at that. He never learned that the automobile would not turn when told to and that cars need different guidance techniques from what horses need. He died blaming the stupid car for his accidents. Calling these projects âwickedâ duplicates Grandpa Thurberâs error. Approach them inappropriately and they instantly become wicked.
I prefer the term fuzzy. âWickedâ sounds as if our automobile has something against us. âFuzzyâ sounds indistinct without suggesting any evil motive. Like Grandpa Thurber with his Hupmobile, we turn our otherwise innocently fuzzy projects into wicked ones. Our traditions, like Grandpa Thurberâs, seem the source of what we experience as wicked:
- We create maps without surveying the territory.
- We follow these maps as if they were based upon knowledge rather than belief.
- We oblige others to follow these imaginary maps, as if following imaginary maps were reasonable.
- We promise rewards if targets are reached, as if any individual controlled the imaginary mapsâ accuracy.
- We threaten to punish those who miss targets, as if missing targets meant that someone had a personal problem or a professional shortcoming.
Our promises and threats justify a remarkable variety of inhuman acts:
- Requiring âvoluntaryâ sacrifices as if they demonstrate sincere commitment.
- Demanding obedience as if that demonstrates dedication.
- Suspecting others as if that demonstrates prudence.
- Coercing as if that could encourage people to work together.
- Punishing as if that motivates.
- âHolding feet to the fireâ as if that would entice action.
5
Misery results from these tactics more often than does project success. Until I started working in Silicon Valley, I had never met anyone making a quarter of a million dollars a year who felt taken mean advantage of by his or her employer. Iâve met several there.
We create the wickedness we experience as âwicked projects.â We do this by interpreting our experiences in ways that not only undermine our success but guarantee meaninglessness. This simple acknowledgment transforms these experiences. I am never a powerless victim unless I abrogate my authority as the author of my own meaningless experiences. I have a guaranteed never-ending search for resolution as long as I believe that this wickedness originates somewhere else. Acknowledging myself as the source gives me the power to master these difficult experiences.
But mastering means losing some of the notions that helped me feel so powerful in the past. My convictions crumble as I accept that I cannot plan predictively enough to keep myself or anyone else safe from encountering unsettling information along the way. I can be confident only that our project will not turn out as planned. Incompetence no longer explains missed obligations, nor can I guarantee success by promising juicy payoffs. My certainties have to crumble, too. I cannot manage my project as if it were a manufacturing process. Deviations arenât necessarily bad. They can signal more meaningful success.
Our projects have shifted into a world where
- Personal sacrifice wonât repel failure.
- Obedience canât attract success.
- Failure doesnât mean that anyone was untrustworthy.
- Coercion compromises capabilities.
- Punishments and enticements donât motivate.
If this shift seems scary to you, welcome to the club. It seems scary to me, too. Iâve concluded that shifting away from my confidence and my convictions should scare and confuse me. What experience could have prepared any of us for challenging our own certainties?
6
CONFUSING OURSELVES
I recently read a blurb about a new project management book. It promised to teach me how to act in order to make my projects successful. I thought, âIs this theater?â Perhaps it is.
Within that bookâs frame of reference, the project manager is the playwright, the casting director, and the acting coach. The project manager creates the script for the project. Then he acts as casting director, assigning roles and responsibilities. Then, switching roles again, he coaches his cast into following his script. The acting-coach project manager has a tool kit filled with techniques for compelling others to deliver predictable performances. He coaches by reasoning, persuading, or, if someone insists upon being unreasonable and contrary, by coercing. He assesses performance by observing behavior.
Iâve had my behavior âmanaged,â just as Iâve managed othersâ behavior. Did I really force people to behave? I suppose I did. I created a plan, a script of obligations; then I held each actorâs feet to the fire. Under these conditions, their contributions had all the juiciness of a mortgage payment. Each contribution became an obligation, when it could have been so much more. Why did I work so hard to create such mediocre results?
Most project managers bring this acting-coach frame of reference to their fuzzy projects. We might prefer something other than coercion, but what can replace this crumbling body of knowledge we call âproject managementâ? Must we continue yelling at the steering wheel like Thurberâs grandfather, unaware that we are the ones confusing ourselves when it doesnât respond?
7
CHOOSING MORE APPROPRIATE
FRAMES OF REFERENCE
Do we have to be in the behavior modification business to successfully manage projects? I have a devil of a time planning a project if I cannot predict how anyone will behave when working on it. I simplify planning if I can at least assume predictability. I can track and control more easily if everyone stays within my prescribed boundaries. But the fuzziness, the indistinctness, makes such predictions unlikely.
Methodologies attempt to shave this fuzziness from fuzzy projects by offering templates designed to make the indistinct more definite. Most work-breakdown structures must have been designed by the compulsive progeny of Frederick Winslow Taylor, the self-proclaimed father of scientific management. Taylor believed that each manager was the benevolent father of his workers; that the managerâs proper role was to allocate work according to skills and to assign workers as required by the work, while limiting the opportunities for what Taylor called âsoldieringââwhat we might call âunplanned interaction.â What passed for science when Taylor claimed his fatherhood doesnât pass for science anymore. Science advanced a century while Taylor and his now-pseudoscientific followers stood still.
Much of what we call âproject managementâ stands upon Taylorâs flat-earth perspectives. When applied to repeatable manufacturing situations, his primitive notions have great utility. The same ideas fall apart when applied in more human, less mechanical contexts. Success requires something other than simply shaving a projectâs fuzziness. Our well-intended barbering leaves us bound with unanswerable questions. We might want efficient projects, but how do we improve the efficiency of a single-instance project when efficiency can only be meaningfully considered as a function of many similar instances? We might want a good plan, but how can we create an effective script for a discovery when we cannot know at the start what weâll discover or how weâll discover it?
Our centuries-long struggle to predict our futures has come to this; innocent attempts to manage our futures create unmanageable ones, well-intended efforts to script the play undermine the purpose of the performance. Our directing guarantees mediocrity. Weâve filled our kit with tools weâre much better off not using. Our traditions mislead us into using them anyway.
8
The unpredictabilityâthe indistinctness of todayâs effortsâ had better not be a problem, because this fuzziness has become an unavoidable feature of our present and future projects. Our projectsâ fuzziness ranks as no more (or less) of a problem than Grandpa Thurberâs inability to tell his car to turn. Just like Grandpa Thurberâs, our interpretations transform a benign feature into an unresolvable shortcoming. Grandpa Thurberâs car was no more like a horse than our present projects are like past ones. It was as unreasonable for Grandpa Thurber to expect his car to behave like a horse as it is for us to expect ancient tactics to guide todayâs projects. Just like many project managers today, the old man created his own troubles by innocently overextending his frame of reference.
We each place our experiences inside such frames of reference, or frames. These frames subtly influence what we believe and how we behave. For instance, some people put driving a car into a âdriving a race carâ frame and so justify as appropriate a different set of behaviors from those of someone who puts driving into a ââchauffeurââ frame. We are usually unaware of these framesâ influence on us. We might not even experience making a choice as we step into another one.
The word project can push me unawares into a playwright/casting-director/acting-coach frame, in which I, as the project manager, automatically begin writing the script, selecting the cast, and coaching the...