Lightweight Project Governance: What Good Looks Like (and What Bad Looks Like)
Project governance has a bad name, and it earned it. Too often it means a calendar full of standing meetings, status decks no one reads, and a steering committee that meets monthly to nod at slides. By early 2021, with teams scattered across home offices and time zones, that heavy model finally cracked: you cannot run a thirty-person video call to approve a $5,000 change. The teams that adapted did not abandon governance — they made it lightweight. The point of governance is to make the right decisions quickly and keep a clear record of who decided what. Everything else is overhead.
Here is the contrast, drawn from real recovery-era projects, between governance that helps and governance that gets in the way.
What good looks like
Decision rights are written down: everyone knows what the project manager can approve, what needs the sponsor, and what goes to the steering group.
Meetings exist to decide, not to inform — status is shared in writing beforehand so the time together is spent on choices and blockers.
There are clear thresholds: spend or schedule changes below a line are handled by the PM; only the exceptions escalate.
Decisions are logged in one place with the date, the options considered, and the rationale, so no one re-litigates last month's call.
The sponsor is reachable between meetings for the genuinely urgent decision, instead of becoming a monthly bottleneck.
What bad looks like
Every decision, large or trivial, waits for the next committee date, so the project moves at the speed of the meeting cadence.
Nobody can say who actually owns a given decision, so it bounces between people until someone forces it.
The status report grows into a 40-slide ritual that consumes the team's week and informs no choice.
Decisions are made verbally and never recorded, so they quietly reverse themselves and the same argument recurs.
Governance is bolted on at the end as an audit exercise rather than built in as a way to steer.
How to make yours lightweight
Write a one-page decision-rights table. List the decision types, the dollar or schedule thresholds, and who approves each. Get the sponsor to agree to it once, up front.
Default to written status, reserve meetings for decisions. If a meeting has no decision to make, cancel it and send a short note instead.
Keep a single decision log. One running document: date, decision, options weighed, owner. It is the cheapest governance artifact and the most useful when memories diverge.
Set an escalation path for the urgent exception. Agree how a genuinely time-sensitive call gets made between meetings, and who can make it, so urgency does not become an excuse to bypass the rules.
Lightweight does not mean loose. A small project with crisp decision rights and an honest log is better governed than a large one buried in ceremony. The test is simple: when a decision is needed, does your governance help it happen faster and leave a clean trail, or does it slow things down and lose the thread? Aim for the first.
If you want a governance model that fits the size of your project rather than fighting it, XNM's program & project delivery advisory can help you set one up.