“Working in a structured manner does not mean that nothing can go wrong.”
1. No or too little tailoring
Many people think that you should always apply PRINCE2 in its entirety, regardless of the size of the project. This is not true. The key word is 'tailoring': you adapt PRINCE2 to your situation.
- Pitfall: You roll out the method blindly without critically examining which components really add value.
- This is how you prevent it: At the beginning of each project, create a tailoring plan. Determine which processes, roles, and documents are useful for your purpose. Keep it simple where possible, and elaborate when necessary.
2. Unclear division of roles
PRINCE2 is crystal clear about roles and responsibilities — in theory. But in practice, it can be unclear who is really ultimately responsible, or who should track risks.
- Pitfall: Roles that overlap, causing you to unnecessarily get in each other's way.
- This is how you prevent it: At the start, plan a session to discuss and record the division of roles. Include this in your project initiation document (PID). Questions? Ask them right away, so everyone knows exactly what to do.
3. Too little attention to risks
Risk management is the beating heart of PRINCE2. Yet this part is sometimes dismissed quickly, or forgotten altogether.
- Pitfall: You focus mainly on planning and deliverables, while potential problems pile up in the background.
- This is how you prevent it: Set up a risk log and review it regularly with your team. Discuss risks and evaluate whether you need to adjust your measures. This way you won't be running behind the facts.
4. Losing sight of the Business Case
PRINCE2 emphasises 'continuous business justification': why are we doing this project and is it still delivering the desired value?
- Pitfall: You only formulated the Business Case in the start-up phase. Then it disappears into the drawer and you never see it again.
- This is how you prevent it: Discuss each phase or sprint again whether the project still fits the company goals. Adjust the Business Case where necessary. This way everyone in the team knows why they work hard on this project every day.
5. Lack of knowledge and cooperation
Although PRINCE2 is a clear framework, it does require practice to really master the methodology.
- Pitfall: You rely on self-study or isolated experience, without deep insight into the underlying principles.
- This is how you prevent it: Invest in good training or e-learning, so that you learn the subject matter and best practices from the field. Also exchange experiences with colleagues or other project teams.
PRINCE2 stands or falls with how you set up and apply the methodology. Do you want more control over these pitfalls? Take a look at our PRINCE2 training or e-learning modulesThis way you keep your projects manageable, clear and — importantly — enjoyable for you and your team.
