Project governance gets a bad reputation for understandable reasons. In too many organisations, governance is where momentum goes to be slowly processed into meeting minutes. Steering committees review papers they have not had time to read, risks are noted but not resolved, decisions are deferred until the next cycle, and delivery teams leave the room with more actions than authority. Everyone involved can point to a process being followed, yet the project itself is no more certain, no more aligned, and no more likely to deliver value.
That is not governance. That is administration wearing a serious expression.
Good governance is not there to slow delivery down. It is there to make delivery possible at the speed the organisation needs and the risk profile allows. It clarifies authority, sharpens accountability, protects value, resolves conflict, and gives delivery teams enough freedom to move without forcing them to guess where the boundaries are. Done well, governance creates confidence. Done badly, it creates theatre, and the difference is usually visible in the first few weeks of a major program.
The Association for Project Management defines governance as the framework of authority and accountability that defines and controls the outputs, outcomes, and benefits from projects, programs, and portfolios. It is also the mechanism through which the investing organisation exerts financial and technical control over the work and the realisation of value. That definition matters because it keeps governance anchored to value, not simply compliance.
At Arqvera, we tend to view governance as the operating system for delivery confidence. It should answer a few practical questions very clearly. What are we trying to achieve? Who has authority to decide? What must be escalated? What evidence tells us whether we are on track? What are we prepared to stop, change, or fund when reality starts to diverge from the plan?
If governance cannot answer those questions, it is unlikely to help when the work becomes difficult.
A common source of friction is the confusion between project governance and project management. Project management is concerned with day-to-day execution: planning, coordinating resources, managing dependencies, tracking progress, handling risks, and keeping the team moving. Governance is concerned with direction, authority, accountability, investment control, decision quality, and benefits.
Put simply, project management is about doing the work properly. Governance is about making sure the right work is being done for the right reasons, with the right controls and the right level of executive ownership.
When leaders confuse the two, governance bodies drift into operational management. Steering committees start debating task-level detail, sponsors become shadow project managers, and delivery leaders spend more time explaining than delivering. This does not create control. It creates dependency. The project team learns that important decisions are not theirs to make, while executives become frustrated that delivery lacks pace. Both sides are usually right, which is why the system needs fixing.
Effective governance sets the boundaries and then allows competent people to operate inside them. It defines delegated authority, escalation triggers, decision rights, and value measures. It does not require every issue to travel vertically through the organisation in search of approval. If every meaningful decision needs a committee, the governance model has already failed.
Governance should improve decision quality. That is its job.
This sounds obvious, but many governance models are built around reporting rather than decisions. The meeting agenda is full, the dashboard is polished, the risk log is updated, and the financials are reviewed, but nobody is clear which decisions were made, which trade-offs were accepted, or which constraints were removed. The project is observed more than governed.
A useful governance forum should distinguish between information, decision, and intervention. Information keeps stakeholders aligned. Decisions commit the organisation to a course of action. Interventions remove a blockage, reset priorities, adjust scope, release funding, change leadership behaviour, or protect the benefit case. If a governance forum spends most of its time receiving information and very little time making decisions or intervening, it is not providing executive control. It is providing executive visibility, which is much less useful when the project is under pressure.
This is where Mark Crutchfield’s operational discipline comes through strongly in the Arqvera point of view: governance must be designed around execution, not ceremony. Clear decision records matter. Action ownership matters. Issue ageing matters. Dependency management matters. Benefit impact matters. None of this needs to be bureaucratic, but it does need to be real.
A good test is simple. After every governance meeting, the delivery team should know what has been decided, what has changed, who owns the next action, and what authority they now have. If they leave only with “thanks for the update,” the meeting may have been polite, but it was not particularly useful.
Modern transformation is rarely linear. Technology projects are now tied to operating model redesign, data quality, vendor ecosystems, regulatory constraints, customer expectations, cybersecurity, AI adoption, and workforce change. A single decision can cut across finance, operations, HR, legal, technology, commercial, and customer experience. Governance designed for isolated project delivery struggles in that environment because the work is no longer contained neatly inside one function.
PMI’s 2026 Pulse of the Profession research is useful here. It reports that 97% of project professionals managed at least one complex project in the past year, and more than half of all projects now qualify as complex. PMI also found that around one-third of complex projects fail, nearly twice the overall project failure rate, while professionals who manage complexity effectively are five times more likely to increase the likelihood of project success.
The implication is straightforward. Governance can no longer be a passive oversight structure that waits for problems to arrive fully formed. It has to help teams navigate systems. That means understanding interdependencies, surfacing trade-offs early, connecting delivery choices to business outcomes, and making sure escalation routes are fast enough for the pace of change.
This is especially important in AI, ERP, post-merger integration, and private equity value creation work. In each case, the technical delivery is only one part of the equation. The real work involves changing how decisions are made, how roles are defined, how data is trusted, how processes run, and how benefits are captured. A governance model that only tracks milestones will miss the signals that matter.
Leaders often respond to risk by adding governance. More meetings, more reporting, more approval gates, more templates, more dashboards. This can feel responsible, particularly when the program is important, expensive, or politically exposed. The problem is that more governance does not automatically create better control. Sometimes it does the opposite.
Excessive governance slows decisions, increases reporting burden, dilutes accountability, and encourages defensive behaviour. Delivery teams begin managing optics rather than outcomes. Sponsors receive more information but less truth. Risks are written carefully to avoid escalation. The project becomes heavier without becoming safer.
Good governance is proportionate. It applies the minimum level of structure required to maintain decision quality, accountability, assurance, and value control. That is not a call for looseness. It is a call for discipline. The right question is not “How much governance can we impose?” It is “What governance is necessary to make this work safe, fast, honest, and valuable?”
This is where the idea of “minimum viable governance” is useful. A low-risk internal process improvement does not need the same governance architecture as a multi-country ERP implementation or a major operating model transformation. A project with a mature sponsor, stable scope, strong delivery capability, and limited integration risk should not be burdened with the same controls as a fragile program dependent on multiple vendors, weak data, and unresolved business ownership.
Control should follow risk. Governance should follow complexity. Anything else is just organisational wallpaper.
The opposite mistake is also common. Some organisations reject governance because they associate it with bureaucracy. They want pace, empowerment, and agility, so they strip back controls until nobody is quite sure who is allowed to decide, what success means, or when risks should be escalated. This does not create agility. It creates ambiguity.
Agility requires clear boundaries. Teams move faster when they know where authority sits, what outcomes matter, which constraints are non-negotiable, and how trade-offs will be handled. Without those boundaries, every issue becomes a negotiation and every decision becomes a stakeholder management exercise.
Too little governance also creates the conditions for “watermelon” reporting: green on the outside, red underneath. When teams are unclear about escalation routes or fear negative reactions, they soften the message. By the time leadership receives the truth, the cost of recovery is much higher. Strong governance creates safe, early escalation. It should make it easier to tell the truth, not harder.
That is why trust is a system. It is created through clarity, candour, consistency, care, and continuity. Governance is one of the places where trust either becomes operational or remains a slogan.
The executive sponsor is the most important role in project governance, and it is also one of the most misunderstood. Sponsorship is not attending the steering committee, opening the kickoff meeting, or lending seniority to a slide deck. It is active ownership of the business outcome.
A sponsor should set direction, protect priority, resolve cross-functional conflict, secure resources, hold benefit owners to account, and intervene when the organisation drifts. They must understand enough to challenge, but not so much that they become trapped in task-level detail. They are not there to manage the project manager. They are there to make sure the organisation remains aligned around value.
APM’s guidance on governance emphasises focused accountability, delegated decision-making, and a “golden thread” from the desired outcome through the governance structure and into delivery. (APM) That is a useful phrase because weak governance often breaks that thread. The board approves strategy, the steering committee reviews activity, and the delivery team manages tasks, but the connection between investment, outcome, and benefit becomes thinner over time.
Good sponsorship keeps the thread intact. It ensures that decisions are not made simply because they are convenient for delivery, attractive to a vendor, or politically easier in the short term. The sponsor’s job is to keep asking whether the work is still serving the outcome.
A project can be well managed and still fail commercially. It can go live, hit a milestone, and satisfy technical acceptance criteria while failing to produce the operational improvement that justified the investment. That is why governance must track benefits as well as outputs.
APM defines benefits realisation as the practice of ensuring that benefits are derived from outputs and outcomes. This is not a post-go-live administrative task. It should be embedded in governance from the start. If scope changes, the benefit case should be reviewed. If adoption risk increases, value confidence should be challenged. If the operating model is not ready, the project should not be allowed to report green simply because the build work is progressing.
This is one of the reasons Arqvera’s Value Compass exists: to help organisations maintain the connection between transformation activity and measurable business value. It is also why Trust Arq focuses on delivery assurance before “go” gets expensive. The goal is not to create more governance for its own sake. The goal is to make sure governance is aimed at the right thing: confidence, control, and value realisation.
Helpful governance is visible in how work feels day to day. The project team knows who can decide. Sponsors understand their role. Risks are escalated early without punishment. Benefits are reviewed as part of delivery, not after the project has ended. The dashboard shows what matters, not everything that can be measured. Meetings have a purpose, and decisions do not drift from one forum to another in search of ownership.
A practical governance model should include clear decision rights, a defined sponsor role, delegated authority for the delivery team, escalation thresholds, independent assurance points, benefit ownership, financial controls, dependency management, and a cadence that matches the risk of the work. It should also specify what will stop. That last point is often missed. Governance is not only about approving work; it is also about stopping activity that no longer supports the outcome.
For organisations unsure whether their current governance is enabling delivery or slowing it down, Arqvera’s Project Health Self-Assessment can provide an early read on delivery confidence. For more complex or higher-risk programs, Trust Arq provides structured assurance across governance, delivery, partner management, readiness, and value control.
Governance that helps is usually quite practical. It makes the important things visible, the hard decisions timely, and the accountabilities unmistakable. It creates a safe route for bad news, a clear route for decisions, and a disciplined route from investment to value. It does not remove complexity, but it stops complexity from becoming chaos.
Governance that slows you down does something different. It adds process without authority, meetings without decisions, reporting without insight, and oversight without ownership. It gives the impression of control while the real delivery system continues to struggle underneath.
Most organisations do not need more governance. They need better governance. More precisely, they need governance designed around the work they are actually trying to deliver, the risks they are actually carrying, and the value they are actually trying to realise.
The test is simple. If governance helps people make better decisions faster, it is doing its job. If it makes capable people wait, repeat themselves, soften the truth, or escalate everything upward, it has become part of the problem.
Technology rarely fails in isolation. Delivery rarely fails in isolation either. Governance is often the difference between a project that can absorb complexity and one that quietly drowns in it.
Is an AI and technology transformation consultancy and advisory.
We help organisations shape business cases, projects, deliver excellence, and realise change and outcomes that stick. We support organisations before, during, and after projects with an end-to-end service where our domain specialisation comes to life.
Before (Inception): We work with you to clearly define the idea, vision, strategy, and business case for change, as well as help select the right partners, and establish governance
During (Execution): We help deliver project and change objectives while keeping implementation under control through structured governance and assurance to realise intended outcomes.
After (Value Realisation): We ensure outcomes deliver measurable value and embed continuous improvement from successes and learnings.
Arqvera is led by industry veterans in the UK and USA with 100+ years of technology delivery intelligence across global consulting, digital transformation, and mission-critical projects and programmes.