Let’s play Connect-the-Dots.

Here’s a direct quote from Ray Lane, president and COO of Oracle Corporation, reported in the January 1st issue of Solutions Integrator: “The NC (network computer) is worthless without Oracle8.”

Dot 1: The network computer, a great new platform that’s supposed to free us from the tyranny of the so-called “Wintel Duopoly” by being fully buzzword compliant — open, scalable, thin-client, and all the rest.

Dot 2: Only it isn’t really open, since you can only develop applications in a single language, namely Java.

Dot 3: It isn’t thin-client no matter how you define the term, since the NC executes whatever code the server sends it, fat, thin, muscular, anemic, or bug-laden.

Dot 4: Scalable? Sure, if you’re willing to scale your network to colossal data rates and invest in ever-bigger servers.

Dot 5: Ray Lane, speaking for the company that first articulated the concept of the NC, saying it won’t work without Oracle8. I guess that “open” thing is a goner, too.

What Lane meant, of course, was that Oracle8 is a fine server platform for NCs, not that it’s the only one. What he told you is something more: Oracle invented the NC for one reason and one reason only — to sell Oracle’s server products. He also told you that Oracle is willing to, shall we say, engage in a wee bit o’ puffery in accomplishing that mission.

No surprises here. Anyone who thought Oracle’s Larry Ellison had any other reason for developing and articulating the NC lives in the kind of dream world where we all just get along and predators eat garden greens for supper because carnivory causes prey to feel too much pain.

The world of commerce resembles a complex, multi-player chess game. Some participants play deeper games than others. Bill Gates, like Bobby Fischer, is a master of the combination, while others (pick any MBA-run company you like) employ positional strategies.

You’ll benefit by evaluating your personal situation with the same conceptual tools. You have goals — programs you sponsor and want to complete, career aspirations you want to satisfy, proteges you’re helping succeed. Your colleagues — managers, peers, service recipients and staff — all have the same.

You’re all playing the same game. You may play audaciously or with caution. You may play forthrightly or with guile. You can no more avoid playing the game, though, than you can find a place with a different gravitational constant — choosing to not play simply means playing blindly and at random.

Even if you prefer to just do your job, you still benefit by playing connect-the-dots with your colleagues. Evaluate what each player says and does, and figure out how they benefit from the results.

There’s nothing wrong with assuming your coworkers are motivated by self-interest rather than the good of the company. Two decades ago, Richard Dawkins wrote a book titled The Selfish Gene, which demonstrated that at a deep evolutionary level, organisms are a gene’s way of making more genes. In part, he justified this perspective by applying game theory to how genes can succeed.

Like Dawkins’ organisms, companies are simply convenient, ephemeral constructions that exist in order to transfer wealth to their owners and employees. Your “selfish” coworkers, like Dawkins’ selfish genes, are doing exactly what they’re supposed to do, and the theory of games applies to them (and you) too.

As a result, alignment between stakeholder benefits and company health is far from automatic. If you work in a place where they do align, you’re lucky — you can advance your career the easy way, by doing what’s best for the company.

Regardless, maintain your sense of personal integrity, provide value for the company’s customers, and help your employees succeed, because that’s the right thing to do and it’s personally satisfying. But like it or not, you’re still playing the game. And because you are, you may as well play to win.

I’ve held nearly every job you can hold in IS, and in twenty years I’ve never worn a pager.

Some of this was dumb luck. When I worked as a programmer, for example, none of the applications I supported ran as overnight batch jobs, so that eliminated one source of pager-itis.

For the most part, though, I carefully planned my freedom from being on-call. When I managed networks and telecommunications, for example, I remained pager-free, even though we ran a 24×7 mission-critical operation. How?

Every time the subject came up I asked the same question: “What would I do about it?”

The team always had analysts on-call if something went wrong. They wore pagers. I slept until the next morning.

“What if they need you for something?” one of my colleagues once asked.

“Like what?” I asked in return. “They know what needs to be done, they’ll make the right decisions, and if anyone questions their authority they can explain that they had no choice — they couldn’t reach me because I don’t wear a pager.”

If I’d worn a pager I’d have had to justify it, and that would have meant insisting on being beeped every time something went wrong. And that, in turn, would have drained the authority right out of my team.

Even worse, I would have lost a lot of perfectly good sleep.

A lot of first-time supervisors treat their newfound authority to make decisions the way a child treats a new Pez dispenser. It isn’t the decisions (candy) that matters. It’s the process of delivering them that’s fun. (As evidence: At a recent “Nerd-fest” thrown by my friends Faith and Lynn, Fitz demonstrated his new motorized Pez dispenser. This is a killer gadget, kids. Ask Mom and Dad to get you one!)

These supervisors either learn the key lesson of career advancement or they’re perceived to be front-line supervisors the rest of their lives, even if they reach middle management. That’s the oldest lesson of succession planning: Always be important, but never be essential.

A regular theme of this column is the distinction between managing well, managing effectively, and succeeding in your career. Managing well refers to how you manage staff. To manage well, you have to delegate well, giving decisions to the people who report to you. Otherwise they can’t grow.

Managing effectively means making sure your department gets its job done well. That means you’re responsible for people and processes, not making decisions. The fewer decisions you make yourself, the more effective you are as a manager.

And then there’s the minor matter of your career. To be promoted, you need to pass the following tests: (1) You should at least resemble being qualified for the position you want; (2) You must have created the appearance of having been effective in your last job; and (3) You must be easy to replace.

This is neither original nor profound, but it is hard to accept. That’s because being hard to replace is a key survival strategy for many employees. And it’s a good one if your goal is job security. If that’s your goal, in fact, you should avoid sharing information, skills, or anything else that helps someone else do your job in your absence.

If, on the other hand, your goal is advancement then you have to treat succession planning as a personal mission. Delegating decisions makes you upwardly mobile. Your department can function effectively without you, and probably includes several qualified replacements, too.

Here’s the irony: Some managers get the silly idea that managing well and effectively is what got them promoted.