One fringe benefit of public speaking is meeting friends I never knew I had.

So it happened when I gave a luncheon speech recently at LawNet, an association for CIOs and IS managers who work for law firms.

You think you have a tough gig? Imagine having no status and no hope of promotion (only lawyers become partners). Imagine having no real company strategy to use in setting priorities, only 20 bosses, each with a priority du jour. Imagine technology being a key competitive differentiator, specifically asked for in requests for proposals but effectively ignored by your firm’s fragmented executive leadership.

After I’d spent an hour babbling about electric fish, prairie chickens, evolution, and IS management, I talked with dozens of LawNet members, many of whom regaled me with anecdotes about bad managers. Bad managers don’t, of course, outnumber good ones, but they sure stick more in people’s minds and craws.

My e-mail reinforces this conclusion. When I write about bad managers I get megabytes of “me too” letters; writing in defense of managers and executives yields the kind and volume of messages usually reserved for commentaries on operating systems or Bill Gates.

Memories of bad managers last longer than memories of good ones and create expectations that the next manager will be just as bad or worse. That, I guess, is how evolution wired us: Failure to anticipate an adverse situation can keep our genes out of the next generation, whereas failure to anticipate a positive event simply leads to a pleasant surprise.

IS Survival Guide is about managing staff well. It’s also about being effective in your job and about how to have a successful career. Managing staff well means building teams and nurturing employees so they can succeed. Managing effectively means getting the resources and decisions needed to accomplish your goals and get the job done. You measure success through career advancement.

These three dimensions of management aren’t intrinsically linked — aligning them takes deliberate effort on the part of company leadership. Sadly, managers can be successful without managing staff well or being effective, because many, and perhaps most, companies are structured so managers have plenty of power to filter information as it rises in the executive hierarchy.

You manage in four directions: down to your staff; sideways to recipients of the services you provide; sideways again to your peers and rivals in the company; and up to the executives above you. In my experience some managers are good at managing staff and service recipients; others excel at managing peers and organizational superiors. Very few are good at all four.

If you want to manage your staff well, be effective, and have a successful career, you have to master all four directions.

You also have to reconcile the three dimensions of management in your day-to-day job. I don’t care how much of a political rat’s nest you work in — good managers insulate the people who work for them from the politics in the rest of the company. Running interference for your employees is, in fact, a key part of your job.

That doesn’t mean you’re allowed to be so naive that you ignore your political environment. Your staff can’t succeed without the resources it needs to do its job. If you’re ineffective, everyone who works for you will be frustrated and ineffective as well, no matter how good a manager you are.

Your success, of course, depends on your ambition, your ability to “manage up”, and dumb luck.

If you want to succeed, or, for that matter, just be an effective manager, you’ll have to play some stupid political games. That’s OK: There’s one thing worse than playing stupid political games, and that’s losing them.

There’s an old joke about a farmer who loans his mule to a friend. The mule will work hard if treated well, he explains. All you have to do is speak gently and the mule will do what you need it to do.

His friend tries it out, but the mule won’t do anything – it just sits in its stall taking up space and food. When the owner comes back his friend complains that the mule wouldn’t work at all.

Puzzled, the owner picks up a two by four and starts whacking the mule about the head and shoulders.

“I thought all you had to do is to speak gently,” his friend said to him.

“Well sure, but first you have to get its attention,” explained the farmer.

The joke isn’t all that funny, but the punch line can be used in a wide variety of circumstances. It probably explains, for example, the exorbitant estimates bandied about for the Total Cost of Ownership (TCO) of a personal computer. The promoters of these ridiculous estimates are just trying to get your attention.

This is the last of our three-part series on the subject. The column two weeks ago showed that TCO asks the wrong question — TCO adds together part, but not all, of three independent statistics — costs associated with improvements to personal productivity and effectiveness, with improvements in communications, and with the automation of company core processes (that is, development and deployment of production application systems).

Last week’s column focused on the statistic you should care about the most: the fixed overhead costs (Personal Computer Overhead Costs, or PCOC) associated with LAN-attached personal computers. PCOC, it appears, comes to about $3,000 per year.

We’re going to wrap things up this week by looking at the number you may have thought TCO measured: The cost of personal computing. Personal computing is the term we’ll use to cover the use of word processors, electronic spreadsheets, personal information managers and stuff like that — software designed to enhance personal productivity and effectiveness.

It’s tempting to calculate a total cost for this category, but it would be a mistake for two reasons. First, the benefits, while huge, defy quantification. (The proof: PCs have completely transformed the workplace — not one PC-enabled job looks remotely like what equivalent employees did 15 years ago.) Comparing quantitative costs with qualitative benefits can tie your brain into knots.

Just as important, these are variable costs — they go up with usage. Your goal when dealing with variable costs should be to reduce unit cost, not total cost. And the cost we’re interested in isn’t the cost of personal computing itself — it’s the cost of the work supported by personal computing (since that’s where the benefit comes in). Let’s walk through an example.

Figure an average employee gets one day each year of formal training, another full day of support, and loses two full days each year just figuring out how to do stuff. Including the employee’s time and that of support staff at a standard rate of $40/hour (a reasonable fully loaded cost for a $50,000 per year employee), that comes to about $1,600 per year. Allocate a third of the PCOC cost to this category of benefit (the other two thirds goes to the other uses of a PC) and you come to a total annual cost of $2,600 per employee for improved personal productivity and effectiveness.

Let’s figure about half of the employee’s total work — about 1,000 hours per year — is improved through personal computing. That makes the unit cost of personal computing about $2.60 per hour. Expressed as a percentage it comes to an overhead cost of 6.5% of the work affected.

Here’s a wild guess: personal computing leads to improvements in productivity and effectiveness that vastly exceed 6.5%. Reduce your support costs? Sure — so long as it has no deleterious impact on the employees you support.