2.3 Planned Change versus Emergent Change

There are two ways that change happens in an organisation. Change is planned and delivered strategically, usually driven from the top. Or change emerges from somewhere — usually starting small, gaining support and momentum, and growing. CM3 asks you to distinguish them, and the exam tests the comparison line by line.

The full comparison

Read the third row carefully. Planned change may consult widely and at all levels — consultation is not what distinguishes the two. Candidates often assume "planned means imposed" and get caught. What distinguishes them is where the initiative and the shaping come from, and how defined the destination is.

Recognising which one you have

Three diagnostic questions:

1. Can you describe the finished state precisely? "Every employee is in the new building by 1 March" is planned. "Customer service is noticeably better" is emergent.
2. Is there a task list, or a direction of travel? A well-defined plan or list of tasks points to planned change. An experimental, step-by-step approach that tests what works points to emergent change.
3. Where do new initiatives come from? If local line leaders are starting their own related initiatives and the centre is supporting rather than directing them, that is emergent change working as intended.

Why the distinction changes what you do

The two types demand different change management:

• Planned change justifies detailed communication plans keyed to milestones, training scheduled close to a fixed go-live, and progress reporting against a task list. The change manager's risk is people arriving at a fixed date unprepared.
• Emergent change demands feedback loops, visible sharing of what is working, and mechanisms to spread local successes. The change manager's risk is drift — activity without direction — and the antidote is a clear, repeatedly communicated direction of travel even when the destination is fuzzy.

A practical consequence: in emergent change, success stories are a delivery mechanism, not just publicity. When a team finds a better way of handling a customer complaint and you spread that story, you are literally doing the delivery. In planned change, the equivalent activity is readiness assurance.

Hybrids are normal

Most real initiatives contain both. A digital transformation typically has a planned core — the systems go live on a date — wrapped in an emergent shell, because how people end up working with the systems evolves over months and cannot be specified in advance. The change manager's job is to notice which part they are in and stop applying planned-change discipline to emergent-change problems.

That mismatch produces a recognisable failure pattern: a change team reports 100% of planned activities complete while the business reports nothing has really changed. Every planned output was delivered, and the emergent outcome — how people actually work — was never managed. This is exactly the outputs-versus-outcomes gap, seen from the delivery side.

Emergent change and the wider syllabus

Emergent change connects directly to several later topics. It sits naturally in Cynefin's complex domain, where an experimental, emergent approach is advised. It relies on co-design, because the people doing the work shape the solution. It is supported by the continuous change management cycle, whose feedback-driven loop is built for exactly this situation. And it depends more heavily on personal power sources than positional ones, because nobody is being ordered.

Sponsorship looks different in each type

The sponsor's job does not disappear in emergent change; it changes shape. In planned change the sponsor legitimises a defined destination, holds the deadline and confronts blockers. In emergent change the sponsor holds the direction rather than the destination, protects the space in which local initiatives can start, and resists the pressure to convert a genuinely emergent programme into a plan with dates so it can be reported on conventionally.

That pressure is real and it is where most emergent programmes fail. A steering group asked to oversee something with a fuzzy end point will, in good faith, ask for a plan. Producing one manufactures precision that does not exist, and the programme is then measured against invented milestones. The honest alternative is to report progress in the terms the change actually has — what has been tried, what worked, what spread, and what the direction of travel now looks like.

Measuring each type

The two types also need different evidence:

Applying planned-change measures to emergent change produces the most misleading report in change management: full completion of every scheduled activity alongside no observable difference in how anyone works.