It looks like nothing was found at this location. Maybe try a search or browse one of our posts below.

Service levels, you’ll recall, are two-part measures. They define a minimum threshold of acceptable performance and tally how often a service provider meets or exceeds it.

Enter the Pew Research Center for the People & the Press. In an excellent example of service levels in action, it defined a minimum threshold of acceptable knowledge of current events –getting two thirds of a questionnaire right (sample question: Who is the current Vice President of the United States of America?).

Then it tallied how many of those surveyed met the threshold.

Pew found, perhaps unsurprisingly, that those who watch The Daily Show and The Colbert Report on the Comedy Channel tied regular newspaper readers for top honors (54%). Those who watch Fox News met the standard 33% of the time, outperforming only watchers of network morning programs. Draw your own conclusions.

It’s tempting to blame this mess on intellectually lazy Americans, Katie Couric, Roger Ailes, or all of the above. Temptation being what it is, I will.

Underneath the symptoms, though, is a challenge you and I face every day as we deal with vendors, staff, managers, vendors, information outlets, colleagues, and vendors in the workaday world of information technology: The challenge of seeing what isn’t there.

To illustrate the point, go back to last week’s column, which described Factcheck.org’s critique of a current U.S. Chamber of Commerce ad. The ad provides an alarming statistic — that lawsuit abuse costs your family $3,500 per year.

I received quite a few e-mails challenging my statement that the U.S. Chamber … well, I said it was lying. The e-mails pointed out that the Chamber’s math was perfect. Lawsuits did cost $235 billion in 2005 and that this does come out to $3,500 per family, if you assume an average headcount of four (bad assumption, by the way).

The problem with the ad isn’t what it said. It’s what it left out — what isn’t there. It left out:

  • How the Chamber defines “lawsuit abuse” (apparently, it’s “filing a lawsuit for any reason at all”).
  • What fraction of all lawsuits falls into the “lawsuit abuse” category (close to 100%).
  • How those who paid the legal fees and fines managed to transfer their costs to your family (and wouldn’t that make for a popular seminar?).

It’s far easier to deceive through omission than through falsification. Omission is far harder to spot.

In your professional capacity you’re inundated with product specifications and performance statistics, staff reports and recommendations, project proposals and justifications, all trying to persuade you to do something or other. If you’re like me you’ve become adept at skimming them to get the gist of what they’re trying to tell you.

Gist is a useful substance, right up there with beef jerky and Maxalt. It has its limitations, though, and top among them is that gist doesn’t help you spot what isn’t there. Quite the opposite. Gist is for understanding what someone is trying to tell you. As a result, it helps them conceal much more than it helps you reveal.

If there’s a magic formula for spotting what isn’t there I’m not aware of it. I do have favorite examples. Here’s one:

Imagine you asked a vendor if HP supports Vista for its 2840 color laser multifunction device (to take an example at random — that I happen to own one is sheer coincidence). Imagine the vendor answered in the affirmative.

The answer would be true. It would also be seriously deceptive. You can get a 2840 driver on HP’s website … which works for USB-attached devices but not network-attached ones. You can also download HP’s admirably conceived Universal Print Driver (UPD). It lets you print to the 2840 through either a USB or a network connection.

But only in black and white, and it doesn’t support the scanning function.

Phrasing your question to be in a position to accurately evaluate the product is something of a challenge.

How do you spot what’s missing? First, don’t skim — read carefully. Second, apply your experience. Think about all the ways you’ve been deceived in the past, look for parallels, and ask about them.

And third, don’t try to be clever. This question isn’t at all clever: “Here’s what I’m trying to accomplish. How will your products help me do it? Tell me step by step.” It might not be clever, but it gets the job done.

Of course, to ask this you do have to know what you’re trying to accomplish.

Privilege means, literally, “private law.” If most of us are honest, we want it for ourselves and resent it in others.

The political philosopher John Rawls proposed that a fair and just a society is one whose rules each of us would endorse without knowing in advance what position we would occupy in it. Privilege is the alternative: A society whose rules are designed by some for their own advantage.

The distinction between privilege and a just social design is just one of the reasons the tired proposition that “government should be run like a business” is fallacious. Government is an instrument of society. Its first responsibility is to be fair, and only after that is it allowed to be efficient. The practicalities of running a competitive business, in contrast, mean fairness takes a back seat to efficiency.

Which is to say, government should be run in a business-like way, but shouldn’t be run as a business. Businesses should be run as fairly as possible, but not at the expense of competitiveness.

What does this mean to you?

When an organization defines its governance — how it goes about making decisions — it generally comes down to one of two alternatives. It can make them through relationships and personal judgment, or it can make them through processes and well-defined rules. Decision-making through relationships and judgment is quick and efficient. Decision-making through processes and rules is deliberate, consistent, and fair.

That’s how the proponents of each would state the case. Their detractors would claim, respectively, that when you make decisions through relationships and judgment you’ve instituted a system based on privilege; systems based on processes and rules are bureaucracies.

One of your most important responsibilities as an IT leader is establishing how decisions will be made. What’s it going to be? Privilege or bureaucracy? Efficiency or fairness?

There is no single right answer; no “best practice” that will save you from having to make a very difficult set of trade-offs.

The first place to look is at how many people are involved. If you run a small IT shop — say you have five people reporting to you — then everyone knows everyone. It’s easy to talk over a problem and come to an equitable solution.

Now imagine you’re responsible for five hundred people instead. Five hundred people can’t easily talk things over, so instead you establish clear rules and criteria through which you’ll make decisions, and a well-defined process for applying them. That’ll solve the problem, won’t it?

Only if no actual human beings are involved. Once you add people to the system it isn’t that simple. As anyone who has written a capital proposal knows, you always include the obligatory paragraph that explains why your idea is consistent with the company’s business strategy, regardless of the strategy and the idea.

So your process has to include a due diligence component, to ensure proposals are what they say they are. Voila! you’ve created bureaucracy.

The crucial element that’s missing when you try to make decisions through a fair process is trust. When you have few enough people involved that everyone knows everyone else, you can evaluate ideas in the context of your trust of their source. That’s just one reason so many leaders, faced with organizational growth, prefer to create an inner circle to a system of rules and processes: It’s a lot easier, and probably safer, to trust people you know than to trust a system that treats close friends and total strangers equally. Faced with decisions, these leaders convene their inner circle. The system is for people they don’t know personally — their friends live by a different, private set of rules.

In a word, they’re privileged.

This isn’t necessarily a bad thing. Say it again: The first responsibility of business is to be competitive. Businesses should be as fair as they can without losing that, and while creating privilege for those you know sounds improper, trusting the motivation and judgment of strangers just as much as those of people with whom you’ve worked closely is naive. You don’t build success on naivete.

The secret is to maintain your balance. With no inner circle you’ll run an ineffective bureaucracy; worse, you’ll consider all ideas to be equal. And intellectual relativism, while a growing social trend, is, simply put, stupid.

But too often, the inner circle, being inner, starts to think it can ignore everyone else. That’s a problem, and a very common one: Privilege begets ignorance among the privileged.

And you’re even less likely to build success on that.

* * *

Credit where it’s due: I first encountered the etymology of “privilege” in one of Terry Pratchett’s fine Diskworld novels, all of which are worth the time spent in their reading.