Tips on using the issues log G G G G G G G Phrase the issue as a question; this is more powerful in helping to focus on a solution. Have only one issue per `line'. Grouping a number of issues together (even if related) makes identification of a solution difficult. Do not add to existing issues or they will never be resolved; record a new issue if a different facet becomes apparent. Make cross-references between issues or refer back to the risk or opportunity logs (by a note in the `comment' column) if this is helpful. Keep all issues visible, even those which have been resolved, as this shows achievement in overcoming problems and exploiting opportuni- ties. It also acts as a check in case the same issue resurfaces later. Shading completed issues makes it clear which are live and which are resolved. If the resolution of the issue requires a project `change', put a cross ref- erence to the change log in the resolution column. Be open with your issues log; share it with the project team and others on whom the project will have an impact. A manufacturing organisation was relocating its works. It was intended that the existing plant would be moved and operated in the new location. After the site was acquired and construction was almost completed an issue was raised under European legislation that the old plant would not be allowed to run in the new location. It was deemed to be a new site and hence all plant had to conform to new emission restrictions immediately. An issue was logged and immediately escalated to the project sponsor as the project manager had no knowledge or power to deal with this. The pro- ject sponsor quickly circulated the problem among various contacts within the organisation. Very soon a specialist unit was identified in the head office that was able to review the issue. It found that the issue was a misinterpre- tation of the legislation and was not valid. The issue was potentially a show stopper for the project. By identifying it and describing it accurately, however, the issue was able to be circulated and resolved (or in this case dissolved). A potentially very expensive change to the project was thus avoided. 426 PA R T F O U R · M A K I N G P R O J E C T S W O R K F O R Y O U