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.
- 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
- 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. Top Next Issue
Are 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 welcomeWould you like to see your comments posted here? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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.
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.
More articles on Personal, Team, and Organizational Effectiveness:
- Appreciate Differences
- In group problem solving, diversity of opinion and healthy, reasoned debate ensure that our conclusions
take into account all the difficulties we can anticipate. Lock-step thinking — and limited debate
— expose us to the risk of unanticipated risk.
- Keep a Not-To-Do List
- Unless you execute all your action items immediately, they probably end up on your To-Do list. Since
they're a source of stress, you'll feel better if you can find a way to avoid acquiring them. Having
a Not-To-Do list reminds you that some things are really not your problem.
- Think Before You PowerPoint
- Microsoft PowerPoint is a useful tool. Many of us use it daily to create presentations that guide meetings
or focus discussions. Like all tools, it can be abused — it can be a substitute for constructive
dialog, and even for thought. What can we do about PowerPoint abuse?
- Workplace 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
- Four Popular Ways to Mismanage Layoffs: I
- When layoffs are necessary, the problems they are meant to address are sometimes exacerbated by mismanagement
of the layoff itself. Here is Part I of a discussion of four common patterns of mismanagement, and some
suggestions for those managers and other employees who recognize the patterns in their own companies.
Forthcoming issues of Point Lookout
- Coming January 22: Disjoint Awareness: Bias
- Some cognitive biases can cause people in collaborations to have inaccurate understandings of what each other is doing. Confirmation bias and self-serving bias are two examples of cognitive biases that can contribute to disjoint awareness in some situations. Available here and by RSS on January 22.
- And on January 29: Higher-Velocity Problem Definition
- Typical approaches to shortening time-to-market for new products usually involve accelerating problem solving. Accelerating problem definition can also help. Available here and by RSS on January 29.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
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
- The Power Affect: How We Express Our Personal Power
Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.