In investment circles, confidence predicts stock market performance. As it should: Confident investors buy more stocks. This increases demand relative to supply. When demand increases relative to supply, prices (for stocks in this case) go up and the market improves … at least, it does in the short term. In the end, earnings do matter — if they’re bad enough they erode investors’ confidence, making them want to sell their shares, increasing supply, decreasing demand, and lowering price.

It’s an excellent example of self-fulfilling prophecy, which makes the much-lauded ability of “markets” to predict the future somewhat less impressive than market religionists extol in their self-congratulatory exhortations.

In corporate America, many employees prophesize in a similarly self-fulfilling manner — in this case, for the inevitable failure of whatever proposed change the company’s leaders have decided to invest in. Call it the Assumption of the Present. While less smug than the asserted perfection of the wisdom of markets, the Assumption of the Present is equally circular: The organization is as it is because it must be. Otherwise it would be different, and that’s why the proposed change, whatever it is, can’t succeed.

The Assumption of the Present is not, however, entirely lacking in logic. It works like this:

Some dynamic systems are in equilibrium — the forces that make up the system are in balance. The rest, pushed by their out-of-balance forces, change until all forces are in balance, at which point they have reached equilibrium and change stops.

So companies, which are after all, dynamic systems, change until they reach a stable state. Once they do, their employees adapt to the equilibrium and the in-balance structural forces that define the equilibrium state become part of the “air” of the place — invisible and unnoticed, built into everything. Mention any change, no matter how desirable, and everyone explains why the change can’t succeed: Because the structural forces that drove the organization to its current equilibrium are a fact of life, the way they are because they must be. Change? How’s that going to happen? All forces are in balance.

It’s the Assumption of the Present. It’s an assumption because it treats all components of the company as immutable elements, not as changeable components of a design.

Except that sometimes it’s more than an assumption — it’s an inference based on experience. Few business changes of any strategic significance rely on a company’s leaders behaving exactly as they have all along. Supply chain optimization means orders and order quantities are established by algorithm, not by the COO’s gut feel. Customer Relationship Management means replacing policies with guidelines and relying on the judgment of customer service representatives. A redesign of the corporate governance process means today’s top priority is inserted into the master schedule as early as possible instead of stopping yesterday’s top priority so today’s can get immediate attention.

Employees have every right to expect the company’s leaders to behave tomorrow pretty much as they behaved yesterday and today. So if a highly touted strategic program depends on those leaders behaving differently, employees have every right to be skeptical.

If you read the literature on business change, you’ll find lots of helpful advice about management commitment, finding quick wins, consistency, communication and so forth. Here’s something I’ve never read in print: If you want any major change to succeed, find something important for the company’s executives to do differently. Identify it. Define it clearly. Prescribe what they need to do that is visibly different from what they’re doing now. Validate your assessment with employees (but tactfully — you don’t want to create the impression that you’re undercutting the company’s leaders).

And present it to every executive, plainly, succinctly, and directly. Explain that their way of going about things was perfectly suited to the old situation. Demonstrate the connection between the behavior change you’re recommending and the strategic change they’re trying to achieve. Empathize with their instincts.

And above all, make it clear: You aren’t asking them to stop doing something that’s wrong. You’re asking them to change how they address some situations so employees will feel more confident when it’s their turn.

Too often we criticize the lack of leadership provided by business executives. Most are entirely willing to provide every bit of leadership the situation demands. They simply have to overcome the same difficulty everyone else does: Recognizing when the traits that have led to their current success have become the barriers to their future success.

Compared to success, failings are much easier to recognize and address.

IT managers deal with contracts a lot — from technology vendors, systems integrators, outsourcers, and other miscreants who regularly darken the doors of corporate IT. Even many who recognize the importance of strong negotiating skills do their best to ignore the contracts that express a negotiated agreement. Mostly, it’s a matter of time and attention span. They have too little of either.

It should be obvious: What you agreed to doesn’t matter. It’s what the contract says you agreed to that matters. Even if the contract is an End User License Agreement (EULA) or some other “shrink-wrap” contract that wasn’t preceded by a formal negotiation, it’s still an agreement, and it’s up to you to negotiate a fair version of it.

So if you negotiated the deal, you need to read the contract provisions to make sure they accurately reflect the deal you negotiated, and if you didn’t negotiate the deal, you need to read the contract provisions to find out which terms need to be negotiated.

Here are a few rules of the road to keep in mind as you do so:

1. If you weren’t party to it, you aren’t bound by it. For example, it’s increasingly popular for EULAs to make the transfer of software licenses to another party, even an acquiring corporation, a contract violation. If you’re on the wrong end of this provision — perhaps you have to integrate the information technology of an acquired company — are you stuck buying new licenses, just because the company you acquired agreed to the EULA and that’s what it says?

No, you aren’t. Yes, you acquired the signed EULA as part of the corporate acquisition. One of two conditions is true: Either you own the license as part of the acquisition and are bound by its terms and conditions, or you don’t. If you do, you can use the license, if you don’t you aren’t bound by it. Even if, for some reason, you’re stuck with the worst of both worlds, so what? Call the offending vendor and make it clear: Either it sells you new licenses for a dollar and continues to collect revenue from annual maintenance, or you’ll convert to a different vendor that’s interested in your business.

2. What isn’t in the contract is more important than what is in the contract. Not really, but there’s more risk there. Spotting circumstances that might arise and prove disadvantageous to you that aren’t described in a contract is much more difficult than analyzing what’s there. If it’s a negotiated contract, shame on both of you for not thinking of the circumstance and negotiating it in advance. If it’s a non-negotiated contract, spotting the missing items takes more work. Before you sign, make sure you can live with its terms and conditions; negotiate those you can’t live with.

3. Contracts only matter when things go wrong. Probably the single biggest mistake managers make in reviewing contracts is focusing their attention on whether the contract accurately reflects the intent of the agreement. That is, of course, necessary, but it’s pretty much irrelevant, because so long as everything is going well, neither party will ever pull the contract out of the file drawer. Companies review contracts when something goes awry. When you analyze a contract draft, do so from the same perspective.

4. After non-delivery, the second-biggest problem that can arise in a contract is excessive success. Take a step back. Does the contract assume failure, or at best mediocre results? Joint ventures are especially susceptible to the danger of success, with one side often giving away far too much on the premise that, “We have nothing right now, so there’s no downside risk.” Sure there is — whatever you’re trying to accomplish might work out far beyond your current estimates, which are, after all, predicated on worst-case analysis.

5. Involve the lawyers, but don’t make it their problem. It’s your deal. Their job is to help you make sure it’s the right deal, not to make sure it’s the right deal themselves. Which means, by the way, that it’s up to you to make sure you’ve established a strong working relationship with your corporate attorneys.

Speaking of lawyers, a common negotiating ploy is for a vendor to say to you, “Do you really want to let the lawyers become involved?” It’s an implied threat: The lawyers will kill the deal, or at best cause unaffordable delay. Your best response is to answer with a question: “Why — is there something in the contract our lawyers might object to?”

If nothing else, their response will have some amusement value.