Resources

What does your capital portfolio ‘current state’ reveal?


Organisations know solutions are available to better manage risk and optimise outcomes in their capital project and portfolio management. But many aren’t aware of the growing risks being created by inconsistent, siloed and manual processes.
CAPEXinsights Business Case for Change Lead, Kim Featherstone, discusses the issues surfaced during assessments of capital project and portfolio practices in leading organisations.

We know there’s a better way. We just don’t have time to stop and figure out what it is.

That’s a typical comment from the stakeholders we interview as we conduct ‘current state’ assessments of capital project delivery, risk management, and reporting processes as part of our ‘Business Case for Change’ service. In these assessments, we leverage industry best-practice to benchmark six aspects of project and portfolio management to establish where organisations are at. This in-depth analysis helps organisations make informed decisions about the right solution for their capital project and portfolio management practices.

Why organisations should do a Business Case For Change

Organisations reach out to us for two main reasons: either someone from the capital projects team has been tasked with finding improvements to processes, or decision-makers are seeking greater transparency and insight from the portfolio.

Often, clients think they know where the issues are and that the case for change will simply confirm this. In fact, they typically underestimate the changes required. Adopting a project and portfolio management solution can represent a significant change for many organisations, involving multiple communities with different needs and levels of delivery maturity and approach.

What our clients discover is that successful capital delivery is about integrating systems, processes, and people – and a case for change requires analysis of all three. 

Systems

Multiple systems mean manual rework, mistrust in data, and lost hours manipulating spreadsheets. With no central platform to view and manage portfolios, underspend is typical, but portfolio managers have no easy way to see this and no way to react.

  • A European food manufacturer we worked with had built a comprehensive system to allocate and control capex. But the system was entirely disconnected from the systems used to deliver the projects. Data used to calculate a business case for capex approval was invisible to the delivery and governance teams, with the resulting risk that projects could diverge from their original intent without oversight.  

This type of scenario is why we’re often called in when boards are concerned about the governance of capex projects. Understandably, directors and executives worry about poor visibility across what can be billion-dollar portfolios. They want to get a high-level read on the current status of capital and to understand risk at any given moment in time.  

More recently, the impetus for increasing visibility in the portfolio has also come from sustainability officers who need to build carbon calculations into capital project decisions and ensure capital portfolios align with sustainability strategies. 

  • Another European client had doubled their capital budget to meet their sustainability goals. This new challenge needed a new system to both calculate the return from a carbon perspective, but also to dynamically compare scenarios based on long-term decarbonisation goals, asset replacement needs, and shifting fuel and carbon prices.

Processes

Typically, after conducting multiple stakeholder interviews, even in larger organisations it’s common to find very few or siloed standardised processes for delivering or governing capital projects. While our interviewees usually have an excellent grasp of the fundamental principles of project management, this knowledge often comes from previous organisations. Individual project managers are highly competent but have brought in their own systems and processes to fill gaps – relying on individual competency over process.

This results in wide variations in delivery styles, risk management, and reporting methods. Often, we see similarities in capex approval processes and major control points, but very different lifecycles in the run-up to pre-capex gates. We’ve had cases where delivery teams were creating new ways of working each time, effectively making everyone relearn processes, leading to delays and variable outcomes. Even when teams retained processes after the project, the knowledge was held with individuals and remained undocumented.

  • A large dairy company needed to consolidate its ways of working to deliver on business growth strategy. At the time, multiple communities were all running capital projects, with their own central capex office. Each community was running parallel processes and their own lifecycles. They were protective of their way of working and resistant to change.

Once people can see the inefficiencies and duplication, communities can jointly agree to pare back and reconfigure processes. This shows the value from having a single common delivery language and the ability to share learnings and insights. Running the Business Case For Change process brings all the voices together to understand the full picture.

People

We’ve spoken to some passionate and highly experienced project managers. But companies with great project managers often find individual heroics are masking inadequate processes.  

  • A global minerals processor we spoke to found that relying on experienced individuals actually impacted both performance and culture. With no clear guidance on what the business wanted, talented project managers suddenly felt ineffectual.

When teams lack standard processes or role clarity, people fall into defensive behaviour and lack appreciation for the value of each role. Those left to sort out their own ad-hoc reporting are often scrambling to produce a hurried paper trail to justify decisions.

  • A Trans-Tasman food processor had a small, busy geographically dispersed project management team. Our Business Case For Change process uncovered ‘forgotten’ site teams – removed from central engineering – forced to use project processes that were not designed for them.

When caught between the site manager and engineering, you can become slaves to 2 masters, battling the system to get essential maintenance projects prioritised against a business strategy that favours projects with a higher internal rate of return. This is what happened in this instance. 

The advantages of undertaking a Business Case For Change

 

Building a Case For Change requires detailed analysis to inform the business case for a capital project solution, however, it also helps organisations understand what’s possible and where the inefficiencies are in their organisation.  

Culturally, it gives the whole organisation a chance to hear from each other about what’s working and what’s not – and to appreciate what each part of the business needs to be successful. This is important. When you implement a capital project and portfolio solution, having that level of appreciation means everyone understands the need for change.

Organisations can then see their potential while having a blueprint to work towards. They have insight into what to do first, where the priorities are, what can be held off, and which communities to bring on first – supporting effective change management.

BOOK a CAPEXinsights consultation to discuss how our Business Case For Change process can help your organisation.


Related