Governance Is Not a Document

"Questions are places in your mind where answers fit. If you haven't asked the question, the answer has nowhere to go."

— Clayton M. Christensen

A coordination plan can be flawless and change nothing. I've held the pen on one.

It did everything a good plan does. I rated two risks High impact, High probability — the kind you're supposed to kill before they cost you. I named the owners. I drew the gates and set the dates. On paper it was finished.

Then, near the back, in the section that lists who hands off what and when, a line of template text nobody had filled in: consult with the team to develop. The plan even described its own condition. Ready to execute, it said, when organizational pull exists.

It's still waiting.

Naming a risk doesn't retire it. Putting a name beside it doesn't give that person the power to act. A plan can say who should move without changing who can. That gap — between the name on the page and the authority to make the field move — is where the work quietly dies. Not because anyone slacked. The work was good. It died because a document can't hand itself the one thing it needs.

So here's the question I ask first, before any model or any schedule. Most plans never put it in writing:

“Who owns the coordination schedule, and what happens to the project if they miss it?”

If the honest answer is "we'd escalate," or "we'd have a conversation," or "it depends," you don't have a coordination schedule. You have a coordination wish. The owner can publish the plan, run the meeting, flag the risk every week — and still not be able to force the decision that ends it. So the risk sits. Rated, named, alive. Waiting for a pull that rarely comes.

There's a way to break that, and it isn't a better document.

You put the question somewhere it can't be avoided. Model the real condition — the actual bays, the actual conflict — and set it down as a decision that has to happen before anyone builds. Now the meeting can't move past it. The person who could be ignored becomes a question that needs an answer. One case is written up in the overhead MEP sectional study. The model was never the point. The point was that it made someone answer.

Governance is not the plan. Governance is who can make the field answer when the plan and the field disagree.

Most capital programs have plans. Good ones. What they're missing is the authority to turn a named risk into a closed one — and that's not about tools and not about talent. The people are good. The software works. It's about who's allowed to decide. That, you can fix, once you can see it.

The unasked question is the governance question. If no one has asked it on your program, the answer — the stall, the drift, the field deciding for itself — has had nowhere to go but into your schedule.