Industry

Fractional COO & ERP lead for energy

I bring exactness to complex energy operations and keep ERP rollouts honest, so process and data hold up where precision is not optional.

16 years inside the operational layer. An independent fractional operator.

The patterns

How Energy operations break

Energy operations are complex, regulated, and data-heavy, which makes them unforgiving of loose process. The teams I meet are often mid-way through, or recovering from, an ERP or systems programme that promised to fix everything and instead added complexity. The issue is usually not the technology. It is that the process and data discipline underneath it were never made exact enough.

ERP programmes overrun and underdeliver

The rollout took longer, cost more, and delivered less than promised, and nobody wants to say so.

Process is not exact enough for the system

The system needs precise inputs, but the process feeding it is loose, so the outputs cannot be trusted.

Data discipline is inconsistent

The same thing is recorded differently across teams and sites, which breaks reporting and compliance.

Complexity has no owner

The operation is genuinely complex, and no single person owns making it coherent.

Reporting is a manual rebuild

The numbers leadership and regulators need are assembled by hand each time rather than produced by the system.

Change lands badly on the floor

New systems and processes are rolled out without the operational side, so adoption stalls.

Why it happens

The technology outran the operating discipline

Energy businesses invest heavily in systems because the complexity demands it. But an ERP is only as good as the process and data feeding it, and that discipline is often treated as an afterthought to the software project. The fix is to make the operation exact first, so the system reflects reality instead of amplifying the mess.

How I approach the fix

The order matters more than any single fix.

01

Diagnose first

I assess the operation and the state of the systems programme, and find where process and data discipline break down. This is the Operations Audit.

02

Make the process exact

Tighten the process and data standards so the system gets inputs it can trust.

03

Lead the rollout honestly

I own the operational side of the ERP programme and keep it scoped to what you need. The heavy build is delivered by a trusted delivery team I coordinate.

04

Make reporting a by-product

The numbers leadership and regulators need produced by the system, not rebuilt by hand.

05

Leave it owned

Clear ownership of the operation and a system the team actually uses.

Where this gets you

The ERP programme lands, scoped to what you need, instead of sprawling. Process and data are exact enough that the outputs can be trusted. Reporting is produced, not rebuilt. And the complexity has an owner keeping it coherent.

Keep the complexity honest.

A 30-minute call, no pitch. Tell me what is breaking and I will tell you straight whether I can help.