CMI Unit 506 Assignment Help — Managing Change

Kotter (1996), Lewin (1951), ADKAR, Evaluate Depth, Management Report Format

CMI Unit 506 assignment help for Managing Change, the operational change management unit of the CMI Level 5 Diploma. The service covers management report format at Evaluate depth, with the three primary change frameworks applied at EAV depth: Kotter’s 8-step change model, Lewin’s force field analysis and unfreeze-change-refreeze model, and the ADKAR individual change readiness framework. Writers hold CMI Level 5 with direct change management experience.

Get a Unit 506 Quote on WhatsApp

What CMI Unit 506 Covers

CMI Unit 506, Managing Change, requires you to evaluate a real change scenario from your professional context using established change management frameworks. The command verb is Evaluate, you must assess what worked, what did not, and why, with framework support and specific evidence. Listing the Kotter steps without applying them to your change scenario is the most common cause of Level 5 referrals on this unit.

CMI Unit 506 Learning Outcomes

Learning Outcome 1: Understand why organisations need to change. The drivers of change, competitive pressure, technological disruption, regulatory change, demographic shifts, and how compelling those drivers are in the specific scenario.

Learning Outcome 2: Understand approaches to managing change. Kotter (1996), Lewin (1951), and ADKAR applied at Evaluate depth, not as a menu of options but as analytical tools for assessing what happened in the change.

Learning Outcome 3: Understand how to engage stakeholders in change. Stakeholder mapping (power-interest matrix), communication planning, and resistance management.

Kotter (1996) — 8-Step Change Model at Evaluate Depth

John Kotter’s Leading Change (Harvard Business School Press, 1996) proposes eight steps for successful organisational change. For Unit 506, the steps are not a checklist, they are an evaluative lens:

Step 1, Create urgency: Was the business case for change communicated compellingly? Did senior leaders communicate the consequences of not changing? Or was change announced without a clear reason why now?

Step 2, Build a guiding coalition: Was there a cross-functional group of influential leaders visibly championing the change? Or did the change have only formal authority (a directive from above) without informal coalition support?

Step 3, Form a strategic vision: Was the desired future state clear and specific? A vision that is too abstract (“we will be more agile”) does not give people a concrete picture of what to do differently.

Step 4, Communicate the vision: Was the vision communicated repeatedly, through multiple channels, by multiple leaders, or announced once and forgotten? Kotter estimates that change communication is typically 1% of what is needed.

Step 5, Enable broad-based action: Were obstacles removed, structural, cultural, or resource barriers that prevented people from implementing the change even when they wanted to?

Step 6, Generate short-term wins: Were early successes identified, celebrated, and communicated? Without visible early wins, momentum stalls and cynicism grows.

Step 7, Sustain acceleration: Was pressure maintained after early successes, or did the organisation declare victory too soon and allow the old ways to return?

Step 8, Institute change: Was the change embedded in culture, systems, and onboarding, so that it persisted even as the original change leaders moved on?

Evaluate depth: For each step, assess with evidence: was this step effectively executed? What was the impact of any weakness? Which single step failure had the most significant consequences for the overall change?

Limitation for Distinction: Kotter’s model is sequential and prescriptive, it implies that change is a managed, linear process. Many real change situations are iterative and emergent, new information, political shifts, and stakeholder responses require adapting the change approach mid-implementation. In complex NHS service redesigns or large-scale commercial transformations, Kotter’s steps often occur simultaneously and in non-linear sequence. Kotter himself acknowledged this in his 2014 revision (Accelerate, Harvard Business Review Press), introducing a dual operating system model for simultaneous change and business-as-usual management.

Lewin (1951) — Force Field Analysis and Unfreeze-Change-Refreeze

Kurt Lewin’s change model has two interconnected components:

Force Field Analysis

Any change situation involves driving forces (pressures pushing toward change) and restraining forces (resistances pushing against change). The current situation is a state of equilibrium between these forces.

At Evaluate depth: list the driving and restraining forces in your change scenario. Evaluate which forces are most significant. Lewin’s evidence: reducing restraining forces is typically more effective than increasing driving forces: pushing harder for change when resistance is strong often increases the resistance. Removing the source of resistance (addressing legitimate concerns, resolving practical obstacles) is more effective than increasing the pressure.

Unfreeze-Change-Refreeze

Unfreeze: Disrupt the current equilibrium, build the case for change, create psychological readiness, challenge the status quo. Without unfreezing, people continue operating in familiar patterns regardless of formal change announcements.

Change: Implement the new ways of working. This is the most visible phase but often receives too much management attention, the unfreeze and refreeze phases are where most change fails.

Refreeze: Embed the change so it becomes the new normal, update systems, policies, job descriptions, and onboarding; celebrate the new behaviours; remove the old ways of working from the environment.

Limitation for Distinction: The “refreeze” stage assumes that a stable endpoint exists after change. In environments of continuous change, digital transformation, regulatory evolution, NHS service redesign cycles, refreezing is problematic. A better metaphor for continuous change environments is Weick’s (1979) “organizing”, change as an ongoing process rather than a transition between stable states.

ADKAR — Individual Change Readiness

The ADKAR model (Prosci, 2006) focuses on change at the individual level, where Kotter and Lewin focus on organisational and group dynamics. Every organisational change succeeds or fails at the level of individual behaviour change.

Awareness: Does the individual understand why the change is happening?

Desire: Does the individual want to support and participate in the change? This is the most critical and most overlooked ADKAR element. A person can have Awareness, Knowledge, and Ability but still choose not to change if they do not Desire to. Desire is influenced by personal motivation (WIIFM, what’s in it for me?) and by their trust in leadership.

Knowledge: Does the individual know how to change, what specific new behaviours, skills, and knowledge are required?

Ability: Can the individual actually perform the new required behaviours? Knowledge of how to change does not guarantee Ability, time, practice, coaching, and support are required to build genuine new capability.

Reinforcement: Are mechanisms in place to sustain the changed behaviour, recognition, incentive alignment, accountability, and consequence for reverting?

Evaluate depth: Identify where individuals in your change scenario most commonly stall on the ADKAR journey. Stalls at Desire require leadership engagement and motivation strategies, not training. Stalls at Ability require coaching, practice time, and resource, not more communication.

Stakeholder Engagement in Change

Mendelow’s (1991) power-interest matrix applied to change stakeholders:

Resistance management: Not all resistance is irrational. Legitimate concerns about job security, workload impact, or quality risk represent important information about change risks. Evaluate whether resistance in your scenario was legitimate concern (requiring response) or status quo preference (requiring influence).

CMI Unit 506 — Pass, Merit, and Distinction

Pass: Kotter’s 8 steps applied to the change scenario. Lewin’s force field and unfreeze-change-refreeze explained. Stakeholders identified. Management report format.

Merit: Kotter steps evaluated for execution quality, with specific evidence for the most and least effective steps. Lewin’s force analysis applied, driving vs restraining forces assessed and the most significant identified. ADKAR individual stall points identified. Stakeholder engagement evaluated against power-interest matrix. SMART change management recommendations.

Distinction: Kotter limitation named (sequential model; Kotter 2014 revision acknowledged). Lewin refreeze limitation named (problematic in continuous change environments). ADKAR Desire as the most overlooked element, evaluate whether the change communication strategy addressed WIIFM or assumed awareness created desire. Original conclusion: which single change management failure most significantly explains the outcome of the change scenario?

WhatsApp for Unit 506 Help

CMI Unit 506 — Common Questions

What is the difference between Kotter and Lewin for CMI Unit 506?

Kotter (1996) is a leadership-centric sequential model, it prescribes eight specific actions that leaders must take in order. It focuses on what leaders should do at each stage. Lewin (1951) is more diagnostic, it helps managers understand the force dynamics before deciding on action. Kotter tells you what to do; Lewin helps you understand why the change is meeting the resistance it is. For Unit 506 Evaluate depth, use both: Kotter to evaluate the leadership actions taken at each stage, Lewin to evaluate why resistance occurred and whether the right approach was taken to address it.

What is ADKAR and why does it matter for CMI Unit 506?

ADKAR is an individual-level change readiness model, it identifies where specific people or groups stall in their change journey. Kotter and Lewin analyse change at the organisational level; ADKAR explains why some individuals adopt the change and others don’t. It matters for Unit 506 because change always happens at the individual level, organisational change is the aggregate of individual behaviour changes.

How many SMART recommendations should a CMI Unit 506 management report have?

The minimum is typically three SMART recommendations. For Unit 506, recommendations should address specific change management weaknesses identified in the evaluation, not generic advice about communication or engagement.

How do I get CMI Unit 506 help?

Send your unit brief, change scenario, target grade, and deadline via WhatsApp. A quote is returned within 2 hours. A writer with CMI Level 5 and direct change management experience is assigned.

The Harvard Business Review publishes peer-reviewed strategic management research that provides the evidence base for the Evaluate and Justify depth required in this CMI strategy unit.

WhatsApp for CMI Unit 506 Help