PRINCE2: Moving with the times

PRINCE2 has stood the test of time as an essential component of project management. Its transition from rigid origins to a flexible, adaptive methodology reflects not only changes in the framework but also shifts in how industries such as construction approach complexity. As a PRINCE2 Practitioner and COO in the construction industry, I’ve seen its transformative effects first-hand. The evolution of PRINCE2 — from its inception to its current iteration — shows how project management methodologies must evolve to remain effective in dynamic environments.

Modern PRINCE2 places a much greater emphasis on flexibility, which has made it far more practical for industries like mine. I discovered this firsthand when I implemented PRINCE2 in our construction operations. Tailoring is no longer a suggestion but rather a key component of the framework. This is especially evident in how modern PRINCE2 enables project managers to tailor its principles to the scope and complexity of the task at hand.

This adaptability came in handy last month when I managed a roofing and scaffolding project with tight deadlines and multiple stakeholders — the type of project that would have drowned in paperwork under the old system. Early versions of PRINCE2 may have slowed the process down with excessive documentation, requiring more time to comply than execute. Instead, we focused on what was most important: clear communication through daily site meetings, defined roles for each subcontractor team, and transparent decision-making. We achieved efficient results while maintaining quality by eliminating unnecessary overheads.

The modern framework also values outcomes over deliverables. Early PRINCE2 versions prioritised task completion, which sometimes came at the expense of delivering real value. Today, the methodology encourages project teams to regularly assess whether their efforts are aligned with stakeholder needs and provide tangible benefits. This is something I see every day in construction, where balancing cost, safety, and client satisfaction is more than just a theoretical concept; it can mean the difference between a successful and a troubled project.

One of the most significant changes I’ve seen across different industries, over the last 20 years, is PRINCE2’s integration of collaboration. Traditional project management frequently treated different phases as siloed operations, with little interaction among teams. Modern PRINCE2, with its emphasis on continuous communication and stakeholder engagement, more accurately reflects the interconnected nature of modern projects. This is consistent with how we work in construction, where site managers, architects, and subcontractors must collaborate to achieve success. Just last week, we used this integrated approach to resolve a complex foundation issue in hours rather than days.

Looking back, PRINCE2 was developed to provide structure during a period when projects were linear and predictable. Early concepts, such as PROMPT, emphasised control and documentation, which was appropriate for large, resource-intensive IT projects in the 1970s. However, today’s projects, particularly in construction, are rarely this simple. The scaffolding projects I oversee today are vastly different from the IT systems for which PRINCE2 was originally designed. However, the methodology’s core principles — clarity of roles, well-defined processes, and an emphasis on outcomes — remain equally valuable.

The transition from rigid control to flexibility reflects broader shifts in how industries approach complexity. Early versions of PRINCE2 were effective for large-scale projects, but bureaucracy frequently created bottlenecks. Modern PRINCE2 recognises that one size does not fit all. Its adaptability enables project managers to maintain structure while addressing changing challenges.

For example, the tailoring principle has enabled us to streamline processes, reduce unnecessary documentation, and concentrate on providing genuine value to stakeholders. This evolution has been critical in construction, where projects frequently require quick problem solving, dynamic collaboration, and meticulous oversight to ensure safety and compliance.

The journey of PRINCE2 demonstrates its ability to grow alongside the industries it serves. From its beginnings with PROMPT to its current version, the methodology has evolved to meet the needs of real-world projects. Its relevance today stems from the recognition that structure and flexibility are not mutually exclusive, but rather necessary partners in effective project management.

Whether in 1980s IT systems or 2024 scaffolding projects, PRINCE2 remains an essential tool for navigating complexity, ensuring success, and delivering meaningful results. For those of us in the construction industry, its evolution has not only improved how we work but also ensured that we meet the ever-changing demands of our profession.


Paul Brothwood

By Paul Brothwood

BA(Hons) DipFSM DipFA CeFA CeMAP PIEMA REnvP TechIOSH PRINCE2 & ITIL4 Practitioner, SMSTS accredited & Scaffold Inspector (CISRS)

Comments

Post a Comment

Popular posts from this blog

Can Bushido (Samurai Code) help small businesses achieve environmental sustainability?

Image
As the Chief Operating Officer of a small construction company, I’ve often faced the challenge of making environmental sustainability part of our daily work. Adopting eco-friendly practices can feel daunting for smaller businesses, which don’t have the resources of larger firms. However, I found unexpected inspiration in Bushido, the ancient samurai code. Bushido emphasises values like integrity, discipline, and loyalty — qualities that resonate with me as I guide our company toward a more sustainable path. While the samurai applied these principles in their own way, modern businesses can use them to shape responsible, environmentally conscious operations, particularly in industries like construction, where sustainability is often seen as costly or complicated. Here’s how I think Bushido can help small businesses make meaningful environmental progress, even with limited resources. Gi, or rectitude, is about making the right choices, even when they’re difficult. For small businesses, th...
Read more

Being a Project Manager at Three Years Old

Image
At the age of three, I was diagnosed with Type 1 diabetes, and everything seemed to change. Suddenly, life presented me with a complex and demanding project: managing a disease that does not take breaks and can be both unpredictable and, frankly, deadly. While most children were playing and learning, I was learning about blood sugars, injections, and counting each bite of food. I didn’t let it overwhelm me; instead, I took control early on to ensure that diabetes would never get in the way of the life I desired. Managing Ty pe 1 diabetes is a demanding daily task. From a young age, I oversaw my own injections, which were often five per day, and meticulously tracked everything I ate and drank. Living with diabetes is no easy task, especially when blood sugar levels can fall dangerously low. However, this “project” never became a limitation. It taught me discipline, precision, and resilience — all of which are necessary skills for project managers, even before I knew what they were. Desp...
Read more

Reflections on ITIL: From Fundamental Ideas to Modern Practices

Image
As the COO of a construction company and an ITIL4 Practitioner, I’ve experienced how foundational ITIL concepts shape daily operations and the overall business framework, particularly in a dynamic and high-stakes industry like construction. Information Technology Infrastructure Library (ITIL), which originated in the 1980s, began as a method for bringing consistency to IT management. Today, ITIL4 focuses on flexibility, incorporating Agile and DevOps principles, making it applicable beyond traditional IT environments. ITIL began with a focus on control. The structured approach emphasised documentation, standardisation, and repeatability, all of which are necessary for consistent IT service management. Back then, it was all about minimising risk through rigid processes, and it was heavily centralised. While that approach was effective at the time, it was often slow and rigid, particularly when applied outside of IT. The most recent ITIL4 framework, however, emphasises collaboration and ...
Read more