“Patriotism,” explained Samuel Johnson, “is the last refuge of a scoundrel.” In a less famous rebuttal Ambrose Bierce disagreed, insisting that it is, instead, the first.

CIOs aren’t, for the most part, scoundrels. Desperate, perhaps, but not scoundrels. It appears that reorganization, not patriotism, is what they resort to first.

We’re in the home stretch of the integrated IS plan, and the subject is how your department is organized. Here’s the first sentence of your plan for next year: “Since we’ve demonstrated repeatedly that reorganizations cause more problems than they solve, this year we will focus on making the organization we have work more effectively.”

There are situations that call for top-to-bottom reorganization. If the company strategy has changed dramatically, requiring radically different work efforts than before, major changes may be necessary. If so, they should be the result of a careful analysis of how you plan to get work done in the future. Reorganizations should, in other words, be your last resort.

Not your first.

We’ve covered the disadvantages of reorganizations in this space before. (See “How not to fix IS,” April 27, 1998). To recap, major reorganizations distract employees from real work, eliminate risk-taking, and metaphorically raise the walls between departments. Reorganizations are supposed to break down barriers to getting work done, but invariably they raise at least as many as they eliminate.

This year you aren’t going to do that. Instead, you’re going to look for all of the factors that keep the organization you have from working well. How? Just ask your employees. They know, and they’re probably dying to tell you, not necessarily in flattering language.

Then figure out what you’re going to do about these barriers to working well.

Some of the most common problems are leadership issues in disguise. We’ll address those in the section to be discussed next week. In the section on organization you’ll address mechanical problems, such as:

  • Overemphasis on organizational boundaries: Any emphasis is overemphasis, so this problem never goes away. You have to have an organizational chart. The moment it inhibits employees, it’s a problem. Encourage and reward an attitude of “never mind who owns it – we need to get this done.”
  • Competing financial goals: I know it’s hard to believe, but in some companies each manager has a budget and is rewarded by his or her performance against it. Yes, it’s true – some companies encourage managers to pad their budgets, which is always at the expense of other departments. The best budget-seller wins. If my bonus depends on my financial results, think I’m going to help you out?
  • The wrong groups: Over time, some groups outlive their usefulness. Over time, new requirements call for the creation of new groups. While massive reorganizations usually cause more problems than they solve, continual grooming of your organization makes all kinds of sense. The trick is to do this without creating organizational winners and losers, because employees who see organizational change as a risk focus on keeping their heads down and staying out of trouble, not on getting the job done.
  • Communication barriers: Among all the possible barriers to communication, three stand out. The first is physical: cubicle walls are too high, people who need to collaborate work on different floors or in different buildings, and so on. If possible, get people who work together a lot nearer each other.

The second barrier is psychological: Shyness is common among technical folk. Create lots of situations where people who wouldn’t normally work together have a chance to interact.

The third barrier, following the chain of command, is just stupid. The chain of command is for giving work direction. If the only way Fred Smith can talk to Irene Jones is for Fred to first talk to you so you can talk to Irene’s boss to set everything up … who’s going to bother?

No matter how you’re organized, your organization will facilitate some work and impede the rest. You’ll never fix it by reorganizing. Instead, plan to eliminate as many of the impediments to cooperation as you can.

I hate making dumb mistakes in this column, but make ’em I do. In a recent column on technical architecture, I described LU2 as IBM’s peer-to-peer protocol and LU6.2 as handling 3270 terminal sessions.

That is, of course, exactly backward, as a few of you kindly pointed out. The good news is that nobody yells at me when I make mistakes like this. The bad news is that far too many people, faced with a choice between owning up to a mistake and burying it deep, will choose burial in an unmarked grave rather than dealing with a bullying boss.

Following my recent column on bosses who rule by fear, lots of you wrote to ask how I learned the innermost details of your situations. Don’t worry — I don’t have a platoon of secret Ninja informants faithfully reporting to me. Having seen a few organizations run by bully bosses, I’ve seen them all.

Although my advice — find a better job — was just fine for someone on the receiving end of a bullying boss, it didn’t do much to help you prevent the problem in your own organization or to catch and fix it when it happens.

So here’s a practical program to keep fear out of your organization. It will work, so long as you sincerely want to create a great workplace:

1. Set the right tone: Model good leadership. Your leadership team will, for the most part, mimic your style.

2. Training: Hold regular one-day off-site sessions. Work through real-world scenarios, perhaps with role-playing exercises. Explore each scenario in depth. If you think your team ends up with the wrong conclusion, let them know your expectations. That’s called leadership. Disagreeing with your initial conclusion doesn’t make your team wrong, though. Learn from your team while you’re leading it.

3. Create communication channels: Make it easy for employees to tell you about problem managers. Establish an open-door policy. Meet employees for off-site breakfasts if they seem concerned over repercussions. Be open, friendly, casual, and available — don’t hide behind an imposing office and a big desk. Set up a Suggestion Box. Discourage anonymous messages — it’s too easy to stuff a ballot box — but treat signed messages as confidential whenever an employee requests it. Make sure employees can go to your boss if they have complaints about you — you aren’t perfect either, and you have to live under the same rules as the rest of your leadership team. Remind employees of their options frequently — not because “I want to spot bad managers,” but because “We want this to be a great place to work and I want to know where we can improve.”

4. Monitor turnover: Excessive turnover is an obvious warning sign. A manager who explains that “We’re better off without that employee,” is a bigger warning sign. Hold exit interviews. If possible, conduct them yourself; otherwise make sure exit interviews are with a senior member of your leadership team outside the departing employee’s reporting structure. Do not delegate this to HR — this is your job.

5. Give bad managers a chance to improve: A chance, not lots of chances. Let the problem manager know, in clear and precise terms, that you won’t put up with dysfunctional leadership behavior and that unemployment is the most likely outcome. Provide training if it’s needed, too.

When you’ve identified a bad manager, you need to take corrective action and monitor progress. This is the trickiest part, because the manager’s team must be told something, but not something that undermines the manager’s authority. That would eliminate any chance of success.

You’re best off if your manager describes a new approach to leadership to his or her team without having to acknowledge and apologize for past behavior. He or she is trying something different and has asked you to personally help monitor progress, explaining why you’ll be personally meeting with each team member periodically for a while.

You won’t satisfy employees who want retribution through this process. Retribution, though, is simply another layer of fear.

That’s what you’re trying to get rid of, remember?