It’s Not a Project Problem. It’s a System Problem.

When the same supply chain problem keeps showing up across multiple projects, it probably isn’t a project problem. It’s a system problem.

That sounds obvious written down. In practice, it is one of the hardest things for an organization to see, because each occurrence arrives looking like an isolated event, with its own project, its own schedule pressure and its own people trying to fix it.

A pattern that couldn’t be ignored

Early in my time in a senior leadership role at a major utility, we were transforming the supply chain business from the ground up while continuing to support a substantial portfolio of capital projects already in flight.

One major equipment category was causing recurring problems. Projects that depended on it were consistently experiencing schedule delays. In some cases deliveries were late; in others, quality was deficient. Each time, the project team escalated, the supplier was pressed, and the immediate issue was eventually resolved.

Then it happened again on the next project.

The pattern had become impossible to ignore, and it was attracting executive attention. We could have continued treating each occurrence as another hole in the dike that needed to be plugged. Instead, we stepped back and looked at the category as a system.

What the systems response looked like

For us, that meant working on five things at once:

1. Revisiting technical specifications. Some requirements had accumulated over time without a clear purpose, adding cost and complexity for suppliers without adding value for us.

2. Aggregating demand. Instead of buying project by project, we consolidated requirements to give the supply market real visibility of what was coming.

3. Building long-term commercial frameworks. New agreements placed greater emphasis on quality and on-time performance, with KPIs to match, so the commercial incentives pointed in the same direction as the outcomes we needed.

4. Going into suppliers’ facilities. Seeing how and where the equipment was made gave us a far better understanding of supplier capabilities and constraints than any bid document could.

5. Managing the relationship deliberately. We established a structured approach to supplier relationship management, including direct executive-level engagement on both sides.

The results

The results were transformative. Schedule disruption was dramatically reduced, quality improved, and the approach became a model for other categories to follow.

Look in the mirror, too

When this post first ran on LinkedIn, a colleague made an important point: asset owners often point fingers at suppliers without recognizing the in-house issues contributing to the problem. He’s right. Point one finger at the supplier, and there are usually three pointing back at you.

Some of the root causes in our case sat inside our own organization: specifications, forecasting, how we packaged work and how we communicated with the market. A systems view only works if it is honest about both sides of the relationship.

How to tell if you have a system problem

A few questions worth asking:

• Is the same category, supplier or failure mode appearing across more than one project?

• Are your teams spending more time expediting than planning?

• Do lessons learned get recorded but not acted on?

• Is each fix owned by a project, while the cause sits across several functions?

If several of these sound familiar, the next fix is unlikely to be the last one.

The lesson has stayed with me: often, the real solution is to redesign the system, rather than just treat the symptom.

Stabilize. If the same supply chain problems keep coming back, I help organizations find and fix the root causes across people, process and technology, so performance holds. Let’s talk.