I just heard it again: “People naturally resist change.”

Can I just respond, one more time, “No, they don’t.”

There just aren’t that many things that people do or don’t do naturally. People naturally love their mothers. They naturally learn to speak, interpret language, and walk. Eating is natural, too, but not raw oysters, which are definitely an acquired taste, and one I’ve never bothered to acquire, because really, yuck.

People don’t naturally resist change. They naturally resist changes they expect to be bad for them, not to mention changes explained in ways that are insulting. Why would they do anything else? If you design change to offer opportunity to employees, and explain it in terms that don’t denigrate their accomplishments, you’ll go a long way toward avoiding change resistance.

The subject of transitions, while related, is distinct. It’s driven by the way humans respond to the perception of loss, as William Bridges pointed out in his excellent and aptly named Managing Transitions. Without taking anything away from the book, here’s a simple technique that can help reduce the difficulty of managing transitions. A lot. To explain it, I have to tell you about the best golf lesson I ever received, and the worst.

The worst golf lesson came from a pro who had an excellent swing which he tried to teach me. He showed me a different way to address the ball, start my backswing, and handle the follow-through. The only part of my swing he left alone was my grip.

It ruined my game for two years.

The best golf lesson started with the pro watching my swing as I hit a bunch of golf balls. “That’s great, Bob,” he told me. “I want you to do just one thing differently. Which eye do you look at the ball with?”

“Both eyes,” I answered. “It’s that binocular vision thing.”

“Try looking at the ball through your dominant eye instead. Don’t close the other one — just cock your head so you’re paying attention to the dominant one.”

I did that and hit a bunch more balls. “That’s great, Bob,” he said. “I want you to do just one thing differently — right now you’re keeping your left heel flat on the ground during your backswing. Let it up as you pull the club back.”

I did that too, and three more “just one thing differentlies” over the course of an hour. The lesson transformed my long game.

That’s the secret of managing transitions: Don’t implement them as major transitions. Doing so turns employees who are competent at the old way of doing business into incompetents in the desired way. It emphasizes the sense of loss while maximizing inability.

Compare this tactic to the golfing way:

“You’re doing this well. I’d like you to try just one thing differently — before you start a project, make sure you and the business sponsor line up everyone who will work on any project tasks and include them as project staff. Get a commitment of their time from their reporting manager, and make sure they know what their tasks are and when they’re supposed to start and end.”

“You’re doing fine. Can I suggest just one small change? Instead of estimating every task yourself, only take the work breakdown structure as far as the assignment level, and ask project team members to finish the job for their tasks.”

And so on.

You can’t implement every change this way. If you’re implementing a major ERP system, which usually means changing much of how the enterprise conducts its business, it’s pretty hard to institute it one small tweak at a time. On the other hand, when you implement ERP, you aren’t telling employees they were idiots for doing business the old way, either. Sometimes, you have few or no alternatives to instituting major change in a single step.

But whenever possible, remember this:

I’ve listened to business change management consultants, and I’ve had a lesson from a terrific golf pro. The consultants told me to “unfreeze, change, and refreeze” — arguably the worst advice ever delivered, given, as it usually is, to companies facing the need for perpetual change.

The golf pro, in contrast, cured my slice.

Once upon a time I helped review a vendor’s Master Services Agreement (MSA). (if you’re unfamiliar with the concept, an MSA defines the relationship between a service provider and a client. Specific pieces of work are spelled out in what are alternately called Task Orders or Statements of Work.) Among the provisions in this gem: Should the relationship go awry, the vendor had the right to terminate with 60 days notice. The client received no right to terminate.

  • A prospective client once asked me to use its standard MSA to govern some consulting work. Had I signed it, any intellectual capital my company used in the engagement would have become their property. Not satisfied with asking for the unrestricted right to use it themselves, they figured I shouldn’t get to use it anymore myself. After roughly seven hours of my life I’ll never get back, we came to the same agreement we should have started with.
  • More recently we were asked to sign an MSA with a provision requiring us to continue our work in the event of a dispute over terms, schedule, effort, definition of deliverables, or what have you. It had another provision, on a different page, asserting the client’s right to withhold payment in the event of the same kind of dispute. Either of these terms is reasonable. Together, they gave our client the right to compel us to continue working without ever getting paid. I don’t think so.
  • Getting back to vendor-driven unilaterality, I once saw a contract that gave an outsourcer the right to increase its hourly rates more than three times the rate of inflation each year. I saw another that included a non-solicitation clause preventing the client from recruiting vendor staff while leaving the vendor free to solicit as it liked.

I’ve been on both sides of this issue enough times to recognize a time-wasting trend: These documents increasingly are written to be one-sided. Really, what’s the point? Does anyone want to do business with a company careless enough to fall for this kind of thing?

I blame the dot-com era. No, really … the dot-com era, and especially the so-called experts who promoted “digital marketplaces” and focused the business world on obtaining the lowest-cost goods in every purchase. Prior to that, the business world had, for the most part, figured out that strong supplier/customer relationships provide more value at lower total cost than when each party views every interaction as a negotiation in which it tries to gain maximum advantage.

Awhile back, KJR introduced the idea of ROT — Relationships Outlive Transactions. You should remember ROT when dealing with suppliers and clients just as much as when dealing with managers and peers within your organization. This isn’t about being a mensch (although aspiring to mensch-hood isn’t a bad personal goal). It’s about personal and organizational effectiveness.

Compare the reputation of two vendors. Of the first, clients say, admiringly, “What a sharp company. It doesn’t miss an opportunity — its people always try to find an angle. They’re shrewd — if our attorneys hadn’t been on the ball they’d have taken us to the cleaners.” Of the second, clients say, “What a great company. You can always trust its employees to be fair. We just do business, and haven’t once had to pull out the contract — we’re always able to work things out.”

You have to choose one. If you choose the first, you know before you start that you’ll have to invest quite a bit of extra time looking for loopholes. You’d have to have a very good reason to go through the trouble.

It works the other way as well: When service providers look at you, are they more likely to say they have to negotiate hard for every point, or that you do your best to establish a working relationship that’s reasonable? And before you say you don’t care, consider that the best service providers can afford to turn down bad business, and are generally smart enough to do so.

Writing fair contracts isn’t all that difficult. The social philosopher John Rawls provided the key concept in his definition of a fair society — it’s one you’d design without knowing in advance where you’d be born in it. To apply his approach to the world of business relationships, when you ask your attorney to draft a contract, don’t reveal whether you’re planning to be the buyer or seller.

The only possible outcome is a contract both can accept.