Ever since mass acceptance of the personal computer, its proponents have sold it on how much it would improve productivity in the workplace. Ever since, economists and accountants have tried to find the productivity gains, without much success.

Try to take away employees’ PCs, though, and you’ll have the same success you’d have removing rifles from NRA members – you’d have to pry it from their cold, dead fingers. Hence, the “paradox.”
We’ve been talking about measures for the last several columns, and it seems appropriate to wrap up the subject (for now) with a column on productivity and how to measure it.

Step 1: Make sure productivity is a useful thing to measure.

The plain fact is, productivity just doesn’t apply to every role in an organization. That’s why so many intelligent and ingenious people have tried to develop white-collar productivity measures and failed.
When you measure productivity, you’re measuring how much stuff a person, group, or machine can make in a unit of time. Widgets per hour. Applications per day. Pages per minute.

Productivity only matters in repetitive processes that produce or handle similar items. The concept comes from factory work. A factory manufactures a particular kind of thing, and lots of it. The more things it produces in the same amount of time, the smaller the capital and labor cost of each item. That translates to lower prices and higher margins, both Good Things (to use the jargon of Economics).

Some white collar jobs do involve repetitive processes. Call centers, insurance claims processing, mortgage application processing, all have a lot in common with factory work. And in fact, automation demonstrably increases productivity in these areas.

Interactive voice response systems demonstrably generate 400%+ returns on investment. Just the screen-pop feature of computer telephone integration can shave 15 seconds from each telephone call – often a 5 to 10% productivity improvement. Some imaging and workflow systems have literally doubled claims-processing productivity. Measurably.

The only repetitive process in many jobs, though, is attending meetings.

To prove the point, let’s take the ultimate example: a Hollywood screenwriter. Let’s devise a good productivity measure – I know, words typed per minute! Yup, when we make a movie, let’s get our script from the fastest typist.

Well, I don’t know how fast Steven Spielberg and his friends type, and I don’t care. Productivity doesn’t matter at all. Audience appeal is what matters, and guess what? You just can’t devise an objective measure to predict it. You have to rely on judgment.

Productivity is just one measure of Effectiveness, a more general measure of value. For a factory worker the two are more or less synonymous. For a screenwriter, productivity has nothing to do with effectiveness.

That’s one reason we’ve failed to find any productivity improvements from the introduction of computers to the workplace – we’re measuring the wrong thing. What we need are measures of effectiveness, and we have to realize a nasty little fact: often, the only measures of effectiveness are subjective.

There’s another reason for the productivity paradox. Technology has enabled a complete transformation of the workplace. People type their own memos rather than dictating them and running them through several manual revisions. Often, they write e-mail messages instead and dispatch them immediately rather than printing anything at all.

Financial analysis now involves graphing dozens of variations of a financial model instead of running a paper tape three times to make sure you keyed numbers in right.

Research now involves searching on-line databases and the Internet, instead of making trips to the library or asking your company librarian for help.

Basically, the jobs we hold now may have the same titles as 15 years ago, but they have little in common.

Statisticians call this “non-stationary data” and they don’t let you use it in analyzing trends. (I was hoping to use a related term – heteroskedasticity – but couldn’t work it in. Maybe next time.)

Productivity paradox? I don’t really care if I’m productive at all. I care how effective I am. That’s what you should care about, too.

It’s re-run time. This week’s presents the three principles IT managers (and, for that matter, non-IT managers) need most if they’re going to do their jobs well.

It is, by the way, the first “IS Survival Guide” ever published. It appeared in InfoWorld January 8, 1996, and I’m delighted to report that even after twenty years, if you’re going to limit things to just three management principles I can’t come up with a better list.

– Bob

KJR News Line

Welcome to the IS Survival Guide, the column that asks, “How can anyone succeed at such a bizarre job?”

You’re responsible for technology traditional IS executives still wish would just go away. You manage the most eccentric employees in the company. You deal with vendors who constantly use terms like partnership and value-added. And while this all goes on, you end up on five committees to advance the management long-term-direction-of-the-year.

Think of this column as management with an edge.

You won’t find any 7-S Paradigms here. No facile graphs that encapsulate a whole industry into four quadrants. No seductive alternatives to the hard work of being an effective manager. No panaceas.

Here’s what you will get: Suggestions and ideas that come from years of real management and executive experience managing technology; conversations with other managers and executives; discussions and debates with consultants, writers and academics; and just plain reading and thinking.

A lot comes from real-world experience of what works well. A lot more comes from real-world experience of what didn’t work so well.

Let’s get started.

The Three Principles of Management

A lot of management comes down to just three basic principles. Understanding them is easy. Applying them is harder. They are:

  • Customers — paying, external customers — define value.
  • Form follows function.
  • Everyone involved must be aligned to a common purpose.

When things go seriously wrong, you usually find something that violates one or more of these simple propositions.

Future columns will often touch back to these principles. Some will cover them in depth. Here are the Cliff’s Notes.

Customers

Customers define value, by exchanging something else they value — money — for your product or service. (A commonly misused term, value-added, is simply the difference between the cost of raw materials and revenue from goods sold.)

Paying customers define value. Internal customers (a nasty oxymoron) do not define value (or quality, which is just one component of value). How can they, when they don’t pay.

The usual definition — anybody whose inbox receives the contents of your outbox — reveals the core fallacy. Customers make buying decisions. And unless your internal customers establish your capital and operating budget, they aren’t the people who make the buying decisions for your products and services.

Always find a way to link your priorities and plans to paying, external customers, or at least to the hot-buttons of your company’s top executives.

Form Follows Function

Well this should be obvious, and it is — when engineers design machines. Designers of organizations fail miserably at it. Compensation plans frequently encourage employee behavior that’s at odds with the organization’s goals. Accounting techniques encourage obstructive bureaucracies and political infighting. When we measure performance at all, we measure what’s easy to measure, not what we care about.
Usually, violations of the FFF principle stem from asking the wrong question. For example, “Should our analysts have an incentive plan?” The right questions: “How do we want our analysts to behave? How do we measure that behavior? How should we reflect its value in our compensation plan?”

Aligning Everyone to a Common Purpose

Well of course, but we have internal customers. Our job is to satisfy them. Somebody else deals with paying customers.

Unless every part of your organization embraces the same externally focused goal, your company’s products and services will lack focus and cohesion. That includes you. Here’s a test: what’s your industry? Information Systems? Or the marketplace your company participates in?

Request for Submissions

I’m collecting examples of ManagementSpeak (ManagementSpeak: “I’m not saying no, but I’m certainly not saying yes.” Translation: “No.”). I’ll publish the winners (and their definitions) in future columns.

Welcome to the IS Survival Guide. I hope you find it valuable.