Governance Is Not the Meeting
A calendar full of reviews does not automatically create good governance. The real test is what happens to an issue before it reaches the room and after the meeting ends.
One of the easiest mistakes in governance is to confuse the meeting with the governance.
A weekly review can happen on time, with the right deck and all the right people in the room, and still achieve very little.
I have come to think of the meeting as the visible part of governance. Most of the useful work happens before and after it.
Before the meeting, the real question is: what needs a decision?
If every project gets equal airtime, the agenda is usually too broad.
Mature governance is selective. It separates routine information from exceptions. It identifies what has changed, what is at risk, what is blocked and what requires somebody with authority to make a call.
That preparation changes the meeting from a status recital into a decision forum.
A good escalation contains more than the problem
“We have a resource issue” is not yet a useful escalation.
A stronger version explains what has changed, what the consequence is, when the decision is needed and what options exist.
This is where good PMO and program leadership adds real value. It helps turn operational noise into a decision that leadership can actually make.
After the meeting is where governance proves itself
I pay close attention to what happens to decisions after the meeting ends.
Was an owner named? Was a date agreed? Did the decision reach the teams affected by it? Did the next portfolio view reflect the change?
A meeting can feel productive because there was a good discussion. Governance is productive only when something changed as a result.
The cadence matters, but not every issue belongs in the same cadence
Weekly, monthly and quarterly forums serve different purposes.
A weekly review might focus on exceptions, decisions and near-term risk. A monthly review can look at trends, finances and cross-program dependencies. A quarterly review has room to ask a harder question: is this still the right work to be doing?
Trying to make one meeting do all three usually creates a very long meeting.
What I want governance to create
When governance is working well, people know:
- what matters;
- what has changed;
- who owns the next move;
- which decisions need leadership involvement; and
- when unresolved issues will be revisited.
None of that requires an elaborate governance model. It requires consistency and discipline.
Meetings are easy to count. Decisions are harder.
If I had to judge the health of a governance model, I would spend less time looking at the calendar and more time following what happens to an issue from first visibility to final decision.