Thursday, February 26, 2015

A Fool with a PRINCE2 Tool is Still a Fool

PRINCE2, with its generic method approach and the specific tribal language, is the perfect gift for a fool who needs a new tool to misuse. Throwing templates, processes and language around can create frustration at a steaming level.

Here are a few PRINCE2 implementation mistakes you should avoid if you don’t want to end up as the fool with the PRINCE2 tool:

  • Don’t rush 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. Others might not understand why one process should be replaced by another.
  • Don’t let project managers implement their own version of PRINCE2. You need one single standard to not confuse the organization.  
  • Don’t be a stranger. Incorporate vocabulary and processes already existing. That way PRINCE2 feels familiar and less of a change.
  •  Don’t be bureaucratic. Only implement and demand what the organization is able to turn into value added processes. You have lost if the organization ends up with a lot of “write-only” documents.
  • Don’t leave the rest of the organization behind. Stakeholders, board members and team managers also need to be trained and helped to understanding their role.
  •  Don’t assume PRINCE2 will make good project managers. PRINCE2 is just a method and doesn’t help you develop communication or planning skills. It does not help you with team work, conceptualization or analysis.

Successful implementation of PRINCE is your organization is not straight forward, but it helps if you avoid the traps described above.

Related articles:

 Image courtesy of supakitmod at

Copyright © PRINCE2How2 - How to implement PRINCE2

No comments:

Post a Comment