Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 7, Issue 21;   May 23, 2007: Ten Reasons Why You Don't Always Get What You Measure: Part III

Ten Reasons Why You Don't Always Get What You Measure: Part III

by

The phrase "You get what you measure," has acquired the status of "truism." Yet many measurement-based initiatives have produced disappointing results. Here's Part III of an examination of the idea — a look at management's role in these surprises.

Even when measurement precedes desired results, we sometimes wonder whether the measuring caused the outcome. We've already looked at our assumptions regarding measurement itself, and at the effects of employee behavior. But management actions also raise questions about measurement-based management. Here are four examples. See Part I, and Part II for more.

The Leonard P. Zakim Bunker Hill Bridge

One of the many problems contributing to cost overruns in the highway project known as Boston's "Big Dig" was a sequence of delays in determining the design of the Charles River Crossing. Once this decision-making overran its schedule, very serious problems developed later in the project, in both management and engineering and construction. As in the private sector, the early focus of scrutiny has been on the engineering and construction rather than on management, in part because we measure them more carefully. Pictured is the Leonard P. Zakim Bunker Hill Bridge in a later construction phase, as it emerges from the Thomas P. "Tip" O'Neill Jr. Tunnel to cross the Charles River. This particular crossing is very near the one referred to as "two if by sea," in the poem, "The Midnight Ride of Paul Revere," by Longfellow (1860). Photo courtesy Massachusetts Turnpike Authority.

We tend to measure "them" rather than "us"
Measurements are relatively less likely to probe attributes of management processes than they are to probe attributes of other processes. For instance, the starting point for time-to-market measurements usually comes after the "fuzzy front end" — the part that includes concept formulation, final approval, and resource allocation — all management processes.
If we believe in the efficacy of measurement, we ought to apply it to management processes, too.
We tend not to measure the effectiveness of metrics-based management
The effectiveness of measurement depends on processes for selecting and designing metrics, collecting metrics data, analyzing it, and using the results to adjust processes. These activities are rarely measured themselves.
If metrics-based management works, it should work for the metrics approach itself. The rarity of attempts to measure the effectiveness of metrics-based management raises questions both about our commitment to the approach, and its validity.
Measurement fatigue
When people adapt to measurement, they find ways to limit the controlling effects of the measurement. The organization then returns to Square Two, which is just like Square One, except for the added burden of reporting (and evading the effects of) the metric. Typically, organizations respond by introducing another metric to "control" the evasion problem.
In this way, an organization acquires a steadily increasing burden of (mostly) ineffective metrology, which eases only with a reorg, or the arrival of a new high-level manager, or an acquisition, or clean-sheet re-engineering, or major downsizing or bankruptcy.
You can't always get what you want
Measurement doesn't help
much if employees are
unable to produce
the desired results
due to forces outside
their control
Even when we measure what we want to get, we might not be providing the resources needed to achieve it. Employees might simply be unable to produce the desired results, because of forces outside their control, physical laws, government laws and regulations, inadequate resources, deficits in skills or knowledge, toxic culture, wrong knowledge, ineffective management, or other factors.
For instance, producing tight-tolerance parts with worn-out, outdated equipment is unlikely to work, no matter what you measure. Altered employee behavior just isn't the answer, and no amount of measuring the output will "encourage" them to do well enough.

And so it appears that there are ample reasons to explain the disappointing results of measurement-based management. Perhaps more puzzling is why the practice persists, and why it's so widely used. Other intriguing questions: When is measurement useful? When does measurement have the effect we hope for? I'll leave these questions for another time. Go to top Top  Next issue: Snares at Work  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Your comments are welcome

Would you like to see your comments posted here? rbrenVlvFsJkdKzTgNXxAner@ChacmPGPbAhtinwnTrbMoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

A late rabbitGames for Meetings: Part III
We spend a lot of time and emotional energy in meetings, much of it engaged in any of dozens of ritualized games. Here's Part III of a little catalog of some of our favorites, and what we could do about them.
A team raises a wall of a new home sponsored by the U.S. Department of Housing and Urban DevelopmentWorkplace Barn Raisings
Until about 75 years ago, barn raising was a common custom in the rural United States. People came together from all parts of the community to help construct one family's barn. Although the custom has largely disappeared in rural communities, we can still benefit from the barn raising approach in problem-solving organizations.
Senator Susan Collins of MaineDiscussion Distractions: Part I
Meetings could be far more productive, if only we could learn to recognize and prevent the distractions that lead us off topic and into the woods. Here is Part I of a small catalog of distractions frequently seen in meetings.
A pair of adult trumpeter swansFinding Work in Tough Times: Marketing
We aren't accustomed to thinking of finding work in tough times as a marketing problem, but it helps. Here are some suggestions for applying marketing principles to finding work in tough times.
Henri Laurence Gantt, inventor of the Gantt ChartThe Tyranny of Singular Nouns
When groups try to reach decisions, and the issue in question has a name that suggests a unitary concept, such as "policy," they sometimes collectively assume that they're required to find a one-size-fits-all solution. This assumption leads to poor decisions when one-size-fits-all isn't actually required.

See also Personal, Team, and Organizational Effectiveness and Critical Thinking at Work for more related articles.

Forthcoming issues of Point Lookout

A vizsla in a pose called the play bowComing April 26: Why Dogs Make the Best Teammates
Dogs make great teammates. It's in their constitutions. We can learn a lot from dogs about being good teammates. Available here and by RSS on April 26.
A business meetingAnd on May 3: Start the Meeting with a Check-In
Check-ins give meeting attendees a chance to express satisfaction or surface concerns about how things are going. They're a valuable aid to groups that want to stay on course, or get back on course when needed. Available here and by RSS on May 3.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenBBnThXQCOeTwLNAKner@ChacrGIDXwNnAErORqQcoCanyon.com or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

Changing How We Change: The Essence of Agility
MasteChanging How We Change: The Essence of Agilityry of the ability to adapt to unpredictable and changing circumstances is one way of understanding the success of Agile methodologies for product development. Applying the principles of Change Mastery, we can provide the analogous benefits in a larger arena. By exploring strategies and tactics for enhancing both the resilience and adaptability of projects and portfolios, we show why agile methodologies are so powerful, and how to extend them beyond product development to efforts of all kinds. Read more about this program. Here's an upcoming date for this program:

Creating High Performance Virtual Teams
Many Creating High Performance Virtual Teamspeople experience virtual teams as awkward, slow, and sometimes frustrating. Even when most team members hail from the same nation or culture, and even when they all speak the same language, geographic dispersion or the presence of employees from multiple enterprises is often enough to exclude all possibility of high performance. The problem is that we lead, manage, and support virtual teams in ways that are too much like the way we lead, manage, and support co-located teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance. Read more about this program. Here's an upcoming date for this program:

The Race to the South Pole: Ten Lessons for Project Managers
On 14The Race to the Pole: Ten Lessons for Project Managers December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
21st Century Business TravelAre your business trips long chains of stressful misadventures? Have you ever wondered if there's a better way to get from here to there relaxed and refreshed? First class travel is one alternative, but you can do almost as well (without the high costs) if you know the tricks of the masters of 21st-century e-enabled business travel…
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.