The Line Between the Head and the Board

Every governance textbook draws the same line. The board governs. The head manages. Strategic oversight on one side. Operational delivery on the other. Clean, clear, understood.

In practice, the line is never where the textbook puts it.

It moves. It moves when the board does not trust the head's judgement on a particular issue. It moves when the head does not trust the board to understand the operational implications of a strategic decision. It moves during a crisis, when the board steps closer to operations because the situation demands it. It moves back afterwards — sometimes. Not always.

The problem is not that the line moves. The problem is that it moves without anyone acknowledging that it has moved. And once it has moved, it is very difficult to move it back, because the precedent has been set and the new position feels like normal.

Boards that do not trust the head tend to micromanage. They ask for more detail. They want to see operational plans. They question individual staffing decisions. They frame this as thorough governance. It is not. It is anxiety expressed through process. And it produces a predictable response: the head starts withholding. Not lying. Editing. Presenting information in ways designed to avoid triggering further intervention. The board gets less transparency, which confirms its suspicion that it needs to look more closely. The cycle deepens.

Heads who do not trust the board tend to manage upwards. They control the information flow. Board papers are polished to the point of opacity. Strategic updates present activity as progress. Difficult conversations are deferred or reframed. The board feels informed without being engaged. The head feels safe without being accountable. Neither side is governing well, and both would describe the relationship as functional.

The textbook answer is role clarity. Define the boundaries. Write them down. Agree on a delegation framework. This helps. But it helps in the way that a prenuptial agreement helps a marriage — it establishes terms, but it does not build trust.

Trust is built through a specific kind of transparency. Not the transparency of sharing everything, which overwhelms. Not the transparency of sharing nothing uncomfortable, which deceives. The transparency of sharing what matters, in a structure the board can navigate, at a level of detail that informs without inviting interference.

That structure is harder to build than it sounds. Most governance frameworks give the board two levels of engagement: the strategic summary in the board pack, and the operational detail they can request if they want to dig. The first is too thin. The second is too much. The middle ground — the level of visibility that builds confidence without enabling micromanagement — requires a shared structure that both sides can see.

Platforms like Loom create that shared structure. The board sees governance-level information — strategic progress, decision history, oversight indicators. The head sees operational detail alongside it. Both are looking at the same system, at different layers. The line is not drawn once in a policy document. It is expressed continuously in what each layer shows.

Because the relationship between the head and the board is not a boundary to be defined. It is a structure to be built. And the schools that build it well tend to spend less time arguing about where the line is — because both sides can see the same picture.