Construction Doesn't Have a Productivity Problem. It Has an Operating-System Problem.

For decades, construction has been told that it has a productivity problem. The statistics make that argument difficult to dismiss. Infrastructure Australia’s 2025 market-capacity work says the long-term construction multifactor-productivity trend remains broadly flat and below mid-1990s levels.

But what if productivity is not the root problem?

What if productivity is an outcome of something deeper: the way we design and operate projects?

A modern project can have a sophisticated master programme, a cost-control platform, BIM, document control, procurement systems, safety systems, Lean workshops and highly experienced people. Yet the project can still become late, congested, adversarial and unpredictable.

That should tell us something.

The industry may not have a shortage of tools. It may have a shortage of system design.

Think about how a major project is assembled. The contract is often designed separately from the production strategy. Design has its own management process. Procurement develops another. Planners create the programme. Commercial teams protect contractual positions. Site teams solve daily production problems. Digital teams manage information platforms. Suppliers optimise their own operations.

Each part can be rational in isolation and dysfunctional in combination.

In manufacturing, nobody would deliberately build a factory by purchasing ten excellent pieces of machinery, placing them in a building and assuming that a production system would emerge. The flow between them would be engineered. Capacity would be understood. Buffers would be intentional. Work in process would be controlled. Quality would be designed into the system. Information would arrive when needed.

Construction projects deserve the same systems thinking—without pretending that a project is simply a repetitive factory.

This is why the next conversation in construction needs to move beyond productivity.

We need to ask: who designed the operating system of the project?

That operating system includes much more than the programme. It includes strategy, culture, governance, commercial arrangements, production design, information, supply chains, resources, planning, control, reliability and learning.

If those elements reinforce each other, productivity has a chance to improve sustainably.

If they fight each other, asking people to “be more productive” is unlikely to solve much.

At Blue Ocean HPA, we have been exploring what a Project Production Operating System could look like: not another piece of software and not another methodology competing with every method that already exists, but an architecture for making the existing pieces operate as a coherent production system.

It is early thinking, and deliberately so.

But perhaps the industry’s next productivity breakthrough will not come from asking every trade to work faster.

Perhaps it will come from designing a better system in which everyone works.

 If this resonates—or you disagree—we’d like to hear where you see this kind of fragmentation showing up on your own projects.