APMG Agile Change Agent cheat sheet

A roadmap sequences change activities over time and shows dependencies between workstreams, distinct from a project schedule that fixes dates and tasks.

Roadmap horizons are typically Now, Next, Later; detail decreases as the horizon extends, so later items are indicative rather than committed.

Each roadmap entry states the change, the business benefit expected, the owner, and the dependency on other entries.

Change is delivered in increments or releases; the roadmap shows the order of increments and the value released at each point.

A roadmap is a communication tool for stakeholders and a planning tool for the change team; it is reviewed and re-baselined at agreed intervals.

Roadmap milestones mark decision points and value-realisation points, not only delivery completion.

Dependencies that cross organisational boundaries are recorded on the roadmap so that sequencing conflicts surface early.

The roadmap links business needs to delivery activity: every roadmap item traces back to a stated need and forward to an outcome measure.

A business need states the gap between current and desired performance, expressed in outcome terms rather than in solution terms.

The case for change links the need to expected benefits, costs, risks, and the consequence of doing nothing.

Benefits are defined with an owner, a measure, a baseline, and a target; without a baseline the benefit cannot be evidenced.

Stakeholder needs and business needs are distinct; the change must satisfy the business need while addressing stakeholder interests.

Requirements are derived from the business need and are prioritised (for example must-have, should-have, could-have) so scope can flex.

The business need is re-validated at each roadmap increment; if the need no longer exists, the change should be stopped or reshaped.

Change impact assessment identifies who is affected, how, and to what extent, and feeds the relationship and environment plans.

Outcome measures are agreed before delivery begins so that benefit realisation can be assessed after the change lands.

Stakeholder analysis maps each stakeholder's interest, influence, and attitude (supporter, neutral, blocker) to determine engagement approach.

The engagement approach varies by quadrant: high influence and high interest need close involvement; low influence and low interest need monitoring only.

Trust is built through consistent, timely, honest communication; a single surprise erodes credibility faster than repeated good news builds it.

Communication planning defines audience, message, channel, frequency, and sender; the sender should be the person the audience trusts.

Resistance is a signal of unmet need or unmanaged impact, not a personality defect; diagnose the cause before responding.

Co-creation with affected stakeholders increases ownership and reduces the likelihood of late resistance.

Sponsors and line managers are the primary channels for change messages; the change team supports rather than replaces them.

Relationships are maintained after go-live; benefit realisation depends on continued engagement with adopters and their managers.

The change environment includes organisational culture, structure, processes, technology, and the external context in which the change lands.

Culture assessment identifies whether the organisation rewards stability or adaptability; the change approach must fit or deliberately shift it.

Readiness assessment checks capability, capacity, and willingness of the receiving area before go-live; low readiness predicts failed adoption.

The receiving environment must have the skills, tools, and authority to sustain the change after the change team withdraws.

Organisational capacity for change is finite; concurrent changes compete for the same people's time and attention and must be sequenced.

Governance defines decision rights, escalation routes, and stage gates; it must be proportionate to the size and risk of the change.

Environmental constraints (regulation, legacy systems, contracts) are recorded as assumptions or constraints that shape the roadmap.

Transition planning covers handover to business-as-usual, including support models, documentation, and ownership of the new ways of working.