Does your organisation need a Chief Project Officer?

Ways of Working
7 Jun
Written By Yuyan Wang

Key takeaways:

Thirty years ago, 80% of a company's resources went to operations and 20% to projects; today, it's the other way round. Despite this massive disruption, most organisations don't have a senior leader overseeing change and transformation.

Lack of clarity and ownership often leads to silo thinking, project overload, demotivation, projects not completed, and a tremendous amount of resources wasted and value lost in the project space.

This is why companies need a Chief Project Officer (CPO) or equivalent to manage change.

CPOs go beyond direct project sponsorship. Their responsibilities include, but are not limited to:

• Fostering a collaborative and empowering culture across silos and adopting a project-driven structure for their organisation.
• Working with the rest of the senior executives to develop programs, initiatives, and projects that are aligned with the organisation's strategy.
• Making sure projects are appropriately selected, prioritised, and resourced according to the strategic goals of the organisation.

Source: The Rise of the Chief Project Officer, by Antonio Nieto-Rodriguez, April 26, 2022