Construction projects may look similar on site.
There are budgets to control, programmes to manage, contractors to coordinate, risks to mitigate and stakeholders to satisfy.
But the way a project is governed can be radically different depending on one basic question:
Is it a public infrastructure project or a private development?
That distinction affects almost everything.
Who has authority.
How quickly decisions can be made.
How procurement is controlled.
How much risk is tolerated.
Who ultimately has to answer when something goes wrong.
In Malaysia, the contrast is especially visible.
Public infrastructure operates within a governance environment shaped by government ministries, JKR, CIDB requirements, financial controls, audit mechanisms and anti-corruption obligations. Private developments, meanwhile, are typically driven by boards, management teams, investors and shareholders, with greater emphasis on commercial performance and speed.
Neither model is inherently superior.
They are designed to solve different problems.
And increasingly, the strongest project governance model may be one that borrows from both.
Public infrastructure is built around accountability
When taxpayers fund a project, governance cannot simply focus on whether the building, road or facility is eventually completed.
The process itself matters.
Public infrastructure projects must demonstrate that decisions were properly authorised, procurement was conducted fairly, expenditure was justified and records are available for scrutiny.
This creates a governance structure with multiple layers of accountability.
A major public project may ultimately be answerable not only to the project team, but also to government ministries, audit institutions, regulators, Parliament and the public.
That naturally changes how decisions are made.
Authority is more formalised.
Approvals are documented.
Procurement follows structured procedures.
Variations require justification.
Risk escalation is recorded.
The system is deliberately designed to leave a trace.
This is one of public-sector governance’s greatest strengths.
When effectively implemented, strong documentation and structured approval mechanisms can reduce arbitrary decision-making and strengthen accountability.
But there is a trade-off.
Every additional layer of control introduces another potential approval point.
And on a construction project, time matters.
A delayed approval can affect procurement.
Procurement delays affect mobilisation.
Mobilisation delays affect programme.
Programme delays eventually affect cost.
The very mechanisms designed to protect a project can therefore also reduce its ability to react quickly.
Private development starts from a different question
Private development operates under a different set of pressures.
The central concern is usually not public accountability.
It is capital performance.
Developers and investors want to know:
How quickly can the project move?
How efficiently can capital be deployed?
What is the expected return?
How will delays affect financing costs?
When can the development begin generating revenue?
This produces a governance structure that is often far more centralised.
Authority may sit with a board of directors, managing director or executive committee.
Procurement can be negotiated.
Preferred vendors can be appointed.
Commercial information can remain confidential.
Award cycles can be shortened.
If management decides that a variation makes commercial sense, approval may happen relatively quickly.
That agility is a genuine competitive advantage.
But speed also creates its own governance risks.
When procurement becomes highly flexible and decision-making is concentrated among a small number of individuals, weak controls can increase exposure to financial leakage, conflicts of interest or poorly documented decisions.
Private governance therefore faces the opposite challenge of public governance.
The problem is rarely excessive control.
The problem is making sure speed does not come at the expense of discipline.
The real difference is what each system is trying to protect
Public and private project governance often appear to be opposites because they optimise for different outcomes.
Public infrastructure governance protects legitimacy.
Private development governance protects capital.
Public projects therefore emphasise transparency, procedural compliance and defensibility.
Private projects emphasise efficiency, profitability and responsiveness.
Public procurement tends to favour open competition, structured evaluation and transparent decision-making.
Private procurement may favour negotiation, preferred supplier arrangements and commercial confidentiality.
Public financial governance focuses heavily on budget compliance and formal justification.
Private financial governance focuses on return on investment, cashflow efficiency, internal rate of return and capital recovery.
Risk appetite differs as well.
Public projects are normally more conservative because decision-makers must consider regulatory, legal and reputational exposure.
Private developers may accept greater commercial risk where the potential return justifies it.
Even project audits reflect this distinction.
Public projects are exposed to external institutional scrutiny.
Private projects rely more heavily on internal corporate governance, investor oversight and financial control systems.
The weakness of public governance is often bureaucracy
Strong governance is not the same thing as more governance.
This distinction matters.
Public-sector systems can become so focused on procedural protection that they create unnecessary friction.
Approvals take longer.
Variations become difficult to process.
Project teams hesitate to make decisions because every decision may eventually need to be defended.
In extreme cases, governance becomes a mechanism for avoiding responsibility rather than exercising it.
A project can technically comply with every procedure and still perform poorly.
That is why compliance alone should never be mistaken for project governance maturity.
Good governance should help a project make better decisions.
It should not simply produce more paperwork.
The weakness of private governance is often overconfidence in agility
The private sector can make the opposite mistake.
Because decisions can be made quickly, organisations may assume that formal controls are unnecessary.
That becomes dangerous when projects grow in complexity.
A RM5 million development can sometimes operate through informal management relationships.
A RM500 million development cannot.
As project scale increases, undocumented decisions, weak procurement controls and informal authority structures become increasingly risky.
Speed without traceability creates vulnerability.
A decision that appears commercially rational today may become difficult to defend two years later when a dispute arises.
This is where private developers can learn from public-sector governance.
Documentation is not bureaucracy when it protects institutional memory.
Structured approvals are not inefficiency when they clarify accountability.
Audit trails are not administrative burdens when they help establish who approved what, when and why.
The strongest model may sit somewhere in between
This brings us to what I believe is the more useful direction for construction governance.
Rather than choosing between rigid public governance and highly flexible private governance, project organisations can adopt an adaptive hybrid model.
Such a model retains public-sector strengths such as transparency, documentation and structured risk oversight while incorporating the private sector’s ability to make decisions quickly.
In practical terms, this could include:
clear Delegation of Authority matrices
stage-gate approval structures
risk-adjusted approval thresholds
structured but accelerated procurement
digital audit trails
real-time performance dashboards
clearly defined escalation procedures
stronger accountability at project level
The objective is not to eliminate governance.
It is to make governance proportional to risk.
A RM20,000 operational decision should not necessarily require the same approval architecture as a RM20 million contractual variation.
Governance should become more stringent as risk increases.
That is very different from applying the same process to every decision.
Digital governance changes the equation
Technology is also beginning to reduce the traditional gap between public and private governance.
Historically, transparency came with administrative cost.
If organisations wanted detailed records, they needed people to prepare reports, maintain registers, circulate documents and update spreadsheets.
Today, much of that can be automated.
Real-time dashboards can provide management visibility without waiting for monthly reporting cycles.
Digital procurement platforms can record supplier evaluations automatically.
Approval workflows can create audit trails without additional paperwork.
Compliance systems can flag missing documentation.
Predictive analytics can identify emerging cost, schedule or risk exposure before it becomes critical.
This means organisations may no longer have to choose between control and speed.
Well-designed digital governance can provide both.
Governance maturity is ultimately about how decisions are made
Project governance maturity can be viewed as a progression.
At the lowest level, control is informal.
Decisions depend heavily on individuals.
The next level introduces documented procedures.
From there, organisations develop structured oversight.
More mature organisations integrate digital governance.
The most advanced eventually move towards predictive, analytics-driven decision-making.
At that point, governance stops being merely a control mechanism.
It becomes an intelligence system.
Management does not simply ask:
“Did we follow the procedure?”
It begins asking:
“What is the data telling us, where is risk developing, and what decision should we make now?”
That is a very different level of governance maturity.
Public-private projects make this even more important
Malaysia’s increasing use of public-private partnerships makes the distinction between public and private governance even less straightforward.
PPP projects must operate within both worlds.
They need transparency because public interests are involved.
They need commercial discipline because private capital is involved.
They need accountability.
They also need speed.
That makes governance design particularly important.
A governance structure copied entirely from the public sector may become too slow.
A structure copied entirely from private development may not provide sufficient public accountability.
Hybrid governance is therefore not merely theoretical.
For many future infrastructure projects, it may become essential.
The lesson for project managers
For construction project managers, especially those operating at senior or strategic levels, governance cannot be treated as an administrative subject.
It determines how power moves through a project.
It determines who can make decisions.
It determines how quickly problems can be resolved.
It determines how risk is escalated.
And when disputes arise, it determines whether the organisation can explain and defend the decisions it made.
The strongest governance systems are therefore not necessarily the ones with the most procedures.
They are the ones that create:
clear authority, financial discipline, structured risk oversight, ethical accountability and timely decision-making.
Public infrastructure has much to teach private development about transparency and accountability.
Private development has much to teach public infrastructure about agility and capital efficiency.
The future of construction governance may belong to organisations capable of combining both.
Because ultimately, project governance should not be about choosing between control and speed.
It should be about achieving both without sacrificing accountability.
The articles and technical notes published on this website are intended for knowledge sharing and professional discourse within the construction project management community. The views, opinions, and interpretations expressed are those of the respective authors and do not necessarily reflect the official policy, position, or constitutional stance of the Association of Construction Project Managers Malaysia (ACPM) or its Council.
The content should not be construed as legal, regulatory, or professional advice. Readers are encouraged to exercise their own professional judgement and seek appropriate advice where necessary
.