Frisbees and hula hoops both came out when I was a kid, and at about the same time.

A year later almost nobody seemed interested in hula hoops, while Frisbees have thrived as a perennial favorite for forty years or so as a cross-species success. (Memo to Frisbee Corp: Invent new model made of diaper material to absorb canine saliva.)

Some management “fads” are more durable than others, too. One in danger of following the hula hoop is employee involvement.

The idea of employee involvement is pretty simple: If you’re making a decision that affects someone, they may have intelligent ideas to offer, and you’ll benefit from hearing them.

There’s a useful adjunct to this idea. If you’re making a decision that affects someone, asking for their ideas is a matter of simple courtesy.

If I’m reading the tea leaves right, this thought process has started to lose its luster among managers at all levels. Based on what I’ve been hearing, there seem to be two basic reasons for disenchantment with it.

The first reason — the one managers emphasize — is that it’s inefficient and wastes everyone’s time, including the employees we’d been involving. Even worse it causes unnecessary anxiety, leading employees to worry about what might happen when instead they can toil away in happy ignorance until management is ready to tell them the answer. (For the record, I’ve never once heard any employee thank a manager for keeping him or her out of the loop, but I’ve heard quite a few managers congratulate each other for this fine logic.)

Management’s retreat from involvement probably comes from our having made it a panacea. Many of us applied it indiscriminately to every possible decision. Worse, we confused it with consensus decision-making, so every departmental decision took time away from work and took a long time to make.

There is, I think, a second reason managers have started to retreat from involvement, and it isn’t pretty.

Many who aspire to management do so because they desire power. Wanting power (that is, the ability to influence events and outcomes) is neither good nor bad. It’s why you want the power that matters. It doesn’t take a psychotherapist to realize many managers want power because they were bossed around earlier in life.

These managers want their turn, and having to involve employees in decisions takes away from the emotional satisfaction of making decisions and making them stick.

They want to be the boss because they want to boss people around. It’s their turn.

This group of managers either washed out during the empowerment and involvement fads of the past decade, or they learned to paste a smile on their faces, getting even with everyone by instituting the appearance of involvement while actually ignoring every idea offered to them by employees.

The survivors are removing their velvet gloves, revealing their rusting iron fists and unpleasant personalities.

They’ve mistaken Frisbees for hula hoops. Right now we’re dealing with the best employment market in twenty-five years, at least as far as employees are concerned. Unpleasant managers will retain only those employees too inept to be hired by good companies or too afraid to start looking. Companies that allow these managers to dominate their ranks will slowly crumble as their best talent leaves for better working conditions.

Involvement doesn’t have to mean holding hands and singing Kumbaya. It’s more a matter of simple courtesy, asking peoples’ opinions before making decisions that affect them.

So in the cold hard world of commerce, simple courtesy gives your company a big competitive advantage.

Is this a great country or what?

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.