Governance Meetings and Operations Meetings Are Different Meetings

Your weekly meeting runs ninety minutes. Two urgent client things eat the first hour. The structural problem that has been on the agenda for a month gets nine minutes at the end, when everyone is tired, and is deferred again.

It will be deferred again next week too. Not because your group lacks discipline, but because you are running two incompatible meetings in one slot, and one of them always wins.

The two kinds of question

Operational questions are about the work. What do we do about this client, who picks up this task, are we going to hit Friday, this build is broken.

They are urgent, concrete, and mostly answered by whoever holds the relevant role. They have a short shelf life.

Governance questions are about how the work is organized. Who decides refunds, does the Bookkeeper role need a spending limit, we keep dropping handovers so what structure is missing, this policy is producing behavior nobody wanted.

They are rarely urgent, they are abstract, and they change the container everything else happens inside.

Why they cannot share a slot

Urgency always beats importance. A client escalation happening today will always feel more pressing than a role definition that has been unclear for four months. So the structural work is permanently last, and permanently deferred, and the same operational fires keep recurring because the structure that produces them never gets fixed.

They need different modes. Operations wants fast, decisive, and mostly one person deciding. Governance wants slow, careful rounds where everyone gets heard, because you are changing the rules everyone has to live inside.

Switching between those modes inside one meeting is genuinely hard, and groups end up doing governance at operational speed, which produces half-considered structural changes, or operations at governance speed, which is agonizing.

Different people care. Not everyone needs to be in every operational conversation. Almost everyone has a stake in governance.

Split them

The simplest version that works:

Operations: short, frequent. Weekly or twice weekly, 30 minutes, standing up if that helps. Purpose: unblock the work.

Governance: longer, rarer. Every two to four weeks, 60 to 90 minutes, sitting down properly. Purpose: change the structure.

If you cannot face two meetings, do one meeting with a hard split and a real boundary: first 30 minutes operations, then a break, then governance, and a rule that operational items are not allowed to reopen after the break. The break matters. It is the mode switch.

Running the operations meeting

Go around the roles, not around the people. For each area with something live:

1. What is stuck?
2. What do you need, and from whom?
3. Who is doing it, by when?

That is the whole meeting. No status reports. Nobody says what they did last week; that is what your project tool is for. If nothing is stuck, the meeting ends in eight minutes, and letting it end is how you keep people showing up.

The one rule: if a question turns out to be about who is allowed to decide something, it is not an operational question. Capture it, park it, take it to governance. Say "that's a governance one" out loud and move on. This single sentence, used consistently, is most of the discipline.

Running the governance meeting

1. Check in. One sentence each. Not optional, and not a warm-up nicety. People arrive carrying things and it comes out sideways in the objection round if it does not come out here.

2. Build the agenda from tensions, in the room. Do not use a pre-written agenda. Each person names any tensions they have, in a few words each, and they go on a list. This takes four minutes and means you work on what is actually live rather than what someone predicted last Tuesday.

3. Work them one at a time, in order. For each: the person who raised it says what they observe and what they want. Then clarifying questions, reactions round, proposal, objection round, integrate. Every tension gets an outcome: a role created or changed, a policy agreed, a next step with an owner, or an explicit "we are not doing anything about this."

"We are not doing anything about this" is a legitimate outcome and saying it out loud is much better than silent deferral.

4. Check out. One sentence each. How was that. This is where you find out that the process is quietly failing someone.

What belongs where

| Question | Where | |---|---| | The client wants a refund | Operations, or just the role holder | | Who is allowed to approve refunds | Governance | | The site is down | Operations, and honestly not even that | | Nobody knows who is on call | Governance | | Can we afford this contractor | Operations, ask the role | | What is the spending limit on a role before advice is needed | Governance | | Ana and Tom disagree about the design | Operations, or the two of them | | Ana and Tom cannot work together | Neither. Restorative conversation. |

That last row matters. Governance is for structure. A relationship in trouble does not get fixed by writing a policy at it, and trying is how policies end up being obviously aimed at one person.

Where it goes wrong

The split exists on paper only. If governance keeps getting canceled because the week is busy, you have not split anything. Protect it the way you would protect a client meeting.

Governance becomes a complaints session. Every tension has to end in a structural outcome or an explicit no. Without that, it becomes a place to vent, people leave heavier than they arrived, and attendance dies.

Operations expands to fill governance. Hence the break, and hence saying "that's a governance one" out loud every single time.

Nobody facilitates. Both meetings need someone holding the process. Not chairing in the sense of deciding, holding in the sense of keeping the rounds intact and stopping cross-talk. Rotate it. It is a role, so write it down like one.

What good looks like

The operations meeting ends early most weeks. The governance meeting is where the recurring problems actually get solved, so the operations meeting has less to do over time.

And when someone says "wait, who decides this?", everyone knows exactly which meeting that question goes to, and it gets there.

Try this week

Look at your last four meeting agendas and mark each item O or G.

If governance items are consistently at the bottom and consistently deferred, you have found the reason the same operational problems keep coming back. The structure that produces them has never had a slot in which it could be changed.