A common and damaging mistake in PRINCE2 project management is mislabelling issues by their consequences rather than their root causes. Project Managers record issues titled "Project Delay," "Extend Stage," or "Higher Cost" — but these are outcomes, not issues. They describe what will happen if the issue isn't resolved, not the issue itself.
Consequences vs. Root Causes
When you name an issue by its consequence, you make it harder to resolve. "Project Delay" tells the Project Board that something is wrong — but it gives them no information about what is causing it, who owns it, or what action is needed. It also conflates multiple different problems that may have the same effect but require entirely different responses.
Ask Why
When looking at an issue, always ask "Why?"
- Why will there be a project delay? — Because a key supplier has not delivered the agreed specification on time
- Why will the cost be higher? — Because the scope of the integration work was underestimated during initiation
- Why does the stage need extending? — Because a dependency on the legal team was not identified in the Stage Plan
Use the answer to this question as the Issue Title and the basis for the Issue Description. This approach enables clearer communication with stakeholders and more precise issue management.
Why This Matters
A well-defined issue title and description enables the Project Board to make informed decisions. When an issue is presented as "Supplier X has not delivered Component Y by the agreed date of [date], impacting the integration testing schedule by an estimated two weeks," the board can make a meaningful decision. When it is presented as "Project Delay," they cannot.
See also: Yes, It is a PRINCE2 Issue and Issue Rating Scales.