Project Management

Please login or join to subscribe to this thread

Project Governance. What makes it challenging?

linkedin twitter facebook   Change Management   Decision Making   Governance  
avatar
Edmund M Oil & gas Ireland, Ireland

I’ve been a project manager for about 10 years now, across five very different industries, and one thing that has been surprisingly consistent everywhere I’ve worked is the lack of real project governance. We all talk about it, but in practice it usually ends up being scattered documents, siloed approvals, unclear phase gates, and a whole lot of “we’ll fix it later.”

I’m currently talking to PMs to better understand what governance pain points they’re dealing with today. I’m especially curious about:

  • How phase gates are handled (if at all)
  • How teams track changes to budgets/timelines/requirements
  • Whether risk visibility actually influences decision-making
  • How PMO expectations differ from what tools actually support
  • How teams enforce accountability without slowing everyone down
  • And honestly—how often governance becomes “busywork” instead of a helpful framework

From my experience, the gap usually isn’t the methodology—it’s that most tools don’t support practical governance, and most PMs end up duct-taping spreadsheets, Confluence pages, and manual approvals.

If you’re willing, I’d really love to hear what challenges you see with governance in your projects or organisations. What slows you down? What’s missing from current tools? What would make governance feel more like support instead of policing?

Not trying to sell anything—just speaking as someone who has felt the pain for years and is trying to validate whether others see the same patterns. Appreciate any insights!

Sort By:
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
Implementing governance is kind of like setting up a PMO. You can do it for the sake of doing it (because you have to have governance) and maybe realize some value, if you're lucky, or you can focus on delivering value and then realize the benefits of it in the process. You don't "need" governance any more than you "need" a PMO. What you need is the value derived from performing the right governance activities at the right time. It becomes busywork when you're doing it for the sake of doing it instead of doing it because it provides meaningful value. One gap is the meaning behind it. If you can't "do" governance without the "right" tools, you might not be able to do it with them, either.

Another gap, and possibly a conundrum, is the desire of non-project managers to talk or think about governance. Project management has essentially codified a slough of topics that only project managers seem to care about (I'm not saying it always is that way, it just seems that way). This is the conundrum - projects need governance. Nobody wants to talk about it or pursue it, but it gets attempted because that's what you're supposed to do and then governance gets blamed when the attempt to implement it fails. Kind of like how agile gets blamed when agile fails. I'm sensing some patterns here. It's almost like people want to blame frameworks to avoid discomfort and accountability.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Edmund -

Context counts and unfortunately when it comes to governance, it rarely is tailored to fit the specific context of a given project. Either the approach is unnecessarily heavy resulting in frustration, delays and reduced business value delivered or it misses the mark leaving the project exposed.

In my last full time role, we implemented a "smart governance" model within a large Canadian bank which tried to do a better job at profiling projects and taking a delivery & control objectives rather than an artifact driven approach. This provided teams and stakeholders with the flexibility of picking approaches which fit their projects while still meeting the needs of control partners.

Kiron
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal

Great question.

In my experience, the biggest challenge in project governance isn’t methodology, it’s coherence.

Most organisations have phase gates, templates and tools, but governance fails because:

  • Gate reviews don’t translate into real decisions
  • Information lives in separate tools with no unified visibility
  • Risks are documented but don’t influence behaviour
  • PMO expectations don’t match operational reality
  • Accountability feels punitive instead of enabling
  • Governance doesn’t evolve with what teams learn

Governance only works when it becomes a living system, not paperwork:

Clear decision pathways, shared visibility, regular alignment cadences, and tools that support how work actually flows.

When governance reduces ambiguity and strengthens decisions, teams see it as support, not bureaucracy.

Thanks for starting this essential discussion.

avatar
Lissette Indhira Pimentel Sosa
Community Champion
Program Manager| HARPER SRL Santo Domingo / Distrito Nacional, Dominican Republic
Governance struggles because it's fragmented and rarely tied to real decision-making. Phase gates are unclear, risks don’t drive action, and PMOs ask for data that tools don’t support, so teams end up patching spreadsheets and manual approvals.
For me, governance works when it’s clear, consistent, and easy to use. When it helps teams make better decisions instead of adding friction, people actually follow it.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"It is impossible to travel faster than the speed of light, and certainly not desirable, as one's hat keeps blowing off."

- Woody Allen

ADVERTISEMENT

Sponsors