Cost Reduction Programme Issue Log
This is a practical guide to building a issue log for a cost reduction programme project — a register of problems that have occurred and need resolving, adapted to the realities of delivering a structured cost-reduction initiative.
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 cost reduction programme project it plays the same role, tuned to this kind of work.
Why it matters for a Cost Reduction Programme project
Cost Reduction Programme projects live or die on delivering a structured cost-reduction initiative. 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 cost reduction programme projects drift into avoidable delay and cost.
What to include
- Issue description
- Priority and severity
- Owner
- Resolution and status
Cost Reduction Programme-specific considerations
Tailor the issue log to the risks that most often derail cost reduction programme projects:
- Benefit measurement
- Impact on service/quality
- Sustaining savings
Example
On a real cost reduction programme project, the issue log would be shaped by delivering a structured cost-reduction initiative. In particular, it should explicitly account for the project’s biggest risks — benefit measurement, impact on service/quality, sustaining savings — rather than treating them as afterthoughts.