Process Improvement Issue Log
This is a practical guide to building a issue log for a process improvement project — a register of problems that have occurred and need resolving, adapted to the realities of improving an existing business process.
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 process improvement project it plays the same role, tuned to this kind of work.
Why it matters for a Process Improvement project
Process Improvement projects live or die on improving an existing business process. 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 process improvement projects drift into avoidable delay and cost.
What to include
- Issue description
- Priority and severity
- Owner
- Resolution and status
Process Improvement-specific considerations
Tailor the issue log to the risks that most often derail process improvement projects:
- Change resistance
- Measuring the baseline
- Scope discipline
Example
On a real process improvement project, the issue log would be shaped by improving an existing business process. In particular, it should explicitly account for the project’s biggest risks — change resistance, measuring the baseline, scope discipline — rather than treating them as afterthoughts.