Change Mgmt common mistakes
Change Mgmt · Understand the traps and how to avoid them.
Treating 'change management' purely as organisational change and answering process questions with culture and stakeholder language, or the reverse - answering organisational questions with change-request, CAB and rollback language.
The exam blends two distinct domains and both share the same vocabulary, so candidates latch onto whichever meaning they met first and apply it indiscriminately to every stem.
What to do instead
Before answering, classify the stem: if it mentions change requests, RFCs, CAB, impact assessment, rollback, baselines or configuration items, use domain 1 (change management knowledge, SFIA 3). If it mentions readiness, adoption, resistance, sponsorship, change curve or benefits realisation, use domain 2 (organisational change, SFIA 4). Practise sorting 20 mixed stems into the two buckets before answering any of them.
Describing change management as an administrative or approval-only activity - 'logging requests and getting sign-off' - when asked what the practice is for.
Candidates recall the visible paperwork (tickets, approvals) rather than the purpose, which is to enable beneficial change while managing risk and minimising disruption.
What to do instead
Anchor answers on purpose and outcome: assess impact and risk, authorise appropriately, schedule and coordinate, and protect service stability while enabling change. Reject any option that reduces the discipline to record-keeping or gatekeeping.
Confusing the change types - treating a standard/pre-approved change as needing a full CAB review, or routing an emergency change through the normal weekly board.
The three categories (standard, normal, emergency) are learned as labels without the decision rule that distinguishes them: risk, recurrence and urgency.
What to do instead
Memorise the rule, not the labels: standard = low risk, well understood, pre-authorised, repeatable; normal = assessed and authorised through the defined route proportional to risk; emergency = implemented fast under defined authority and documented retrospectively. For each practice question, ask which of these three the scenario describes before looking at options.
Choosing 'escalate to the change manager' or 'reject the change' as the default answer whenever a scenario shows a risk or conflict, rather than selecting assessment, mitigation or proportional authorisation.
Exam stems are written to feel risky, and escalation feels like the safe, responsible-sounding option; candidates also assume the change manager personally decides everything.
What to do instead
Prefer answers that assess impact, identify and mitigate risk, and route the decision to the accountable authority at the right level. Escalation is correct only when authority genuinely sits above the role in the scenario, and rejection only when risk cannot be mitigated. Learn who owns what: change manager coordinates and enables; the accountable owner authorises.
Ignoring the rollback or back-out plan, or treating it as optional, when evaluating a change proposal in a scenario.
Candidates focus on the forward plan and benefits and skim past the remediation element, which is often the discriminator between two plausible options.
What to do instead
For any change-assessment question, check four things: impact and risk assessment, test evidence, back-out/remediation plan, and scheduling around business constraints. If one option includes a credible back-out and another omits it, the one with it is usually correct.
Treating resistance to organisational change as a communications problem to be fixed by more email or a better slide deck.
Communication is the most familiar and easiest lever, so candidates reach for it; resistance is actually frequently rational, rooted in loss of competence, workload, status or uncertainty.
What to do instead
Diagnose before prescribing: distinguish rational resistance (genuine concerns, valid information) from emotional response and from organisational/political blockers. Match the response - genuine engagement and involvement for rational concerns, visible leadership and support for emotional response, sponsor intervention for political blockers. Choose communication only when the stem shows an information gap.
Assuming a single sponsor announcement or a one-off town hall creates commitment, and selecting 'communicate the vision once at launch' style options.
Candidates underestimate the timescale of organisational change and treat it as an event with a launch, rather than a sustained process over months.
What to do instead
Look for answers with sustained, repeated, multi-channel engagement, active and visible sponsorship throughout, and reinforcement after go-live. Treat one-off communication options as distractors unless the stem specifically concerns an information deficit at a single point.
Designing change activity without defining measurable success - accepting 'improve efficiency' or 'increase awareness' as an outcome.
Candidates conflate activity (training delivered, communications sent) with outcome (adoption, benefit realised) and default to soft, unmeasurable language.
What to do instead
For every change-plan question, insist on a baseline, a target and a measure: adoption rate, process compliance, cycle time, error rate, benefit realisation against the business case. Reject options that only count outputs (sessions held, emails sent) and prefer options that tie back to the original case for change.
Applying a fixed, linear change model as a recipe - reciting the stages of a curve or model and picking the option that names the next stage - instead of using it to interpret the scenario.
Models are memorable and give a comforting structure; candidates memorise sequences without learning what each stage implies for the intervention a change manager should make.
What to do instead
Learn each model as a diagnostic lens: what people typically feel and do at each stage, and what leadership response that stage calls for (information and direction early, involvement and support through the dip, reinforcement and recognition later). Answer by matching the described behaviour to the stage, then choosing the intervention appropriate to that stage.
Overlooking the wider system - ignoring stakeholders outside the immediate team, or ignoring how the change interacts with other concurrent initiatives, technology, reward structures and processes.
SFIA level 4 requires coordinating change across a programme and its environment, but candidates answer at team level, focusing on the people directly affected and forgetting dependencies and cumulative change load.
What to do instead
Before choosing, scan the stem for signals of scale: multiple business units, parallel projects, suppliers, regulators, unions, customers. Prefer answers that map stakeholders across the whole affected system, sequence and de-conflict with other changes, and align processes, measures and rewards with the new way of working. Reject team-only plans when the scenario is organisation-wide.