This is Electoral College week.

As I write these words, we still doesn’t know who won the presidential election. We do, however, know who lost.

Us.

Both Bush and Gore ought to feel embarrassed over the virtually perfect lack of leadership they’ve each shown since the election. Maybe not as embarrassed as John Ashcroft of Missouri, who lost to a dead guy (although to be fair, how do you say anything negative about an opponent who just died under tragic circumstances?) but embarrassed nonetheless. They’ve forgotten one of the most basic leadership rules there is: The relationship outlives the transaction. Their scorched-earth post-election strategies will make it much harder for either to succeed once taking office.

Bush and Gore have already blown it. They’ve achieved the extraordinary — they’ve made Bill Clinton seem like a man of character. But how about the leadership team one or the other will install?

They’ll also have challenges — the same challenges you or I would face when hired to take over an existing department. Fortunately for them, we’ve been talking about that exact problem in this column. You’ll recall last week we started with the first rule for taking over a department, which is: Fermez la bouche. Take time to size up the situation, figure out who you can trust and under what circumstances, what needs to be changed and what needs to not change, and so on. Every member of our new president’s leadership team would do well to remember this rule, because it will be hard for them to have all the answers when they don’t even know the questions.

If Dubyah is the winner, his team faces the harder challenge. Throughout his campaign, Dubyah slammed federal employees as “the bureaucrats in Washington” who aren’t to be trusted. Now they report to his leadership team.

This situation is common in the business world as well. Many managers find it convenient to foster competition with and distrust of other departments as a team-building technique. When promoted or transferred to a new role in which the departments they’d disparaged now report to them, their chickens come home to roost — the natural tendency to give a new leader a honeymoon period is replaced by a sullen do-the-minimum mentality. “You don’t trust me, why should I trust you?” is the natural reaction of employees who have been on the receiving end of us-vs-them politics.

If you’ve made this mistake, how should you recover? My opinion: Don’t even discuss it. Your focus needs to be on how you and the team are going to work together, not on what’s gone before. Even if directly confronted, say, “What’s important is that we’re on the same team now, so let’s talk about how we’re going to succeed together from this point forward.”

Figure it this way — nothing you could say now can undo what you said then. It’s how you act from this point forward that will determine your ability to lead your new team.

As every programmer knows, God was able to make the world in only six days because he didn’t have an installed base. Programmers rarely have that luxury.

New managers have a different kind of installed base to worry about. While the difficulties they face are not as technically daunting as creating a backward-compatible operating system upgrade, the social engineering issues faced by a manager taking over an existing organization present their own set of significant challenges.

When you take over a department, whether it’s through a promotion or a job change, you don’t get the luxury of designing your operation from scratch. You’re inheriting an installed base — an existing team, well-worn processes and ways of doing things, and an entrenched culture. But where programmers usually have a test environment in which they can safely find and fix mistakes, managers have to do their testing in the production environment of an ongoing operation. Missteps are very public, and hard to unmake.

The social engineering starts before you take the job. If at all possible, find out whether you’re walking into a problem area or not. If it isn’t a problem area, try to get a mandate for change from the reporting manager to create a problem where none existed before. Failing that, let some other victim take this no-win job.

Coming into a smoothly running organization is much harder than taking over a disaster area. How are you to succeed? Your chances of further improving the situation and having the team look to you for leadership are low. If your charter is to maintain the status quo, your predecessor will get the credit if you succeed; you’ll get the blame for any deterioration.

Compare this to the desk o’ death. The department is in shambles. The team is demoralized, productivity is low, waste is high, service levels aren’t. Whenever possible, choose the desk of death, especially if you’re the third or fourth manager to get the job — expectations will be so low that your success is virtually guaranteed.

So long as you follow a few simple rules.

The first is to keep your yap shut. Beyond the usual pleasantries of how delighted you are to have the opportunity, say as little as you can. Listen to everyone, in group settings and one-on-one. Neither agree nor disagree with anything beyond broad philosophical concepts, and above all, don’t choose sides or make any commitments. Offer no ideas of your own. Listen and make note of who says what.

In a desk o’ death, everyone has a private agenda and is trying to recruit you. Assume everything you’re told is biased. You have to piece together an accurate assessment jigsaw puzzle fashion out of bits and pieces. The moment you accept any individual as a preferred or unquestioned source of information, you lose your ability to lead — your preferred source will have established his perspective as your own.

So the first rule is to take time to size up the situation. Then you can decide what needs to be changed — processes, technology, reporting relationships, team members (chances are, if it’s the desk o’ death not everyone is a great employee), attitudes, or what have you. And, you can choose your priorities.

That’s the first rule. The second will have to wait until next week.

Until then, trust nobody.