December 14, 2011	Volume 11, Issue 50
Recommend this issue to a friend Join the Friends of Point Lookout HTML to link to this article…	Archive: By Topic    By Date Links to Related Articles Sign Up for A Tip A Day!
Create a perpetual bookmark to the current issue
| Follow @RickBrenner	Random Article

When Change Is Hard: Part II

by Rick Brenner

When organizational change is difficult, we sometimes blame poor leadership or "resistance." But even when we believe we have good leadership and the most cooperative populations, we can still encounter trouble. Why is change so hard so often?

Members of the 1437th Treadway Bridge CO, US 8th Army, erecting a floating bridge during the Korean Conflict on Route #3-D after the flooded roadbed washed out. Temporary bridge building was and is essential to military campaigns. When we think of combat, though, bridge building is not the first activity to come to mind. Nevertheless, without the capability, most campaigns would fail utterly. So it is with organizations undergoing dramatic change. They must take on responsibilities that they don't consider to be in the usual course of events, and they must construct policies and procedures that will not endure. These activities are necessary when we take on the challenge of organizational change. Photo taken July 8, 1952, courtesy U.S. Army Corps of Engineers.

In Part I of this exploration of the challenges of Change, we examined two sources of difficulty — sources internal (our emotions) and source external (outside pressures). This time, we explore issues related to planning. We'll look at three sets of reasons why planning change is so difficult: unexpected linkages, unexpected detours, and the need for temporary bridges.

Unexpected linkages

Linkages between organizational elements are often informal and unaccounted for. When an unrecognized linkage exists, changing one of the linked elements requires that we deal with the other linked elements.

For example, when one group is physically situated close to another, friendships and associations form. Some of those connections might be channels for ongoing knowledge exchange. Separating the two groups by moving one group to a distant location can stress those connections, degrading performance. Relocating them both together might be preferable.

If we break linkages we don't understand, change can be hard. A plan to move one group might seem perfectly sound, but it can fail if it doesn't recognize the importance of bonds between people. What might seem like resistance could actually be the result of interrupted knowledge flow due to breaking connections.

Unexpected detours and backtracking

At times, only after we begin executing a change plan do we recognize some factors we neglected. When this happens, with a little luck, we can make adjustments and continue. But sometimes we have to stop or backtrack, replan, and begin again.

For example, in an acquisition, if we intend to relocate the acquired IT department, we might find that relocation is impractical because key people would require financial assistance with real estate issues. And keeping those people in place might also incur unsustainable costs. The department relocation plan wasn't defective, though it didn't anticipate real estate market conditions.

If a plan is incomplete, change can be hard. The people involved might not be resisting change — they might actually have legitimate issues that the plan didn't anticipate.

Temporary bridges

When we At times, only after we begin
executing a change plan
do we recognize some
factors we neglectedencounter or anticipate difficulty, we might not be able to change systems directly from their current configurations to the final configurations we seek. Sometimes, we must build temporary bridges.

For example, in the IT relocation problem, the organization might become a lender, investor, or loan facilitator, to enable people who are relocated to secure mortgages for new homes.

Plans that include interim configurations that we intend later to abandon aren't necessarily defective. And the people whose needs we're accommodating in this way aren't making trouble — they have legitimate needs that we must somehow address. Unless we can be flexible enough to find temporary bridges, change can be hard.

When change is hard, and when the job market is tight, some managers are tempted to communicate the change-or-else message. Resist the temptation. Someday, those who are unhappy will have alternatives. And they will choose them. First in this series   Top    Next Issue

Is your organization embroiled in Change? Are you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt? Read 101 Tips for Managing Change to learn how to survive, how to plan and how to execute change efforts to inspire real, passionate support. Order Now!

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Outsourcing Each Other's Kids

Outsourcing is now so widespread that it has achieved status as a full-fledged management fad. But many outsourcing decisions lack the justification that a full financial model provides. Here are some of the factors that such a model should include.

On Beginnings

A new year has begun, and I'm contemplating beginnings. Beginnings can inspire, and sometimes lead to letdown when our hopes or expectations aren't met. How can we handle beginnings more powerfully?

Letting Go of the Status Quo: the Debate

Before we can change, we must want to change, or at least accept that we must change. And somewhere in there, we must let go of some part of what is now in place — the status quo. In organizations, the decision to let go involves debate.

Kinds of Organizational Authority: the Informal

Understanding Power, Authority, and Influence depends on familiarity with the kinds of authority found in organizations. Here's Part II of a little catalog of authority, emphasizing informal authority.

Obstacles to Finding the Reasons Why

When we investigate what went wrong, we sometimes encounter obstacles. Interviewing witnesses and participants doesn't always uncover the reasons why. What are these obstacles?

See also Organizational Change and Project Management for more related articles.

Coaching services

Get the ebook!

• Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
• Get 2003-4 in Why Dogs Wag Their Tails (PDF, USD 11.95)
• Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
• Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 19.99)

Public seminars

The Race to the South Pole: Ten Lessons for Project Managers

On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:

• Northern Quest Casino, 100 N Hayford Rd, Airway Heights, WA 99001: June 11, Professional Development Day, Inland Northwest Chapter of the Project Management Institute.
   

The Race to the South Pole: The Power of Agile Development

On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:

• Download to
  your calendarThe Yard, 1211 South Mammoth Road, Manchester, NH 03109: June 15, Seminar, New Hampshire Chapter of the Project Management Institute.