Issue Register for day to day work?
I've seen the concept of an Issue Register in PRINCE2 but that would for issues and risks during a project that well end as they all should do.
I've never used one in practice for either a temporary project or day to day work.
I envisage for day to day work that comes into an operational team that the same concept can be used so that a team is asked to log an issue or risk so managers are aware it exists. Once the status column changes to 'Resolved' etc then it will filtered or moved off the current list.
Is this use commonplace and any pitfalls I have missed for using a project management tool in this way?
Marcee last edited by
The PM industry--if that is a thing--does not own exclusively its tools. If you find that the issue log, or any tracking and control log, works in your work, use it. The pitfalls in using a log is not really about the log itself but more about how it is used. Some cons I have experienced are:
- it becomes a deliverable of and in itself, versus a dynamic and dirty tool;
- teams start one but don't really use it, in order to check off some requirement;
- there are unending arguments about what goes in and what does not; and
- teams end up using it as the reporting mechanism
Logs are simply meant to track items, maintain some data attributes on each item for prioritization or other metric inputs, hold responsibility and accountability for some party, and to be an input to other reporting requirements. These are all good things for both project and operation environments.