Competing with Existing Processes
There might be existing processes competing with the PRINCE2 method. Colleagues might get offended if you want to "steal" their process. Engage stakeholders early and incorporate their vocabulary.
Inconsistent Implementation
Project managers implement their own version of PRINCE2. You need one single standard to avoid confusing the organisation — define it clearly and apply it consistently.
Unfamiliar Approach
Incorporate vocabulary and processes that already exist in the organisation. That way PRINCE2 feels familiar and less of a change — making adoption much smoother.
Excessive Bureaucracy
Only implement and demand what the organisation is able to turn into value-added processes. You have lost if the organisation ends up with a lot of "write-only" documents that nobody reads.
Excluding Stakeholders
Stakeholders, board members and team managers also need to be trained and helped to understand their role. PRINCE2 is not just for Project Managers.
Overestimating the Methodology
PRINCE2 is just a method and doesn't help you develop communication or planning skills. It does not help with teamwork, conceptualisation or analysis — those require separate investment.
Document-Focused Language
Discuss "information and decisions" rather than documents and processes. Documents are just the vehicle — the real value is in the thinking, the dialogue, and the decisions they enable.
Successful implementation of PRINCE2 in your organisation is not straightforward, but it helps if you avoid the implementation traps described above.
See the full 10-Step Implementation Guide for a proven, gradual approach to rolling out PRINCE2.