Paul Glen: Even if you can't measure it, you still must manage it
Computerworld - The other day, after speaking to an audience of technical people about the importance of building good relationships at work, a young help desk manager asked, "What metrics should I monitor for that?" I realized that he was trying to reconcile the importance
of relationships with a conflicting tenet of his managerial faith that says, "If you can't measure it, you can't manage it."
We geeks love that idea. It meshes with our preference for objectively verifiable facts over squishy subjectivity. We find metrics comforting, having been taught to expect constant feedback on the question "How am I doing?" We get grades on tests and papers. We get scores in video games. We get raises and promotions at work.
But our ardor for this explicit feedback loop can lead us astray. We take it too far, transforming the not-meant-to-be-taken-literally "If you can't measure it, you can't manage it" into the absurd dogma "If you can't measure it, it doesn't matter."
With that mantra as our lodestar, we not only ignore hard-to-measure aspects of work such as relationships, but also self-righteously see that approach as a virtue. You can see this mindset play out in numerous destructive ways. Project leaders become obsessed with the process-prescribed approvals while ignoring the mutual trust required to get them. Technical leaders abrasively condescend to users or sponsors, since "they don't get it." Developers adhere to the precise content of a requirements document -- as if ticking off 100% of the requirements is more important than making sure the product makes sense -- and they end up delivering unusable code.
A more appropriate mantra would be, "Even if you can't measure it, you're still responsible for it." That's because some things, like relationships, are too important to be ignored but too subjective to be measured.
For those important things that metrics can't quantify, you need to use indicators. Indicators are metrics' cousins. Where metrics quantify observable facts that are very closely related to what you want to measure, such as production rates, indicators are less precise and more indirect. They are observable facts, but they can serve only as a proxy to suggest how you're doing on something fundamentally unmeasurable.
For example, there really is no metric for directly measuring the quality of your relationship with your project sponsor. But there are indirect indicators that help you assess that relationship. You could get a reasonable impression by asking questions such as these:
Does she respond to my emails?
Does she show up at our meetings prepared?
Does she seek my opinion before making important decisions?
Does she share information with me?
Does she invite me to meetings that I feel I should attend?
Relationships don't come with dials and dashboards, and only a true geek would need to be told that it would be counterproductive to try to quantify the answers to such questions and plot them on a graph. Instead, you should use the answers as indicators that can move you closer to something that feels like metrics, but you need to internalize such information and let your gut tell you whether your relationship is healthy or not.
Well-chosen indicators will help you manage the unmeasurable, and that can be immeasurably important.
Paul Glen, CEO of Leading Geeks, is devoted to clarifying the murky world of human emotion for people who gravitate toward concrete thinking. His newest book is 8 Steps to Restoring Client Trust: A Professional's Guide to Managing Client Conflict. You can contact him at firstname.lastname@example.org.
More by Paul Glen
- Paul Glen: The most important career question you've never even considered
- Paul Glen: Techies and users are in a vicious circle of mistrust
- Paul Glen: The benefits of an unstructured career
- Paul Glen: Motivating the mercenaries
- Paul Glen: The gifts and costs of working with 'them'
- Paul Glen: How can you wield influence if you don't know what it is?
- Paul Glen: For geeks, avoiding blame is a silent career killer
- Paul Glen: When you've had it with a stakeholder
- Paul Glen: Nobody wants you to be a technology vending machine
- Paul Glen: Geeks love problems, so give them some
Read more about Management in Computerworld's Management Topic Center.
- IT Skills Proficiency Tool This tool helps you determine if your team has the right skill sets and what gaps need to be filled. By evaluating your...
- Agility & Scalability for Oracle EBS R12 and RAC on VMware vSphere 5 This white paper outlines extensive performance and scalability testing of Oracle EBS applications on a Vblock™ Systems with vSphere 5.
- Oracle and VCE: The Next Step in Integrated Computing Platforms In this ESG Lab review you will learn how a VCE system driven by Oracle, delivers the perfect blend of high performance and...
- Migrate Oracle Apps from RISC/UNIX to Virtualized x86 Ready to move Oracle to a virtualized environment? This brief explains how true converged infrastructure can help you migrate from a RISC/UNIX environment...
- Top 4 Digital Signage Fails Join RMG Networks for a look at four of the most common reasons digital signage fails in corporate businesses. Learn about strategies to...
- Geek's Guide to Presenting to Business People Watch this on-demand webinar with Paul Glen, author of "Leading Geeks," to learn how to effectively introduce technical initiatives to non-technical users (executives... All Project Management White Papers | Webcasts