UPI Study › Courses › Principles of Management › Free lessons › Lesson 6.4 Free with a free account
Turning Intention into Action: The Planned Change Process
Principles of Management · Chapter 6: Leading Organizational ChangeSection 6.4 · lesson 28 of 11711 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Principles of Management.
Lesson complete
Earn the 3 college credits for Principles of Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Lewin's Change Toolkit: Unfreeze-Change-Refreeze and Force-Field Analysis →← Leading Through Uncertainty: The Manager's Role During ChangeNext lesson: Lewin's Change Toolkit: Unfreeze-Change-Refreeze and Force-Field Analysis →
In this lesson
Turning intention into action.
- Distinguish planned from emergent change
- Describe the 8 stages of planned change
- Explain how a change is diagnosed before it is designed
- Recognize the common failure pattern
Transcript
Everything said in the video, section by section (1,546 words). Read along, or search it.
Leading Organizational Change
The Planned Change Process
Most change efforts start with good intentions. Many of them end exactly where they started. This section lays out the general process that turns an intention into a change that actually holds. We begin by separating planned change from the emergent change that happens anyway. Then we walk through the eight stages of planned change, and what each one produces. We spend real time on diagnosis, the stage most often skipped, and the classic error it prevents. Then the change agent, the design of the intervention, resourcing, evaluation, and institutionalization. And we'll name a failure pattern you will recognize the moment you see it in a real organization.
Planned and Emergent
Not All Change Is Designed
Planned change is change deliberately designed and managed, through a defined sequence of stages. Emergent change is different. It arises gradually from ongoing organizational activity, without being centrally designed in advance. It's worth being honest about this from the start. A substantial share of the change inside real organizations is emergent, whatever any formal plan says. Informal adjustments, workarounds, and gradual shifts in practice accumulate on their own. They often move faster than any planned initiative. So this framework describes the planned side of that reality. It's the right approach whenever a change is significant enough, or risky enough, to warrant deliberate design. It is not a claim that every organizational change follows, or should follow, this sequence.
8 Stages
Each Stage Produces What the Next One Needs
The general planned change process runs through eight stages. The key idea is that each stage produces a specific output the next stage depends on. Recognizing the need produces a stated trigger. Diagnosing the problem produces an understanding of the actual problem, rather than its presenting symptom. Identifying options produces a set of genuine alternatives. Selecting an intervention produces the chosen one. Planning the implementation produces a concrete plan, with resources attached. Implementing produces the change itself. Evaluating produces evidence of whether it worked. And institutionalizing produces a change that survives past the attention of the people who drove it. Skip a stage, and the next one starts without the input it needs.
Figure 6.4.1
The 2 Stages Most Often Skipped
Here are the eight stages laid out as one continuous path. Two of them are marked, because they are the ones most often skipped. The first is diagnosis, right near the start. The second is institutionalization, at the very end. Notice where both of them sit. Diagnosis comes before the visible activity of designing and implementing a solution. Institutionalization comes well after implementation has already produced its visible result. In both places, the active, visible work of change is either not yet underway, or no longer underway. That is exactly why both are so easy to shortchange under time pressure.
Diagnosis
Find Out What Is Actually Happening
Diagnosis is the deliberate gathering of data on what is actually happening, before deciding what to change. It's the stage most consistently skipped under time pressure. That connects directly to the diagnosis problem from Subchapter six point two. Skipping diagnosis is precisely what lets an organization change whichever target is easiest. The target actually responsible never gets identified. And diagnosis has a visibility problem. It happens before anything that looks like action. To a busy leader, it can feel like delay. In fact, it is what makes the action worth taking. Four methods are available for diagnosis, each with its own reach, and its own limitation.
Table 6.4.1
4 Diagnostic Methods, None Unbiased
Table six point four point one compares the four diagnostic methods on what they reveal, what they cost, and their bias. Interviews reveal rich, detailed, individually contextualized understanding, straight from the people closest to a problem. They're costly in time, especially at scale. And what people say may not match what they actually do. Surveys gather structured information across a large group, cheaply per respondent, though they're harder to design well. Their depth is limited, and the framing of the questions can shape the answers. Observation reveals what people actually do, independent of what they say they do. It's costly in time and access. And people often behave differently when they know they're being watched. Performance data offers objective, already-available measures, at very low extra cost. But it reflects only what the organization already chose to measure, which may not be what matters. No single method is unbiased. That's why good diagnosis often combines more than one.
The Diagnostic Error
The Presenting Problem Isn't Always the Real One
The most consequential diagnostic error has a name. Mistaking the presenting problem for the real one. The presenting problem is the issue as it was first described, often by whoever raised it. The error is accepting it as the real problem, without checking that the two are actually the same thing. Picture a department head who reports that her team needs more people. That's a presenting problem. Diagnosis might reveal the real problem is an inefficient handoff between two roles. No amount of extra headcount would fix that. The inefficiency would simply be reproduced, with more people involved in it. Accepting the presenting problem at face value is faster than diagnosing it. That's exactly why it happens so often, under the same time pressure that causes diagnosis to be skipped altogether.
The Change Agent
Inside or Outside?
Someone has to drive the change. That person or group is the change agent. The role can be filled from inside the organization or from outside, and each brings a different balance. An internal change agent brings existing organizational knowledge, and established relationships. She also has a stake in outcomes that persist after the change is complete. But she brings existing loyalties and political entanglements too. Those can compromise how objective she is perceived to be. An external change agent brings genuine outside objectivity, and specialized expertise the organization may lack. But she lacks the internal knowledge and relationships an insider has. And she typically has no lasting stake once the engagement ends. That can affect how invested she is in a solution actually holding.
Designing the Intervention
4 Design Decisions
Once a problem is correctly diagnosed, designing the intervention involves four related decisions. Scope is how much of the organization the intervention touches. Sequence is the order in which its parts are carried out. Pace is how quickly it proceeds. And the pilot decision asks whether to test the intervention on a small scale, before committing to it fully. That last decision hides a distinction worth making explicit. A pilot that genuinely tests whether something works is designed to produce real information. That includes the possibility that the intervention should be abandoned, or substantially revised. A pilot that merely demonstrates is designed, consciously or not, to confirm a conclusion leadership has already reached. On paper, the two look similar. Both involve a small-scale trial. Only the first one is genuinely diagnostic.
Plan and Evaluate
Resources, and a Baseline
Implementation planning specifies who does what, by when. It also specifies the resources committed to the plan. Time, budget, and personnel. This point deserves to be stated plainly. An unresourced change plan is an announcement, not a plan. A document describing what should happen, without allocating the time and resources to do it, communicates an intention. It doesn't commit the organization to an outcome. And that gap is exactly where many change efforts quietly fail. Evaluation asks what would show the change worked. The answer has to be measured against a baseline, established before the change began. Without that baseline, an organization can't tell genuine improvement from normal variation that would have happened anyway. So establishing the baseline is part of the diagnosis and planning stages. It can't be credibly reconstructed after the fact, once the change is already underway.
Institutionalization
Does the Change Survive Its Champion?
Institutionalization is the stage that decides whether a change survives, past the attention of the people who drove it. It previews the refreezing stage developed fully in Subchapter six point five. Here's the test. Does the change depend on the continued personal attention of its original champion? If so, it hasn't been institutionalized, however successful it looks. Genuine institutionalization embeds the change in structure, measurement, and routine, so it persists independently of any one person. Now put the pieces together, and a familiar failure pattern appears. A strong announcement, paired with weak diagnosis, no resourcing, and no baseline measurement. Then reversion to the previous state, within a year. Each element of that pattern traces to a specific stage being skipped or shortchanged. That's why the process is a full sequence, and not a menu of stages to pick from freely. Lewin's model in Subchapter six point five, and Kotter's eight steps in six point six, elaborate this same process. They don't replace it.
Case Vignette
Solving a Problem Harborline Never Had
Here is a composite case, constructed for instruction. A regional office of Harborline Manufacturing reported persistent delays in processing customer orders. Acting on that presenting problem, leadership approved a new order-management software system, to speed up processing. The rollout was announced with considerable fanfare. But no one had gathered data on where the delay actually occurred, before choosing the software. A brief diagnostic review, done only after the system was purchased, found the processing software had never been the bottleneck. The real delay sat in a manual approval step further upstream. That same approval was still required before an order could even reach the new software. The new system was implemented on schedule, and it worked exactly as designed. And order processing delays continued, almost unchanged. Leadership had jumped from recognizing a need straight to selecting an intervention. It skipped the one stage that would have caught the mismatch, before any money was spent.
About Principles of Management at UPI Study
Principles of Management (Business 101) is a self-paced online course of 117 video lessons in 17 chapters, from the classical schools and the four management functions to leadership, motivation, change, human resources, strategy and ethics. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus Every course with PRO →
Why take it here
Why students take Principles of Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Principles of Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Turning Intention into Action: The Planned Change Process
What is the difference between planned change and emergent change?
What are the stages of the planned change process?
What is the difference between a presenting problem and the real problem?
How do you diagnose a problem before making an organizational change?
About the Principles of Management course
How many college credits is Principles of Management?
How much does Principles of Management cost and what is included?
Which universities accept UPI Study credits?
How long does Principles of Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Principles of Management.
117 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →