Cost Reduction Programme Decision Log
This is a practical guide to building a decision log for a cost reduction programme project — a record of the key decisions made, by whom and why, adapted to the realities of delivering a structured cost-reduction initiative.
What a Decision Log is
A decision log is a record of the key decisions made, by whom and why. For the full concept and how it works in general, see Decision 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 decision 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
- Decision
- Date and owner
- Rationale
- Alternatives considered
- Impact
Cost Reduction Programme-specific considerations
Tailor the decision 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 decision 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.