Role & Responsibility

A cycle both sides are feeding without knowing it.

Management doesn't know what the board actually needs. So it produces more: more detail, more justification, more pre-emptive answers. The board reads the detail as an invitation to engage. The cycle continues. Everyone is working hard. Nobody is governing.

The boundary between board and management is almost never explicitly agreed. It is assumed, negotiated informally, and redrawn every time a paper arrives at the table. That instability produces predictable behaviour on both sides, and neither side is doing anything wrong. They are responding rationally to an unclear situation.

Five words that draw the line clearly enough to hold.

• Design

  Creating solutions, strategies, structures, and operating models that deliver the mission. Design requires immersion in the work. Management, entirely. The board does not design.

• Decide

  Making the calls that determine what the organisation does. Mostly management. The board reserves a short list: CEO appointment, board composition, constitutional matters of genuine strategic consequence.

• Discern

  Applying collective judgement to what management brings. Is the thinking sound? Are values upheld? Is the organisation healthy? The board's central contribution, and the one most often displaced.

• Delegate

  The explicit granting of authority for management to act without seeking endorsement. Unclear delegation is the engine of micromanagement. Board grants, management holds.

• Due Diligence

  The quality of thinking management must demonstrate before the board will endorse. A standard agreed in advance, so management knows what it is writing for and the board knows what it is reading for.

Two and a half hours. Board and management. One shared map.

• First halfThe Honest Diagnosis
  • Opening provocation: both sides name their experience of the current dynamic honestly. What is working, what is not.
  • The Five Ds introduced, walked through against real examples from this organisation's experience.
  • Board papers audit: what was each recent paper asking the board to do? Was that a governance question or an operational one?
  • Where the gap is biggest between what mgmt assumes and what the board wants is where the work lives.
• Second halfBuilding the Shared Map
  • The reserved list: the board names, explicitly and briefly, what it decides for itself. Brevity is the discipline.
  • The delegation map: what management can do without endorsement, named explicitly and agreed by both sides.
  • The endorsement threshold: four zones of decision territory agreed. Management knows what it is writing for.
  • Commitments recorded in minutes. The board commits to holding the framework. Management commits to writing to it.

A shared map both sides can rely on.

• The reserved list

  A short, explicit list of what the board decides for itself. Brevity is the measure of quality: a long list is a governance problem, not an achievement.

• The delegation map

  What management can do without seeking endorsement, named and agreed by both sides. The engine of a functioning board-management relationship.

• The endorsement threshold

  Four zones of decision territory with a clear brief for what management needs to demonstrate in each. Mgmt knows what to write for. Board knows what to read for.

• A brief for the next paper

  Management leaves with a clear understanding of what the board needs. The next papers should be shorter, sharper, and better used.