“Would you like to see our dashboard?” Larry Robbins asked.

Larry, a talented CIO, is an old friend and occasional client — several years ago I provided some assistance as he combined two IT divisions into one following a corporate “merger of equals.” He’s a very bright guy, a strong leader, and a former consultant himself who’s taught me quite a few tricks of the trade along the way, so there was only one right answer: “You bet!”

While not organized quite the way we put our standard dashboard together at IT Catalysts, it’s very nicely done, providing a clear snapshot of how his IT division is performing and progressing, just like a dashboard is supposed to. With Larry’s scorecard in hand, I asked if he’d be willing to share what he’s learned are the keys to implementing a successful IT dashboard, seeing as how he actually has one. He graciously agreed. So without further ado, here’s Larry on IT dashboards:

  • Keep it simple at the highest levels, to provide focus, focus, and more focus. The dashboard establishes priorities — what’s important. Keeping it simple helps employees at all levels figure out how they can best contribute to improving these priorities.
  • Measures: Crawl, walk, run. Some areas are simply insufficiently mature to manage to the desired measures. That’s okay. Don’t pretend — deal with the situation as it really is. If necessary, take a year to put in place the process (and understanding) necessary to measure the next year. We call these “milestone” measures, which are the concrete steps required to bring that area to the maturity level necessary to measure outcomes in the future. The worst thing to do is to miss this step and pretend. That drives cynicism.
  • Siloes: We tried establishing separate departmental goals for each of my direct reports, with the intent of clarifying accountabilities, around which there was much enthusiasm. The process of doing so actually began pulling my team apart. I now believe many of these departmental objectives will be addressed anyway, as the department head performs his or her primary job.The real purpose of divisional priorities is to provide a meaningful framework to align the department heads to accomplish those priorities that can only be accomplished together. I’m learning the core effectiveness of an IT organization is its ability to operate collaboratively, even while its structure, and the pressures of day-to-day business trade-offs constantly tug at pulling it apart. The employees noticed too, which silently encourages the same behavior through the ranks.
  • Assign “Goal Champions.” Making each of the CIO’s direct reports responsible for one of the dashboard measures gives them an opportunity to influence peers and think like a CIO, getting out of their silos to do it. And as they sponsor these goals in various meetings, employees have an opportunity to see department heads acting on behalf of the entire IT shop rather than defending turf. These are all good things … and there’s no downside.
  • Job of the CIO: I’m learning that it’s to create an environment where everyone can make their best contribution. It sounds simple but it’s not. Peter Drucker said it best: “So much of what we call management consists of making it difficult for people to work.” We’re encouraging employees to customize their goals to contribute to our top four priorities in whatever ways make the most sense to them. It’s working, largely because we have employees who are passionate about making a difference.

I’d love to embellish, but Larry didn’t give me much room to maneuver — his suggestions speak for themselves. I am, in any event, happy to report that the dashboard guidelines provided here in recent columns line up quite well with his experience in real-world IT.

I’m even happier to report that he isn’t consulting anymore. Who needs that kind of competition?

Ever wonder how they sleep at night?

Business executives sometimes have to let people go. Sometimes they have to lay off large numbers. There are occasions when companies have to push employees hard — to work long hours and extra days without any more pay.

It happens. The future being somewhat less predictable than the past, strategies don’t always turn out to be wise and tactics sometimes backfire. New leaders sometimes come in to find a predecessor has allowed a culture of mediocrity to develop, and with it the accumulation of too many employees, and too many of them with less-than-superb talent.

Business leaders sometimes do have to make hard choices. When the situations arise, the good ones do. That isn’t the question.

The question is whether they sleep well afterward; whether they accept large bonuses and option awards for doing so; whether they take joy in the exercise, as many employees suspect.

It turns out that many of them might.

KJR Club member Paul Novelli pointed me to an article by Alan Deutschman in the July 2005 issue of Fast Company recently, describing the research and conclusions of criminal psychologist Robert Hare.

Dr. Hare is widely known in his field for developing the “Psychopathy Checklist” — a twenty-item personality evaluation that’s the gold standard among law enforcement professionals for the diagnosis of criminal psychopaths. Dr. Hare has reached a disturbing conclusion: Many CEOs are borderline or more-than-borderline psychopaths. He suggests that boards of directors should screen CEO candidates for psychopathy — the absence of empathy, compassion, remorse and guilt.

I hope it never happens. In the modern world of business, if boards of directors were to apply the Psychopathy Checklist to CEO candidates, many would use it to identify those best suited for the job. They’d use it, that is, to systematically exclude candidates exhibiting capabilities for empathy, compassion, remorse and guilt. While conventionally regarded as useful personality traits, they can interfere with the successful operation of a modern publicly held business.

Enterprises compete globally. Among their competitors are companies whose strategies and tactics aren’t constrained by empathy, compassion, remorse and guilt, and which acknowledge responsibility only to shareholders — not to employees, customers, or the communities and nations within which they operate. Even their obligation to the law is limited to a comparison between the cost of compliance and the cost of the fines for noncompliance. (Don’t agree? Research Union Carbide’s track record in Bhopal.)

There have always been amoral corporations. What’s new is that behavior we’d consider psychopathic in a human being is business as usual in business. So when a company competes with psychopathic rivals and doesn’t adopt a similar stance it’s like trying to adhere to the Marquis of Queensbury rules in a knife fight.

Here’s a challenge for you, as chief information officer or as a manager who would like to become a chief information officer: According to Dr. Hare, chances are good that at some point in your career you’ll find yourself working for a borderline or more than borderline psychopath. Can you handle that kind of situation?

The easier (but still hard) version of the question is associated with those business leaders who harm shareholders — the Bernie Ebbers and Chainsaw Als of the executive suite. Harming shareholders is universally recognized to be Bad, so at least the situation is clear.

There are also many business leaders, at all levels, who exhibit more psychopathy than you might personally find comfortable but who don’t express it in ways that break laws or harm shareholders. If you report to them, you might find yourself dealing with abusive behavior, unreasonable demands on your staff, shoddy practices toward customers, assignments or explanations given to you that deliberately conflict with those given to other managers, or any of a number of other circumstances that break no laws.

The question used to be what you should do if you find yourself working for a bad boss. Dr. Hare has just raised the stakes, by letting us know some of these bad bosses are, clinically speaking, psychopaths. Bad boss or psychopathic boss, if you’re looking for the answer here, you won’t find it, because there is no “the answer” — leave, perhaps, assuming you have alternatives. In a large city you probably do. In a smaller community you might not. Not that leaving fixes anything beyond your personal circumstances. And where will you go, when managers are, in increasing proportions, required to behave psychopathically?

Businesses are, increasingly, psychopathic entities. According to Dr. Hare, many have psychopathic leaders.

One wonders which came first.