A good friend told me, “I was terminated with 20 minutes left in the day, on a Thursday. They had said I would be severed sometime during the month but they had led me to believe it would be closer to the end of the month. Nice treatment after 24 1/2 years …”

Another company bought his employer a few years before. He had known the day was coming, and he never once expressed resentment over his coming layoff. Elimination of redundant staff is one of the realities of a merger or acquisition. Yes, it’s painful, but there’s no foul — business is out to make good business decisions.

Why was it was managed so badly?

Consider the Portuguese man-of-war. As we learned in high school, although it looks like one animal, it’s actually a colony of independent coelenterates, each of which feeds and reproduces separately.

We’re colonies, too. As Richard Dawkins points out in The Selfish Gene, a body is just a gene’s way of making more genes. Even that is a simplification. An unknown proportion of our internal constituents began as independent critters. Mitochondria, for example, the organelles that make oxygen the key to metabolism instead of a toxic gas, started out as free-living bacteria.

Even though each of us is a colony, we manage to act as a purposeful organism – so much so that we harm individual colony members with callous disregard. (Example: Every time someone goes on a diet they starve or kill billions of fat cells – and just think of how many are destroyed during liposuction!)

Liposuction creates personal change. How about business change?

IS projects have always been about business change, and an increasing number of companies recognize that all IS projects are really business change projects that inject significant new technology into the equation.

Most business changes both create and eliminate jobs within the enterprise. Whatever your role in IS, at some point in your career you’ll help eliminate the jobs of innocent employees who did their jobs competently but whose roles are no longer needed because of the business change you helped the company achieve.

Companies are getting better at managing business change. They’ve learned to redesign processes, integrating technology into the new process design. They’ve learned to train employees in the new processes and technology rather than assuming everything will be self-evident. Most have learned to communicate the reason for a change, not just “here’s your new job – now go do it.” Some have even learned that redesigning the organizational chart comes after redesigning processes and technology, not before.

Sadly, though, many companies still see employees as nothing more than adipose cells … hence the phrase, “Getting rid of the fat.” And if you raise your hand to protest a layoff you risk being branded as soft – the business equivalent of “bleeding heart liberal.”

So here’s some advice: If you have an opportunity to influence how your business will manage a change that requires layoffs, don’t get all righteous about what is ethical, compassionate, or the right thing to do. In business, ethics is a personal matter, and ethical businesses get that way through leaders who act ethically, not through preaching.

Instead, be practical.

Point out that the long-term goal of business change is growth, and the cost of laying off one group of employees and then recruiting a different group is far higher than the cost of retraining the employees you have.

Suggest that when “trimming the fat” the company should use a sharp knife, not a sledgehammer. If valuable employees who support change find opportunities while non-performers and change resistors find themselves on the outside, most employees will quietly applaud when they no longer have to cover for their non-producing peers.

Most important of all, point out that every time the company treats departing employees like the cast-off byproducts of cosmetic surgery, the morale of every remaining employee plummets, and employees who might otherwise support change will become sullen and passive resistors of it, something every bit as poisonous as some colonists in a Portuguese man-of-war.

That’s bad for profits, and even worse when the next big change comes around.

And now, a dumb CIO story:

A division of a multi-billion-dollar enterprise embarked on a business redesign. Because the redesign was expected to have technical repercussions, an IS analyst was part of the team.

Among its findings, the team recommended replacing a core legacy system, so the head of internal consulting called the CIO to ask if he was comfortable with the team’s findings.

The CIO hadn’t seen the team’s recommendations, but when the head of internal consulting explained them he responded that he could not support them, explaining that his analyst really didn’t understand the system, the environment, or the situation. Further, he instructed the head of internal consulting to keep him informed of the positions his analysts took in all future projects, to prevent a recurrence of the problem.

Nice solution, don’t you think?

We’re continuing our series of columns on managing change. We’ll take a break after this one, which explores the fascinating issue of restoring IS’s reputation as a sponsor of change from its current status as grumpy change resistor.

Restoring? Yes. Back when IS was EDP (electronic data processing) and consisted of a lot of programmers and computer operators with a couple of managers to keep enough coffee, coke and pizza in stock, we wrote all the legacy systems we now can’t figure out how to replace, transforming our companies from top to bottom as we did so.

Now we have business people in charge and, obsessed with tangible returns on investment and avoidance of risk, we’re paralyzed.

Since every business change from this moment forward will require the active support of IS, we need to be better than this. How can you change your own organization from a sullen group of change resistors to an energized team of enthusiastic supporters?

Step one: Look in a mirror. Do you like the challenge of doing things differently, or are you obsessed about what will break in the process? Do you wake up with ideas on how to improve the business, or do you wake up grousing about end-users who install their own software? Do you complain that NT just isn’t as stable as the mainframe, or do you explain to your system administrators that since some data centers manage to create highly reliable server environments, you’re going to do so also?

Is your habit to say yes or to say no?

Here’s how to turn your organization into a supporter of change: In your next all-hands meeting explain that from this point forward, nobody will ever turn down a request from the business. Ever.

No matter what the request, the answer will be, “We can do that. If you’ll sign up to the cost, we’ll figure out how to make it happen.”

Need to replace a core legacy system? We can do that. It will be expensive because conversions are never cheap, but if you’ll sign up to the cost, we can do it.

Want to integrate multiple legacy systems into an integrated call center? We can do that. We’ll have to engage an outside development partner because we don’t have a lot of the expertise we’ll need, and right now our resources are stretched pretty thin, but that’s okay. There are lots of good systems integrators out there and we’ll find one to work with us to get your job done. If you’ll sign up to the cost, we can do it.

Need a Macintosh instead of an NT workstation? We’ll have to install a Mac gateway onto one of our servers, but if you’ll sign up to the cost, we can do it. Will the Mac user want help desk support? Since we don’t have Mac expertise in-house, we’ll find you outside support … if you’ll sign up to the cost, of course.

How do you embrace change instead of resisting it? Make change part of every employee’s job description, that’s how. If their job is figuring out what it will take to make change happen, they will.