Your board owns decisions about what success looks like. Your CEO owns decisions about how to achieve it.
The distinction seems simple, but it trips up nearly every governing board at some point. A governance decision answers "what" and "why": the outcomes you exist to produce, the resources you'll commit, the standards you'll measure against, the direction the organization moves. A management decision answers "how" and "who": the staffing plan that gets you there, the vendors you select, the day-to-day operations that deliver your services. When a board chooses a strategic priority, that's governance. When the CEO hires the team to execute it, that's management. When the board sets the budget, that's governance. When the CEO decides which contracts to sign within that budget, that's management.
The common mistake is that boards approve a governance direction without clarifying what authority they have actually delegated. They do not deliberately take over management. A hospital board might approve a new cardiac care program (governance) and then, months later, find itself drawn into discussions about which equipment vendor to select (management) simply because no one explicitly said the CEO owned that choice. A community foundation board might adopt a new grant-making priority (governance) and then get pulled into reviewing individual applicant proposals (management) because the board never established a clear threshold for when staff decisions become board decisions. In both cases, the line is never drawn clearly in the first place, so crossing it is not an intentional act.
The practical test is this: ask whether the decision changes what the organization is trying to accomplish or simply how it goes about accomplishing what it already set out to do. If it shifts the target, the board owns it. If it only affects the path to the target, the CEO owns it. This sounds straightforward, but it requires honest conversation at the point of decision, not after confusion has already set in.
One complication deserves direct attention: what happens when the CEO's management decision produces a result that seems to contradict the board's governance direction? A foundation board sets a priority to fund early childhood programs. The CEO, exercising delegated authority, awards a grant to an organization that later faces controversy. The board's instinct may be to intervene, to involve itself in the specific grant decision after the fact. But the governance response is different. The board should examine whether the criteria it set were clear enough, whether the delegation was properly defined, and whether the monitoring framework caught the issue at the right level. The specific grant decision remains management's to make and to learn from. The board's role is to ensure the governance framework, the criteria, the delegation, the monitoring, was sound.
Your board can make this distinction operational through these steps:
- When your board adopts a goal, strategy, or budget, explicitly state what authority you are delegating. Say: "We're setting the priority. We expect you to determine the best way to execute it." Silence is not delegation. It is ambiguity waiting to become conflict.
- Create a simple decision map for your organization. List the major decision categories (strategic direction, resource allocation, program design, operational execution, personnel) and note which ones live at the board level and