Change Management Programme Issue Log
This is a practical guide to building a issue log for a change management programme project — a register of problems that have occurred and need resolving, adapted to the realities of delivering large-scale organisational change.
What a Issue Log is
A issue log is a register of problems that have occurred and need resolving. For the full concept and how it works in general, see Issue Log. On a change management programme project it plays the same role, tuned to this kind of work.
Why it matters for a Change Management Programme project
Change Management Programme projects live or die on delivering large-scale organisational change. A well-built issue log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how change management programme projects drift into avoidable delay and cost.
What to include
- Issue description
- Priority and severity
- Owner
- Resolution and status
Change Management Programme-specific considerations
Tailor the issue log to the risks that most often derail change management programme projects:
- Resistance to change
- Sustaining adoption
- Leadership alignment
Example
On a real change management programme project, the issue log would be shaped by delivering large-scale organisational change. In particular, it should explicitly account for the project’s biggest risks — resistance to change, sustaining adoption, leadership alignment — rather than treating them as afterthoughts.